Versions Compared

Old Version 31

changes.mady.by.user Timothy R Schoen

Saved on

compared with

New Version 32

changes.mady.by.user Unknown User (ardama@mit.edu)

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  • Learnability
    • A lot of text is required to explain actions
    • Long presses are hard to discover, as is dragging between points
  • Efficiency
    • Long presses and dragging are efficient and fast to use if you know they're there
  • Safety
    • Adding or removing a landmark from the filter is easily undone
    • When dragging between landmarks, it might be easy to make a mistake, but again this is direct manipulation so it is easily undone

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

Screen #1 - Basic homescreen showing the user main uses of the app
Screen #2 - When finding a new tour, this is the first screen the user will see.  Allows them to input their starting location manually or to use their current position.

Image Added

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).

...