...
- The first task description, "Read something interesting", initially confused some users who didn't realize they were being asked to try to scroll down or expand items. Changing the description to "Find something interesting to read" resolved this.
- Because it is a mobile app we tried to afford scrolling by displaying a partial line of content at the bottom edge, but some users did not realize that the page was meant to be scrollable.
- Users were able to notice the "Expand" button and click on it to expand items to see the full version. In some of the original tests, we didn't display a "Shrink" button on expanded items; users during these tests tried to touch the original menu to get back, similar to how you close a photo on Facebook. Some users did this even after we started showing the "Shrink" button - we could consider making clicking outside of an expanded item shrink it, though this could be another issue that comes up with a paper prototype.
- A couple of users hit the "Share" button. Ideally, this wouldn't require any additional effort, just that the user do anything more, and the backend would make the post in the background using an API. (Tom: what?)We might need to ask for additional input in some cases though, like email forwarding.
- Some users thought the interface was busy and suggested hiding buttons. When the interface is on a real screen we can better determine whether decreasing learnability by hiding the buttons makes sense.
- For the most part, users were familiar with interfaces that present a list of items to read, and did not have significant roadblocks navigating.
...