The team profile will require a Google/Android account to log-in with. This would be a parent account for teams, so there should be functionality for teams to create branched/linked accounts. Then from there, students would add themselves to the parent account and create their own account. This would not only allow all scouting data to be accessible to the parent account, but it would provide them with the ability to keep track of the scouts. Finally, the profiles will allow teams to oversee scouting for their whole team. They can create settings that can be pushed to the child accounts, and they can add preferences for functionality. They could also upload their team colors and profiles to customize the app.
How can we break this up in to smaller chunks of work? For example, we could support team colors without needing to sync that to the cloud, and add syncing later
One core consideration for this app is that we need to be offline-first. Not all venues have WiFi available, so whatever we build will need to be able to work offline as well
As we starting building this out we should also make sure we are considering ease-of-use. What does management of all these accounts look like? Where can we simplify the process or add value to support additional complexity?
The team profile will require a Google/Android account to log-in with. This would be a parent account for teams, so there should be functionality for teams to create branched/linked accounts. Then from there, students would add themselves to the parent account and create their own account. This would not only allow all scouting data to be accessible to the parent account, but it would provide them with the ability to keep track of the scouts. Finally, the profiles will allow teams to oversee scouting for their whole team. They can create settings that can be pushed to the child accounts, and they can add preferences for functionality. They could also upload their team colors and profiles to customize the app.