Paper Prototyping
Prototype photos:
|
|
|
 |
 |
 |
Main Screen. |
Screen showing an incoming call. |
Prompt window to view the location. |
 |
 |
 |
Interface for viewing the location. |
Interface for adding a comment to a location. |
Interface for viewing the notes. |
 |
 |
 |
Interface with multiple notes. |
Screen for viewing the tweets and links to the available
articles and maps. |
Safety prompt window asking for a confirmation to change the viewing
mode. |
 |
Image viewer. |
Briefing:
from Arjun's perspective:
Purpose of application: parents and friends can recreate narratives of the stories their loved ones tell.
- You are a father named Arjun.
- Your son is Raj, a college student at MIT in Cambridge, MA.
- You are to talk to Raj and would really like to visually recreate the stories that Raj tells you.
- You will be using your home desktop computer to talk to Raj.
- You will use a system called Teleport that allows you to visually explore spatial locations as well as look through images and tweets that Raj uploaded.
from Raj's perspective:
Purpose of application: parents and friends can recreate narratives of the stories their loved ones tell.
- You are a son named Raj, studying at MIT.
- Your father is Arjun lives in India.
- You are to talk to Arjun and would really like to communicate your experience of living abroad.
- You will be using your home desktop computer to talk to Arjun.
- You will use a system called Teleport that allows you to store and share your experiences.
Scenario Tasks:
Task 1:
Raj wants to show you where he goes jogging. Accept the call and view the comment that Raj made.
Task 2:
You want to show Arjun Charles River and add a comment.
Task 3:
You want to find out more about Yosemite Park. Check if Raj added pictures or tweets and look through them.
User testing observations (Round 1):
User 1:
Observations
- Users ignored panning and altitude controls.
- Some description elements mistaken for buttons.
Feedback
- Was not obvious how to exit a mode.
- Found the voice transcription natural in the context of application though generally the user does not like it.
- Got irritated with the pop up window.
- Suggested that direct manipulation with a mouse would seem more natural than using the provided controls.
User 2:
Observations
- Likes exploring the interface, testing different navigation controls.
- Had difficulty finding how to move from the image viewing mode to reading tweets mode.
- Does not move directly to address the task but takes extra steps to explore the interface. For instance instead of directly viewing the location, goes to the tweets tab first.
Feedback
- Suggested it would be easier if mode change buttons were located within the main active window, not only from the bar above.
User 3:
Observations
- Confuses navigate symbol for a button (bad internal consistency).
- Likes navigating, using different control buttons.
- When adding a comment is concerned if the comment was saved or not.
- Easily finds exit buttons.
Feedback
- Wished there were smoother transitions between high-level and low-level navigation.
For instance, when taking a street view low-level navigation seems more natural. However, our interface provides only high-level mode change controls.
- When hitting exit would like to see a confirmation that the comments added have been saved.
- Suggested that dragging with a mouse when exploring the street view would feel more natural than using some of the buttons we provided.
Feedback summary
Prototype iteration:
User testing observations (Round 2):
User 1:
Observations
Feedback
User 2:
Observations
Feedback
User 3:
Observations
Feedback
Issues to consider/resolve before moving forward: