team random medium fi prototyping
play

*TEAM RANDOM* Medium-fi Prototyping NYLAH AKAAR ALEMA OMARI - PowerPoint PPT Presentation

*TEAM RANDOM* Medium-fi Prototyping NYLAH AKAAR ALEMA OMARI Value Proposition: Random runs youll never get tired of Problem: Running the same old routes can get boring and sap a runners motivation to exercise, leading them to quit.


  1. *TEAM RANDOM* Medium-fi Prototyping NYLAH AKAAR ALEMA OMARI

  2. Value Proposition: Random runs you’ll never get tired of Problem: Running the same old routes can get boring and sap a runner’s motivation to exercise, leading them to quit. Solution: Run randomly generated routes to spice up your exercise life. Bookmark cool locations you pass for future reference, throw some body-building workouts in to spice up your run, and connect with other runners out and about.

  3. 3 Tasks

  4. Task 1: Go for a fun run (moderate) Task Description: ● Run on new and exciting paths ● See interesting sights and landmarks along the way ● Program random workouts to do along the way Changes from low-fi: ● Allow users a preview of run area before starting for safety ● Make random workouts more optional for power users ● Changed from simple to moderate task

  5. Task 2: Get real time updates on your workout (simple) Task Description: ● Check your current stats (pace, time, distance, elevation, etc.) ● Get recommendations for how to improve your performance and build your perfect workout Changes from low-fi: ● We decided to focus solely on giving stats as opposed to offering recommendations for improvement ● Changed from moderate to simple task

  6. Task 3: Bookmark locations and revisit after run (complex) Task Description: ● Save landmarks, businesses, and places that you pass along the route for future reference ● Get directions to saved locations for later enjoyment Changes to low-fi: ● Allow users to save custom locations ● Instead of having users simply navigate back to the location, we’ve changed saved locations to let users re-run routes featuring that location

  7. 3 Design Changes

  8. Before After Design Change 1

  9. Rationale From feedback we received, we realized that after entering the miles and destination for a run, users would expect to immediately start running. Because of this we rearranged the home page to kick off the run immediately, with a small link beneath the RUN button for users to further customize their workout. There was also confusion during our user testing about what to input in the destination text box, so we changed the destination to be button options for “round trip” and “one-way.” If a user selects one-way, a text box will then appear beneath the button for a user to enter their final destination.

  10. Before After Design Change 2

  11. Rationale Since we modified our home page to allow users to immediately get to running, we decided to make the run customization page an optional link for users to click on, as opposed to a required part of setting up a run. This change came from feedback in user testing, where we noticed that most users opted out of customizing their workouts, selected “no” for every option, and just wanted to start running. In our new, optional customization page, we also change altitude to hills since users were confused what to input for altitude. We also made an aesthetic decision to arrange the exercises into a box that users could click on, as opposed to a long list of exercises for them to check “yes” or “no” to.

  12. Before Design Change 3

  13. After Design Change 3

  14. Rationale There was a lot of confusion surrounding our saved locations feature in user testing and during section presentations. We ultimately discovered that users would rather see past runs that featured a save location and go on that run again (or a new one) to revisit the place. We therefore changed our original design, which simply opened Google Maps to lead people back to a saved location, to our new design which will show the past run histories of each saved location, as well as popular routes that feature that location. In the past run histories, we decided to include the date, stats, and map as users expressed the desire to reminisce about past runs and also have the ability to run again.

  15. Task 1: Moderate flow Go for a fun run!

  16. Enter the number of miles to run

  17. Select one-way to enter an end destination or stay on round trip

  18. Optionally customize your run settings

  19. Click run to get a preview of your route and then start running!

  20. Afterwards, get a summary of your run and rate the route

  21. Task 2: Simple flow Get real-time stats on your workout!

  22. During your run, click the stats button to view current stats

  23. Task 3: Complex flow Bookmark locations and revisit after the run!

  24. While running, the app provides the user with interesting locations that they pass. The user can say “bookmark” to add that location to their bookmarked locations. (Limitation: couldn’t represent voice command)

  25. Navigate to bookmarked locations in the hamburger menu

  26. Click on a bookmarked location to see your past runs and popular public runs that include the location. Click run again to rerun an old route to the saved location.

  27. Prototyping Tools We used Figma to create our medium-fi prototype. It was great using Figma because it was full of features that allowed us to make iPhone screens easily. There were tons of features to make quasi-buttons and professional looking screens. The tool also allowed all four of us to work together in real-time which was nice. The only real issue we had with Figma is that we could not figure out how to make our own icons for our prototype.

  28. Limitations/Tradeoffs of Current Prototype For our current medium-fi prototype, limitations are that we cannot use this in a real scenario because it only simulates one case. Features in the hamburger menu do not work currently, with exception to ‘Bookmarked’. The ‘Customization Workout’ screen also does not allow to select ‘Yes’ or ‘No’. Additionally, we have not yet implemented voice-interaction in this current prototype, but will do so in the next iteration. For example, the user currently cannot bookmark a location because that is a voice-interactive feature. Also, we have multiple runs saved under our ‘Bookmarked Locations’, but only the run dated Oct. 15th is implemented. Other than those features and full-functionality, this medium-fi prototype should support a general use case from start to finish.

  29. Wizard of Oz Techniques and Hard-Coded Features In this medium-fi prototype we used no Wizard of Oz techniques or hard-coded features.

Recommend


More recommend