Scenario:

Local Linda has a friend from high school visiting her at college. She wants to show her friend around the city, but hasn’t done many of the “touristy” things herself. Linda uses Torch to find a good walking tour that hits many landmarks and they follow it over the course of the day. At the end of the day, Linda decides that there were a few landmarks that would have been better-suited for the tour, and creates her own.

Our Three Tasks: Find, Follow, & Form

1. Ways to find a tour

• Map displaying landmarks that the user can include & list of tours (clicking would go to map)
• Map displaying landmarks that a user can include, auto-generate tour based on that
• Map displaying possible tour routes & filter using a list of landmarks with checkboxes
• Some way to do search/filtering (slide-down, parameter search, etc).

2. Ways to follow a tour

•  Map view with current location and a route to follow (like an iPhone)
• Show you a picture of the next landmark with description, direction (like a compass)
• Ordered list of landmarks on the route potentially with a map (landmark #, picture, name) with the step you’re on, perhaps with a small map (like Winphone 7)
• Shows you the next step and then landmarks that are nearby/related/on the way

3. Ways to form a tour

• Modifying a tour by making changes while following
• Drag your finger in between landmarks on a map
• Drag-and-drop tour ordering
• Adding locations to a database, don’t specify tour route

Storyboards

Storyboard #1

• Map displaying landmarks that the user can include & list of tours that include those landmarks (clicking would go to map)
• Map view with current location and a route to follow (like an iPhone)
• Drag your finger in between landmarks on a map

Storyboard #2 

• Map displaying landmarks that a user can include, auto-generate tour based on that
• Shows you the next step and then landmarks that are nearby/related/on the way
• Adding locations to a database, don’t specify tour route

Analysis:

• Learnability
  • Unique icons for each type of location may not be implicit.
  • Finding detailed info by clicking on icons shown on map may not be obvious.
  • Ambiguity on "type" of location (Is a bar recreation or restaurant?).
  • Map areas behave as expected (no additional learning if already familiar).
  • Icons are used consistently throughout the tour process to solidify/clarify their purpose.
• Efficiency
  • User cannot see selected locations while choosing additional ones.
  • User cannot get an estimate on time/distance until all locations have been chosen.
  • Several different screens to navigate to add a location (home page -> map page -> location page).
  • Using map in substitute of address input saves time (starting spot, new location)
  • Hard to add a specific place if it isn't on the map (have to go to the "advanced search" page).
  • Finding a "subtype" of a more general "type" can be inefficient since each location has to be looked at individually (for instance, finding an authentic Italian restaurant among a wide variety of other restaurants). 
• Safety
  • Requires several deliberate button presses to add an event (good for error prevention)
  • Easy to remove unwanted locations
  • Directions to locations are not very detailed (just show the map, leaving potential for user to get lost).

Storyboard #3 

• Map displaying possible tour routes & filter using a list of landmarks with checkboxes
• Show you a picture of the next landmark with description, direction (like a compass)
• Modifying a tour by making changes while following

Storyboard #4

• Some way to do search/filtering (slide-down, parameter search, etc).
• Ordered list of landmarks on the route potentially with a map (landmark #, picture, name) with the step you’re on, perhaps with a small map (like Winphone 7)
• Drag-and-drop tour ordering

Analysis:

• • Learnability

• • • Simple, straightforward menu for picking parameters
    • Explicit markings for each stop, detailed descriptions
    • Map areas behave as expected (no additional learning if already familiar)
    • Icons are used consistently and may be already familiar to user
    • Ambiguity about how to drag and drop by long-pressing on a stop
    • May be confusing how to get back to main menu
    • Not clear what is clickable and what is not clickable

• • Efficiency
    • User cannot pick specific locations/not clear how to add location. 
    • User can easily switch order of stops if they know how
    • User can easily change mode of transportation from walking to car or vice versa
    • Very few screens to navigate
    • User can easily change tour time or parameters
    • Default tour parameters exist on menu (start: current location, tour: 1 hour, travel: walking, see everything) making it easy for the user to start
       
  • Safety
    • Requires several deliberate button presses to make a tour (good for error prevention)
    • Easy to remove unwanted locations if known how
    • Directions to get from one stop to the next are detailed and time estimates provided