...
Sketch | Storyboard | Learnability | Efficiency | Design Issues |
|---|---|---|---|---|
| Bob would read through his news items using this interface. He would use his 2 fingers to scroll up/down looking at the news items. he could use tap on the "star" buttons to quickly mark items as significant, and "share" buttons to share the items in the feeds he made available in Hubbub (like Facebook or Google+). The items would be "cut off" if they are too long, so Bob would have to tap them to expand them or shrink them accordingly. | This interface is very similar to ones people already use to view information (Twitter, Facebook, reddit, etc.). In addition this format is very common for phones, so Bob will have little trouble learning how to go through his news items. | If he wants to mark a large volume of items (such as read or read later), it will not be easy or quick to do here. | There is nothing on this interface that explains how to mark something as read later. This is a preliminary sketch, so it is missing some buttons. Also, it is not clear how to mark items with a tag different from the "star" button. |
Filter Items
Sketch | Storyboard | Learnability | Efficiency | Design Issues |
|---|---|---|---|---|
| To use this filtering interface, Bob would have to mark all of the programming posts manually and in advance with a tag (like "cool code" or something). If Hubbub could infer the pattern the design would match our scenario. | This interface is very easy to use. There are only items and check boxes, so Bob can quickly and easily try out some of them to see what they do if he's not sure. | This is extremely inefficient, because it only filters on things you've already tagged, aside from what sources to include. | We add added this design to show that this idea may be is too narrow on its own for adequate filtering for our user population, and we will still need an advanced search option to give users more control if we decide to implement this. |
Save Items
Sketch | Storyboard | Efficiency | Design Issues |
|---|---|---|---|
| This is an example of a popup menu that would appear after hitting a save button on the page. Here, Bob's previously created/used "save" tags are displayed to make saving faster. Since bob has categorized code-related items before, he will already have a "code-related" tag of some kind. This would just be a special tag that makes sure items don't get deleted. For example, if we add options for the user to delete items that have been around for a long time (month or something), items with the save tags would be ignored. | This is pretty efficient. Bob could save an item in 2 taps on his phone using an existing tag. As the list of save tags list grows, we can allow scrolling/arranging options for the save tags to speed up the search for the correct tag. | There isn't a new way to add a save tag drawn in this sketch. That was an accident. |
...