...
- We have two mechanisms to save content for later. The first is to hit a "Read Later" button that causes items to show up again in a later session. The second is a set of tags that users can apply to items, and later search for, similar to Gmail. One user mentioned that she would save emails often since she doesn't want to reply to them on the phone, and suggested that hitting "Read Later" on an email mark it as unread, which would be desirable to users who use both Hubbub and their email clients to read emails.
- When the user hit "Read Later" we changed that button's caption to "Saved". Some users thought that "Saved" didn't fit their mental model (emails are already "saved") and suggested removing the item from the list. We might go a step further and make the gesture for reading later be swiping the item off the screen, similar to dismissing notifications on Android.
- Tagging went smoothly for most users. They realized that they should check the tags they want and then hit "Save" to save or "Cancel" to abort.
- We didn't ask users to create new tags, but they did recognize that there was a textbox at the top and one user created a tag anyway. That user did not realize that they had to press the "New Tag" button for their tag to be created.
- One user noted that it wasn't clear how to rename a tag. It is, in fact, impossible with the current interface, something we may need to fix.
Filtering
- Several users took more time
...
- on the filtering task than they did
...
- on the other tasks, partly because the task itself is more complex.
- The filtering interface
...
- went through the most changes in the iteration step. In the initial design, users got to the filtering interface by switching tabs at the top, but most users were confused and took longer than we would have liked to find
...
- the "Filter" tab. When we replaced it with a button,
...
- users learned the interface much more quickly.
- Some users didn't immediately understand what the advanced filter options referred to
...
- . On paper the "Advanced Filter"
...
- text surrounded by what were supposed to be disclosure arrows looked more like a header than a button. Since our task required using an advanced filtering option, users were slow to complete it. One user who couldn't find the "has a hyperlink" advanced option added "http" as a keyword search instead, which was creative and may have been as effective.
- Some users asked for ways to preview the results of their filter,
...
- showing filter options
...
- alongside the items in the reading interface.
- Before the
...
- our design iteration, users were confused about how to
...
- apply or save
...
- their filter. After we made the buttons more prominent
...
- , users figured it out quickly.
Observations
User | Tom's Notes | Rahul's Notes | Leilani's Notes |
|---|---|---|---|
User 1 | computer |
| --user wants email marked unread when hit “read later” |
User 2 |
| computer? | --User was unsure what “read something interesting” meant (didn’t try to expand any of the information in the list, just tried to read them as is) |
User 3 |
|
| computer |
User 4 |
| computer | --clicked on gmail “icon” directly, rather than the email content |
User 5 | computer |
| --I only have half the notes for this test because I was working on RS2 testing for a bit |
User 6 | computer |
| --user’s first comment was that our interface is very busy |
...