...
- One user suggested that hitting "Read Later" on an email should mark it as unread: 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 recommended making items unread when they are set to read later, which would be desirable to users who use both Hubbub and their email clients to read emails.
- Seeing "Saved" after hitting "read later" didn't fit users' mental models: When the users hit "Read Later" we changed that button's caption to "Saved". Some users thought that "saved" didn't make sense (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.
- One user did not realize that they had to press the "New Tag" button to save a new tag: 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 didn't realize the "New Tag" button needed to be hit in order for their tag to be created.
- It wasn't clear how to rename a tag: One user noted this during testing. We realized then that it is in fact, impossible to rename a tag with the current interface. This is 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.
- most users were confused and took longer than we expected to find the "Filter" tab: The filtering interface went through the most changes in the iteration step. In the initial design, users got to accessed the filtering interface by switching tabs at the top, but most users were confused and took longer than we expected to find the "Filter" tabhad trouble finding the tab in the first place. When we replaced it with a button, users learned the interface much more quickly.
- Our "Advanced Filter" options button looked more like a header than a button: 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 wanted to preview the results of their filter, showing filter options alongside the items in the reading interface.
- Before the our design iterationInitially, users were confused about unsure how to apply or save their filter. After we made the buttons more prominent in the updated prototype, users figured it out quickly.
...