Versions Compared

Old Version 31

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

Saved on

compared with

New Version 32

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

Saved on

Key

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

...

Task

User Interview and Observations

Learnability

Efficiency

Safety

View friends

 

 

 

 

Create a LocaShare

 

 

 

 

Edit a LocaShare

 

 

 

 

LocaShare overview

All the users looked at the home screen for a long time to figure out how
to find the overview. They did not realize that the photo was clickable.
One user explored the map because that user thought that it indicated
the overview information of users that were able to see that user’s
location. This user then tried visiting the friends page and asked if the
user had to navigate to all friends pages to determine who all could see
this user in a particular location. Once at the profile page (after being guided
there), they were able to spot the “LocaShares Overview” button and knew
what that meant.

Found the overview pages easy to use. One user discovered a system error
when that user found a few locashare names that weren’t states listed in
the “States” tab. There was another system error when a user tried navigating
to the home screen from the overview pages using the home icon in the header.

 

 

* Photo on home page does not
give the affordance of clicking
or being a link to view the profile.
* The location of overviews did not
match the mental model that users had.

* Users mentioned that a lot of 
steps were necessary to accomplish 
this task.


* This task did not involve any updates 
to the state of the system and therefore
no safety measures were necessary.  

Reflection:

  • Different group of users have different mindsets in using an application. How to make the app intuitive to all users is hard. Therefore, how to make the app easy to learn and easy to understand becomes important since it is nearly impossible to make an app cater to all the people.
  •  It is hard to hide system implementation from design. Programmers are used to “programming language” and sometimes this makes the app not speak user’s “human language.” For example, we used to have “latitude, longitude” to express user’s current location.
  • The tradeoff between implementation and design. Good designs might sometimes entail hard implementations. In this course, we don’t have many chances to do prototyping on implementations, therefore, even though we had some really nice design features in paper-prototying, we were unable to carry it out due to implementation limitation. This also makes us deviate from our previous design and produces immature features.