Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Sketch

Storyboard

Learnability

Efficiency

Safety Design Issues

Bob would read through his news items using this interface. He would use 2 fingers to scroll up/down looking at the news items. he could 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.

Items would be marked as read automatically as he visits them.

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.

...

Sketch

Storyboard

Learnability

Efficiency

Safety Design Issues

To use this filtering interface for our above scenario, Bob would have to mark all of the programming-related posts from Google+ manually and in advance with a tag (like "cool code" or something). If Hubbub could infer the this pattern, the design would match our scenario.

We realized while analyzing this sketch for Design # 1 that this design 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.


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 added this design to show that this idea 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

Learnability

Efficiency

Safety 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 fasterlisted in the first drop-down menu. Since bob has categorized code-related items before, he will already have a "code-related" tag of some kind in the list. 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.

If Bob wants to see these items again, he just has to specify he wants to see items with the "code-related" save tag under filtering. , when he goes back to read them. Then he can read them again using the reading interface.

There will be a "new tag" entry in the first drop-down menu, so Bob can specify a new save tag if the current list of tags don't suit his current needs.

With this interface, he can also specify how long he wants items to be saved with the second drop-down menu.

It's pretty clear what is being saved. But Bob may not realize how to create a new save tag with this design. He would have to explore the drop-down menus to see what they do.

This is pretty efficient for saving a single item. Bob could save an item in 2 taps 1 tap on his phone using an existing tagthe default menu values. 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.

However, if you want to save multiple items, this is not an efficient way to save. We will have to look into options for bulk saving, if this turns out to be a necessary feature for our user population. There isn't a new way to add a save tag drawn in this sketch. That was an accident

The item Bob is trying to save is displayed to make sure he's saving the right thing.

Bob's save choices will remain visible after selecting items from the menus, so he can verify them before he hits the save button.

Design # 2

Read Items

Sketch

Storyboard

Learnability

Efficiency

Safety Design Issues

 

 

 

 

 

Filter Items

Sketch

Storyboard

Learnability

Efficiency

Safety Design Issues

 

 

 

 

 

Save Items

Sketch

Storyboard

Learnability

Efficiency

Safety Design Issues

 

 

 

 

 

Design # 3

Read Items

Sketch

Storyboard

Learnability

Efficiency

Safety Design Issues

 

 

 

 

 

Filter Items

Sketch

Storyboard

Learnability

Efficiency

Safety Design Issues

 

 

 

 

 

Save Items

Sketch

Storyboard

Learnability

Efficiency

Safety Design Issues