Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Migrated to Confluence 4.0

Prototype Photos

This is the toolbar shown at the bottom of every page.  It allows quick and easy access to the four main pages: Workouts, Groups, Input Times, and Data.

Image Added

This is our calendar page, used in several of the tools.  It serves to help you pick and plan workouts and is an effective and safe visual tool.

Image Added

Workouts

An example of the workouts page.  Here you can select a new workout, or edit the existing workouts.  The section in the center is a pop-up for creating new workouts.

Image Added

View Data

This is an example of a selection screen with drop down windows.  The date selection range at the bottom takes you to the calendar page. 

Image Added

This is our chart page, where users can chart the progress of their athletes over time, as well as compare athletes against each other.

Image Added

Input Times

This is an example of our workout selection page:  This will take you to the stopwatch page once you make a selection.

Image Added

This picture is of the first stopwatch page that we made.  The icons at the bottom of the page are present on all pages and serve as a navigation bar.  (They are omitted from the other images to save space.)  Image Added

This is our improved stopwatch page, where we removed the stop command and moved the start command up to the top of the page, closer to the instructions.

Image AddedPLACE PHOTOS OF PROTOTYPE HERE
TODO

...

Briefing

"This is Forward Strides. The purpose of this interface is to assist in the process of inputting and viewing athlete performances and workouts. It is primarily for coaches, specifically in those sports with time-based performances (track, swimming, speed skating, etc.). Here are your tasks."

...

  • People liked the 4-item menu bar at the bottom of the app, as it was simple and looked nice
  • Though there was room for improvement regarding its learnability, once people understood the timing mechanic mechanism (tapping an athlete's name to take down his/her time), people liked the concept and implementation

...

  • When viewing a graph of past performances, how do we show multiple repetitions in a workout? IE. Joe Bish has 2 repetitions of the 1 mile swim during the workout on March 18th. Do we put 2 data points, 1 average data point, other solutions?
  • What does the performance graph look like with multiple peopleathletes, multiple workouts?

...

Prototype Changes

  • Changed the collapse/expand arrows from up/down to right/down. This removed confusion about what the arrow represented and is more consistent with other applications the user may have seen
  • We moved the stopwatch buttons from the bottom of the screen to the top of the screen under the timer itself. This way users quickly associated the timer and its controls with one another, and the vertical flow of the page required the user to read the text below
  • Greyed out name buttons during the timer page until the timer is started, preventing users to arbitrarily click user names beforehand
  • On the view performance "View Performance" page, instead of clicking a group and having it pop up a list of athletes, changed this to a collapse/expand section. There is a checkbox and a button "Select all" on the group header to allow selection of all athletes in the group quickly. If all athletes are manually checked, the group checkbox is also checked to indicate the entire group is selected
  • Changed filter at the top of the graph page to be less obstructive
  • Reworded some headers to be more consistent with our structure (Select Group(s) to Select Athlete(s) on the view data tab)