User Tools

Site Tools


scoutradioz:programming:planning

Planning

this page is a stub!

2024 Off-Season Wishlist

  • Start the beginning of an onboarding program for community developers
  • Modernize the Scoutradioz landing page experience
  • Update Voyager with scouter functionality in Mothership
    • Add “super scouting” to Voyager
    • Update “per user scouting dashboard” to show only the matches the user is assigned to (rather than all six in each match where the user has an assignment)
  • Improve general app navigation
  • Implement using images to enable capturing auto paths

Stretch goals

  • Add OAuth authentication, separate “user login” from “per-team entitlements” - i.e., a single OAuth authenticated login could be associated to multiple teams
  • Ingest TBA's OPR/cOPR data and statbotics EPA, allow teams to incorporate with their own metrics
  • Implement a 'zero-org' purely OPR/cOPR/EPA view set, i.e. can select any event and see Scoutradioz metrics/etc. even if no team is scouting
  • Add APIs - e.g. integrating with The Purple Standard, or enabling teams to programmatically download their own data, etc.
  • WYSIWYG form editing

Bugfixes/optimizations

  • Revise the 'browse by event' view to cache the data & not recalculate it every page load
  • More guardrails / automatically sniffing out suggestions (e.g., “set who is present”, “you should manually enter data”, etc.)

Long-term Wishlist

  • Enable browser-based Bluetooth to share large amounts of data between offline Voyager instances
  • Share robot pit scouting photos to/from Voyager
  • Incorporate analytics directly into Voyager

Github issues lists

Notes from teams at 2024 Worlds

We met with many Scoutradioz-using teams at Worlds over the course of the event and asked them two questions:

  1. “What do you love the most about Scoutradioz?” and,
  2. “If you could ask for one thing to be added/fixed/changed/etc., what would it be?”
  • 5914 - Love: Can see all the data at once
    • Ask: SR team should do more to get the word out
  • 5885 - Love: Gives you a lot of insights that public sites don't, comments from your team. First year using it, going pretty good so far!
    • Ask: Improve the interface, it's tough to navigate
  • 2531 - Like: whole interface, features, alliance selection
    • Ask: Between regionals, set up different rosters for different events
    • Ask: Be able to preplan what events you're going to
    • Ask: Enable use of temporary accounts for a single event
  • 3006 - used in the previous year, not this year
    • Ask: needs offline (we then explained about Voyager)
  • 456 - Love: It’s better than Fires; SR easier, more depth
    • Ask: Can we blend data? Fires blends data, good for sanity checking
  • 8576 - Love: worked so much better, versatile, dispersed scouting
    • Ask: Make it easier to change the pit scouting questions
  • 5584 - Love: fantastic! like the drive team dashboard
    • Ask: Had issues with bad cell (mentioned Voyager, they hadn’t had time to kick the tires)
    • Ask: Could we browse by event? (mentioned the new “browse” link which newly enables browsing by event)
  • 8738 - Love: scouting was the differentiator, enabled playoffs success; tablets have been huge! “I love it because I see the results” (from one mentor who works for Salesforce)
  • 1899 - Love: all the data you can see at once
    • Ask: Can it be even more optimized for a phone? There is so much info, it’s hard to use on phone e.g. all team metrics
    • Ask: Be able to record auton paths
    • Ask: Can we improve navigation? it is tricky
    • Ask: Can we publish a feature road map?
  • 5895 - Love: like data visualization, I can understand what's going on
    • Ask: Enable fixed scheduling, being able to assign people specifically
  • 1912 - Love: so awesome, we love it, very user friendly, I figured it out the first time; This is the first year we did scouting
    • Ask: JSON file building via WYSIWYG / drag and drop interface.
  • 7166 - Love: information you get from it (provided we put good data in), we use alliance selection the most
    • Ask: 'Can you make me read the docs?' 😆
    • Ask: Can we provide multiple quick YouTube videos walking through individual stuff
  • 5987 - One complaint, they had a problem where all the data got wiped out earlier. That aside, Love: liked it, using it this year, really good!
  • 8513 - Love: All Team Metrics
    • Ask: When assigning, could assign specific people? interfered with pit crew, time control
  • 6002 - Love: fav, so easy to assign something, still allows anybody to cover
    • Ask: Why only show 15 matches in the scouting dashboards?
    • Ask: Why didn't the scouting dashboards refresh? (make it clearer when/if the FRC events data flow is offline)
    • Ask: Pull in OPR and EPA
  • 245 - Love: it's been really helpful, we didn't bring our scouting team, like the radar
    • Ask: Ability to do direct comparisons, simulated alliances
  • 9717 - Love: really simple to use very easy; no wishlist items (!!)
  • 9023 - Love: pretty easy to see, easy to collaborate, provides really drive team dashboard
    • Ask: record auto paths, order (main reason they used Lovat)
  • 68 - Love: pretty good season with it; Voyager worked after reading the docs
    • Ask: Multi scouts in the same organization, average, pull more scouts in
  • 1250 - Love: Drive team dashboard absolutely amazing, alliance selection & data, also awesome
    • Ask: Ability to +/-5 on alliance data
    • Ask: Multiple scenarios in picklisting
    • Ask: Optional to hide rankings/predictions/etc (no spoilers mode)
    • Ask: When fewer students, make it easier to teaming up with teams, do data sharing, yet still having individual picklists
    • Ask: Custom charts

…plus several new teams, very enthusiastic but not yet having feedback 🙂

scoutradioz/programming/planning.txt · Last modified: 2024/08/16 12:35 by moconnell@team102.org

Donate Powered by PHP Valid HTML5 Valid CSS Driven by DokuWiki