Introducing my team's (in development) scouting app, ThunderScout

[snekiam]

Originally Posted by 19lmyers

I was hoping to build an Excel .xlsx export option into a later release of the app, but the main hurdle is that most libraries are too large to embed into an Android app (POI included).

I'd be interested in seeing your implementation and would love to see what you've done so far. Also, the simplest way to currently deal with the custom enum types is to call .name() or .toString() on them to get a string constant representation. I am planning on making that a bit more elegant eventually

I'll see if I can finish up a little more of what I was working on - Finals are this week at my high school, but I have next week off, so hopefully I can get a more complete implementation done by then. I was working on a system my freshman year, which I ended up abandoning in the end that had generated xls files, but it was honestly kinda a piece of crap, and unmaintainable.

[19lmyers]

I've prepared a new alpha release: Alpha 0.3!

This version:

• Adds a new view that summarizes the match data for a selected team
• Fixes a critical bug where the ScalingStats of a team wouldn't be saved when scouting
• Also includes other "bug fixes and stability improvements"

I'm uploading it to the Play Store now. You can find it on GitHub here.

As always, new screenshots can be found here.

If you like the app or have a suggestion on how I could improve it, please reply here, open an issue or pull request on GitHub, or send your feedback via the Play Store!

[cad321]

I absolutely love the app. We developed a similar app that we used this season. However it wasn't nearly as refined/clean as this. It also had notably more bugs. We are seriously considering using this next season.

The only 2 things that I might like to see added is a way to track what match number the stats were recorded in, and the second being an option for a robot's picture. The first we like just to ensure we aren't reading duplicate data accidentally recorded (say 2 students record the same robot during the same match by accident). The match number can also let us track how a team progressed through a regional. The second we find helpful for during our scouting meeting. Being able to let people pull up a picture of the robot you're talking about rather than remembering who team xxyy is in a list of 60 can be much easier.

Again, the app looks fantastic so far and can't wait to see this revised for 2017 SteamWorks.

[19lmyers]

Originally Posted by cad321

I absolutely love the app. We developed a similar app that we used this season. However it wasn't nearly as refined/clean as this. It also had notably more bugs. We are seriously considering using this next season.

The only 2 things that I might like to see added is a way to track what match number the stats were recorded in, and the second being an option for a robot's picture. The first we like just to ensure we aren't reading duplicate data accidentally recorded (say 2 students record the same robot during the same match by accident). The match number can also let us track how a team progressed through a regional. The second we find helpful for during our scouting meeting. Being able to let people pull up a picture of the robot you're talking about rather than remembering who team xxyy is in a list of 60 can be much easier.

Again, the app looks fantastic so far and can't wait to see this revised for 2017 SteamWorks.

Happy to hear that this app may be of some use to you!

I was expecting someone to eventually request match numbers. I implemented the timestamp instead because in my experience, scouts often forget what the match number is, but I'll consider adding it in the future.

Robot pictures is more of a pit scouting thing. I've considered adding a pit scouting mode, but haven't found time to pursue avenues such as that yet.

[dirtbikerxz]

Originally Posted by 19lmyers

Happy to hear that this app may be of some use to you!

I was expecting someone to eventually request match numbers. I implemented the timestamp instead because in my experience, scouts often forget what the match number is, but I'll consider adding it in the future.

Robot pictures is more of a pit scouting thing. I've considered adding a pit scouting mode, but haven't found time to pursue avenues such as that yet.

Match Numbers are pretty useful. Especially when looking back on the data. Because more often than not, our scouters will remember a specific match number in which a specific robot stood out. Time stamps can get pretty confusing, especially with all the field delays, and other problems that naturally occur at regionals.

[19lmyers]

New alpha release: Alpha 0.4!

This version adds:
- A data selection UI that allows you to delete individual matches
- Some basic sorting criteria to the data view
- A quick settings toggle for the Bluetooth server on Android 7.0 and up
- A round icon and launcher shortcuts on Android 7.1

Bug fixes:
- Counter views in the scout UI now behave properly on orientation changes

The new release should be on the Play Store (testing link) within the next 24 hours. Available on GitHub here.

New screenshots can be found here.

[19lmyers]

After testing Alpha 0.4 I found a bunch of very annoying bugs involving the new quick toggle. I ironed out those bugs for the most part (and fixed some startup errors with the Bluetooth server as well), and since I've already published two alphas in two days, these fixes will have to wait until the next alpha build...

...which might be in two days from now! xD

EDIT: The sorting modes are also bugged. The result is sorted lowest to highest, which is the opposite of the intended behavior. A fix for this will also be in the next alpha.

[19lmyers]

I've figured out how to make an Amazon developer account.
When the app launches in 2017 I should be able to have it uploaded to the Amazon App Store as well as Google Play- this means that those of you with Kindle Fire devices won't have to manually install Google Play Services to use the base app functionality!

[19lmyers]

I've released a new alpha containing the first iteration of the Feed: A reverse chronological timeline of what the app does, right on the home screen.

As always, if you have any questions or comments I'd be happy to hear them.

[19lmyers]

A new alpha has been released: Alpha 0.6!

This release adds a much-requested feature: Match numbers!

The scouting flow has been reworked and improved to accommodate the addition of match numbers and alliance colors.

You'll also find alliance colors tinting various screens of the app

Please send me your feedback on this release! This addition is a major change to the scouting flow, and I'd like to have input on how I can further rework the data viewing screens to accommodate it.

Finally, suggestions, bugs, and ideas about where ThunderScout can go next are always welcome!