...
Sketch | Storyboard | Learnability | Efficiency | Safety |
---|---|---|---|---|
Initial sketch: | This is an example of a menu that would appear after hitting a save button on the page. Here, Bob's previously created/used "save" tags are listed 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. | 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 1 tap on his phone using the default menu values. As the list of save tags grows, we can allow scrolling/arranging options for the save tags to speed up the search for the correct tag. | The item Bob is trying to save is displayed to make sure he's saving the right thing. |
...
Sketch | Storyboard | Learnability | Efficiency | Safety |
---|---|---|---|---|
Initial sketch: | With this interface, Bob is brought immediately to the first item in his feed. He goes from one item to another using the next and previous buttons. He saves and shares items using the "save" and "share" buttons. He can mark things using the "tag" button, which would open a new (maybe popup) menu. |
|
|
|
...