...
screen 8:
learn: only a few controls, each labelled appropriately. shows size of data
eff: all on one screen
vis: checkmark by what you are including. size of file changes to report those changes
err: can readd things you remove, once you hit send you can cancel the sending of the file. you can always restart this dialog from the review races screen
Design 2:
Screen 1: Upon startup, the user sees a map with the locations of each of his/her races highlighted. There are buttons to zoom in on the current location and to go to options. Multitouch gestures are accepted. 
Screen 2: When zoomed into a location, the user can see old races (and their titles over the start points), as well as a button on the current location to start a new race from the current location. 
Screen 3: Once the user clicks on "new race", he/she sees a list of the recently used race screen configurations. If the user wants, he/she can choose one of those for the new race or create an entirely new configuration. 
Screen 4: The configuration editor screen allows you to move around panes of information and add/remove specific plots or pieces of information from the race screen. Once the user is set, he/she can start the race. 
Screen 5: Once the race starts, the chosen configuration screen is no longer editable and begins showing data. 
Screen 6: When the user is done with the race, he/she sees a summary of the race. Once a user is done, it returns to the main screen (large map with all races shown). If a user clicks on an old race, he/she sees this same summary screen. 
Screen 7: When the user presses playback on the summary screen, he/she is shown this screen. It shows the editable race configuration screen, but with added playback controls so he/she can play/pause and scan forward/backward through the race data. He/she can also add/remove plots of data while the race is playing. 
Design 3:
This is the home screen of our tab-bar interface. This is where victoria can select a new race or to replay an old one.
...
Er: No errors can occur on this screen. Simple login box can be erased at any time, and tab-bar lets users navigate backwards at any time
The second page is for configuration of the race after victoria has chosen to start a new race. This pane features a number of toggles, to select what data she wants to be visible to her during the race.
Pre-Race Config (#2):
L: Familiar on/off switches used in iOS on other apps. Buttons and control are all at the bottom (a little non-standard, but there are no other options)
...
Er: User can easily undo any selection made
If she wants to select a ghost trail to follow, similar to our other implementations, she will scroll through a list of saved trails as a pop-up from the second tab-bar item 
Choose Ghost Trail Page (#2.5):
...
Er: Has a cancel/confirm button pane, so any choice the user makes will be reversible.
This is the next tab screen that she encounters, featuring a button to start and stop the race once she has configured the page. Here is where all the data will be displayed in real-time
During Race Page (#3):
L: All columns are aligned with the title of the data type displayed to the left of the value. No options to change on this page
...
Er: Errors in arrangement of data can not be easily corrected. The user must navigate to a previous page to change these options
Once she saves the race, or if she wants to view a previously recorded race, she will navigate to the fourth tab-pane, and chose the race from the scroll menu that appears.
Select a Race to Replay Page (#4):
...
Er: Very easy to reverse selections with cancel/confirm and simply by returning to this page to select again
This screen should appear virtually identical to the live race page, but is replaying an old race and features a play/pause button, fast-forward, and rewind
Replay Race Page (#5):
L: This page is nearly identical to the "During Race Page" again with the necessary labels to help the user know what page he or she is on
...