Scheduling System | Android Development
Repository
https://github.com/LakeEffectRobotics/LakeEffectScoutingApp
https://github.com/LakeEffectRobotics/LakeEffectScoutingServerApp
What is this
This is an app made for a FIRST robotics team.
One of the most important strategic parts of the competition is scouting. Scouting is recording data about other robots to analyse and see what robots are good at what and bad at what.
This is an app to do scouting. Recording data on paper and then putting it in a database is convoluted and wasteful, so we built an app to replace this system. 6 people use the app independently on Android devices and record data about one robot each per game. A server app can then pull data from all the devices to combine it all in one.
Technology Stack
The apps are built with Java and use bluetooth to communicate. The layouts are made in XML.
What have I implemented
Now that all of the nessesary features of the app are implemented, I am implementing a system to organise and schedule when people should switch on and off scouting to prevent chaos and prevent someone needing to do it manually.
Server
On the server, I have created a UI for adding a bunch of active devices to a list to be able to pull them all in one button pressed.
I implemented a user UI to add and remove a list of users.
This list of users will be used to send to the client devices so they know what users are scheduled to scout when.
Client
On the client, you now just have to select a match number, the robot number and team (alliance) it is on is dicided based on the schedule.
Future
The schedule will be decided by the server, and sent over to the client. The client will know when to switch off instead of scouting as well, instead of just knowing a schedule of what robot number to scout (watch) per match number.
Pull Requests
https://github.com/LakeEffectRobotics/LakeEffectScoutingApp/pull/132
https://github.com/LakeEffectRobotics/LakeEffectScoutingServerApp/pull/16
Thanks for the contribution, @ajayyy! Seemingly a lot of work has gone into this, good job. Just for your information: the repository linked at the top doesn't exist anymore (I guess you renamed it).
I would recommend adding a leading space for inline comments. In the grand scheme of things it obviously doesn't really matter, but in my opinion they look a lot more like commented out code when you don't add a space.
Also, it's recommended to try and keep the subject of your commit message to around 50 characters. You can write additional information in the body of the message if needed.
Your contribution has been evaluated according to Utopian policies and guidelines, as well as a predefined set of questions pertaining to the category.
To view those questions and the relevant answers related to your post, click here.
Need help? Write a ticket on https://support.utopian.io/.
Chat with us on Discord.
[utopian-moderator]
Oops, I accidentally kept the wrong words . One of them is scouting app and one of them is server scouting app (I just linked server app). Thanks for the review!
Thank you for your review, @amosbastian!
So far this week you've reviewed 8 contributions. Keep up the good work!
Hi @ajayyy!
Your post was upvoted by @steem-ua, new Steem dApp, using UserAuthority for algorithmic post curation!
Your post is eligible for our upvote, thanks to our collaboration with @utopian-io!
Feel free to join our @steem-ua Discord server
Hey, @ajayyy!
Thanks for contributing on Utopian.
We’re already looking forward to your next contribution!
Get higher incentives and support Utopian.io!
Simply set @utopian.pay as a 5% (or higher) payout beneficiary on your contribution post (via SteemPlus or Steeditor).
Want to chat? Join us on Discord https://discord.gg/h52nFrV.
Vote for Utopian Witness!