...

The app is intended as a mobile app, most likely for a tablet, so when being viewed in a desktop browser, it is necessary (in order for the display/layout to make the most sense) for the browser window to be re-sized (drag the bottom right corner) horizontally such that the 5-item menu on the bottom spans the window horizontally (this will be about 768px across, like a tablet being held portrait). Use as much of the vertical dimension of the screen as possible (a standard tablet would have 1024px in the vertical dimension, holding it portrait).

What Works, What Doesn't

It is almost fully functional, but there are some exceptions.

The chart page does not display the results taken by the app. Instead it displays some fake chart. We thought this functionality was perhaps outside the scope of this iteration, and the important thing was the selection page just before. So clicking "View Results", inputting the data, then clicking "View Progress Chart", will bring you to a page that is static so don't worry about anything after getting to this page (except maybe the "Back" button).

As of now, modifying results of a workout is only possible by re-timing the workout. We suggest that there exists the functionality to modify the results from the Stopwatch manually, but that functionality will come later.

You will start out with no data (groups, members, results). This iteration of ForwardStrides uses LocalStorage (from HTML5) so when you modify things, such as adding groups, taking times, etc. they will be remembered on your computer. After opening up the Home page, you can begin by exploring the tabs at the bottom, adding groups, adding members to each of these groups, and creating workouts for these members/groups. When you have some groups, members, and workouts, you can start timing their results. That should get you started with a somewhat realistic scale of data (assuming this app is used for a single team of athletes).