GR3: Paper Prototyping

Prototype Photos

Opening Screen

This is the screen the user first sees when the application starts.  The crossed-out line is a result of our design iteration.

New Race Screen

This is the screen that appears when the user wants to record a new race.

Save race screen

Once the user stops the recording of a race, he or she is prompted to save the race.
Select a recorded Race

If the user wants to select a saved race to follow or playback, this screen appears.

Description of a recorded race

This is the screen that describes a race that has been recorded.  The buttons on the right take the user to detailed plots of the data recorded, and the buttons on the bottom allow the user to replay a race as it was recorded, or record a new race following the recorded path.  

Briefing

Scenario Tasks

1. Set up a new race
2. Set custom settings:## Toggle voice recording "On"
   1. Add notes
   2. Re-order data based on importance for this race (e.g. splits are less important, so place this datum at the bottom)
3. Set to race mode to observe race data hands-free while race is going
4. Stop and save race data after race has finished
5. View recorded race data after the race has finished

Observations

Listed below are the most important observations we made during the testing sessions, reformatted for easy reading:

1. None of the users realized that dragging and dropping rows of information on top of each other would result in combining the two pieces of data into a “scrolling row” which would show both rows over time.
2. Our concept of ghost trails is confusing; even actual rowers didn’t realize what they meant. Some users thought that ghost trails would make your race not actually be recorded, others thought that it would cause an old race to be replayed in the map row.
3. Some users were annoyed that they had to reenter a race’s name when they finish a race.
4. Most users didn’t know how to get the controls onto the screen after they faded away (this is during playback). Some users figured it out by pressing the screen, others just ignored the playback features.
5. One user was confused about the “Back” button on the race summary page, since this screen is invoked immediately following a race’s completion; the user thought that it would return him to the race, instead of going into the “completed race selection screen”. The same user thought that the “Stop” button on the playback screen would have the same result as the pause button in the playback controls.
6. Every user thought that a rower should see a countdown to the race start after pressing “Begin Race”, since in a real race the user would have to press the button, then pick up the oars and race.

Prototype Iteration