A scoring application for long-distance motorcycle rallies. The application requires a password specific to the event you are riding. It also requires you know your assigned rider number and a code for that rider. Once that is applied, you may use the app. For those testing the app, in the instructions button on the title page, there is listed in there a generic password, rider number, and rider code you can use to test the app outside an participation in an actual event.
What is the purpose, target audience, and features in my app?
Long-distance motorcycle rallies are essentially complex scavenger hunts on motorcycles. Riders are given a list of locations they can visit. Each location has a different amount of points. There is physically no way to visit all the locations within the time allotted for this picture hunt so the rider must pick the best route they think they can ride and still gain the most points.
The rider earns points by taking pictures of some specific item at that location. It might be a statue, a building, a historical marker, or anything of interest. The rider then sends that picture to someone on rally staff who will either grant or deny points for that rider for that bonus.
The app facilitates this process. First, the info screen allows the rider to designate which event they are rider by putting in an event password. Second, they denote their assigned rider number. To keep riders from 'accidently' using someone else's rider number, there is also a rider specific code that must be entered. Then the system identifies their name and what their scoring color (scoring is broken up so as to not make one scorer not have to do much work). It also let's them put their email in so that they get a copy of the response they send.
The scoring function let's them take a picture and pick a bonus code number. They can then send that picture to scoring via an API through Airtable. The claim screen shows the rider what they've submitted thus far.
It's supposed to make it easier than emailing in the information and this information in the app is more readily available than flipping through emails to find something you took a picture of.
What is the purpose, target audience, and features in my app?
Long-distance motorcycle rallies are essentially complex scavenger hunts on motorcycles. Riders are given a list of locations they can visit. Each location has a different amount of points. There is physically no way to visit all the locations within the time allotted for this picture hunt so the rider must pick the best route they think they can ride and still gain the most points.
The rider earns points by taking pictures of some specific item at that location. It might be a statue, a building, a historical marker, or anything of interest. The rider then sends that picture to someone on rally staff who will either grant or deny points for that rider for that bonus.
The app facilitates this process. First, the info screen allows the rider to designate which event they are rider by putting in an event password. Second, they denote their assigned rider number. To keep riders from 'accidently' using someone else's rider number, there is also a rider specific code that must be entered. Then the system identifies their name and what their scoring color (scoring is broken up so as to not make one scorer not have to do much work). It also let's them put their email in so that they get a copy of the response they send.
The scoring function let's them take a picture and pick a bonus code number. They can then send that picture to scoring via an API through Airtable. The claim screen shows the rider what they've submitted thus far.
It's supposed to make it easier than emailing in the information and this information in the app is more readily available than flipping through emails to find something you took a picture of.
Show More
