...
User Test
| Critical Incidents/Quotes
| Design Learnings/Possible Fixes
|
|---|
User 1
| Add Contact
"Why is there a Barcode on my Identity?"
-Appreciated not having to physically type anything to trade contact info
"What does Verified mean"
-"Looks like my iPhone Contacts app"
Send to Contact
*-"*I like the icons"
-Felt slow to send a message -- Have to click through three screens before you can type
-Easily able to send messages and receive them
Receive from Unknown
"It's Red. That's bad Right?"
-Did not realize long press opens menu of options, had to coach user to find it
Remove Contact and Message
-Went to contacts app directly to delete user
-Surprised that messages were deleted also -- different from iPhone standard which leave messages behind | Add Contact
-Since the 'Barcode as my Identity' Concept is not that common, some guidance in the form of help or a tutorial animation could ease learnability.
-Linkage between 'Verfied' on Contacts screen and 'I know this person' on Contacts Editor is maybe not clear. Potential rewording for consistency.
Send to Contact
-Consistency to existing chat applications was successful
-Efficiency can be improved, on new messages we can directly go to the contacts list instead of the blank new message screen.
Receive from Unknown
-User was familiar with iPhone, not Android, so standard UI mechanism like Long Press were not as easily discoverable. Perhaps a button or alternate mechanism to display an additional function is possible would help learnability.
-Color coding was obvious and well received.
Remove Contact and Message
-Might want to further emphasize non-reversible behaviors, especially when they deviate from existing applications. This user removed message, even with the additional prompt, and didn't realize until late what it actually meant. |
User 2
| Add Contact
-Accidentily made new conversation first
-Got to barcode fairly quickly
-Accidentally made new conversation first
-Got to barcode scanner fairly quickly
Send to Contact
-Quickly created a conversation
-Quickly sent message
Receive from Unknown
<ac:structured -macro ac:name="unmigrated-wiki-markup" ac:schema-version="1" ac:macro-id="47ab5099-6500-4f27-8742-ef188d59d79f"><ac:plain-text-body><![CDATA[ -"I have no idea how to add [them] as a contact"
]]></ac:plain-text-body></ac:structured-macro>
-clicked on person to attempt to add (need long click)
-tried using add to conversation
-went to contact, then identity (basically searched everything)
-hard to be told to long click after a few minutes of hopeless searching--"how was I supposed to know that???"
Remove Contact and Message
-did quickly and efficiently
| Add Contact
-Seemed fairly clear to user
Send to Contact
-Seemed very clear to the user
Receive from Unknown
-This clearly needs to be changed in some way, it was very clear the user was never going to figure it out on their own.
-Maybe add a "+" button or other icon on any unknown people, in order to afford adding
Remove Contact and Message
-Seemed clear to the user |
User 3
| |
| Add Contact
- Immediately knew how to add the contact.
- Felt that the QR code was obvious and efficient.
- Confused about what a "knowing" a user meant. Thought that this was required.
Send to Contact
- Clicked on the person trying to start a conversation.
- Got it on the second try.
Receive from Unknown
- Clicked on the conversation to add to contacts. Didn't know that a conversation could include more than one person.
Remove Contact and Messages
- No problem.
| Add Contact
- "I know this person." is confusing. We should probably change the wording.
Send to Contact
- We should add a long-click menu to contacts to make them more consistent with the android contacts application.
Receive from unknown
- We might want to make the fact that something is a conversation more obvious. However, a single mistake with no side effects is acceptable when learning an application.
Remove Contact and Messages
- No problems.
|
Reflection
Going through the design process in a methodical way was very educational, and we could see the design evolving throughout. We reflect on the evolution of this design through each stage.
...
During the initial Analysis, it was instructive to think concretely about the tasks we wanted users to be able to complete. We ended up going back to you the task list multiple times for updates because the actual tasks necessary to achieve a users goals were simplified over time. We did a good job targeting specific user needs, but perhaps took on too much total scope for the purpose of this class looking back on it.
...
For the computer prototype we were attempting to get the barebones functionality working, as this was the first Android application any of us had worked on. It was a bit of a learning process, but it helped us get comfortable with standard design elements in Android, that were most likely created with usability in mind.
GR5 - Implementation
Architecting the application such that multiple people can work independently on certain sections is a huge help. Separating the UI from the backend allows both to be developed in parallel, and dividing the application into distinct section allows each one to be created independently.
...
Even with all the upfront work, user testing still yields new insights. We are not yet able to translate from English into . Given the feedback we have received, we have located areas where we can definitely improve. This definitely highlights how usability design is an iterative process that can go on indefinitely.