Rambl: Hi-Fi Midway Milestone

Skip the obvious. Travel with Rambl.

Problem: People have a hard time finding the interesting and unique experiences when they travel, and often stress that they aren’t spending their time wisely or regret what they chose to do. Solution: Gamify the discovery of nearby, out-of-the-ordinary places exactly when you need them, called footprints. These footprints are sourced from other players, and further curated based on your preferences and behaviors into itineraries, or paths. Collect Rambl points for different actions and trade them in for real dollar rewards!

Today’s Agenda Heuristic Evaluation Results: App Navigation & Content Clarity Overview of Revised Design Implementation Update Demo

Heuristic Evaluation Results: Level 3 Issues 32. H6. Recognition rather than recall On the page when leaving a footprint/review, app asks the user “what type of activity was it?” even though the system should already know given that user had to choose the “activity” before the Rambl began. Fix: Remove this question from task flow 45. H3. User control and freedom There does not appear to be a way to cancel a Rambl while rambling. Fix: Insert a cancel button to allow user to exit rambl.

Heuristic Evaluation Results: Level 4 Issues 5. H2-3: User control & freedom: Unable to return to the previous page after clicking the hamburger menu. Fix: Add a return option from the main menu. 8. H2-10: Help and documentation: On the “Stomp Progress” page, it is unclear “7 out of 10 footprints” referring to only current itinerary or historical itinerary. Fix: Reword progress bar description for clarity 16. H2-2: Match between system & real world: It is unclear “Add friends” is a clickable button. Fix: Use a different design to signal button function

Overview of Revised Design App Navigation: From Heuristic Evaluation feedback, app needs improved navigation. Removing home screen and hamburger menu and adding navigation bar at the bottom that will always be exposed to user. Navigation bar will include: Previous Rambls (Including Friend Rambls), Current/Create Rambl, Stakes/Points Page, and a Profile Page w/ Settings ( “settings” tab that will include all other menu items that are not often used.) Backward and forward navigation between different screens will be secure and clear Key Term Clarification Clarify the stomp and stake process and its inherent risks by making the UI more informative. Show user progress more clearly, providing an overview screen to show previously stomped and boosted locations. Update the Stomp footprint page to be more intuitive: include description of what progress bar details, and tie stomps/stakes to an overview screen accessible from the main nav bar Add details to an FAQ screen that will show the first time a user launches an app

Prototype Implementation status Tools Being Used: We are using React to build our mobile app using JavaScript, composing mobile UI from declarative components Implemented Features: We built the app navigation infrastructure to enable user to move between different screens. We finished implementing Task Flow #1: Get a curated itinerary.

Unimplemented Features and Plan to Finish Create Stomp / Boost Stomp Workflow (2 day) Stomp Overview Page (3 hours) Footprint remaining tracking in ongoing rambl flow / Mark Footprint as visited in Rambl Ongoing screen (1 day) Friends list on Profile Page (2 hours) A lot more styling! Decisions about page naming (History vs Past , Current vs Create) FAQ page explaining vocabulary ( 2 hours) Task Flow 2 (3 days) Task Flow 3 (3 days)

Limitations/tradeoffs We hard-coded the following parts of the prototype. App does not have user location detection capabilities. Thus, we assembled list of dining and amusement options in major cities that a potential user could visit and provided those dining and amusement options in test user’s rambls. App does contain a database of imaginary friends to an initial test user and these imaginary friends have past rambls that the test user could follow. To demonstrate the “add friends” function, app contains a contact list of imaginary acquaintances the test user can choose from.

Demo