...
Currently, this design does not support recovering from deleting a bookmark or folder, but we hope to change this in the future (either a confirmation pop-up or something). However, because bookmark area is larger, it is easier to hit the correct bookmark and therefore the error rate is reduced.
Another bad part about error correction is that it is relatively easy to click on a bookmark, so once you click, it opens a new tab/window in your browser, making you have to close that to return to what you were working on.
Design 2
First time Nikola visits the page myweb.com, he sees this:
...
Because the interface is so simple, learnability should be pretty high. One thing unclear from just viewing the default labels and so on, is that user might not know what favorites or suggestions mean and represent. This could be solved by having a short introduction to the website when the user creates an account but we will leave it for further development later in the project. Everything else seem very simple, as long as user is aware of all of the possibilities. This will be particularly intuitive for safari users because our interface derived a lot from the safari view history option.
...
Visibility of the bookmark itself is very high because a big part of the browser window is used to display it. But if If we want to keep the labels spread out and visible, we need to limit number of labels. So in In this case, we are limiting the amount of labeling the user can do in order to preserve simplicity and visibility. Also, user doesn’t have the view of all bookmarks stored, so he needs to scroll through them in order to see them.
...
One thing that’s not currently recoverable is that if user deletes the label or the bookmark, which is not that hard, he deleted it forever and if he wants to recover it he has to go and add the bookmark again. Or even worse, he needs to go and label his bookmarks with the label again. It would be nice to have a pop-up to confirm that user wants to delete the thing or not.
Another bad part about error correction is that it is relatively easy to click on a bookmark, so once you click, it opens a new tab/window in your browser, making you have to close that to return to what you were working on.
Efficiency:
Even though the UI is pretty easy to use, it is not the most efficient solution. This design sacrificed a lot in order to achieve as high visibility as possible. If a user wanted to find a bookmark that was somewhere amongst the ones labeled as favorites for example, he would need to scroll down until he find finds it, instead of just clicking on the layed-out bookmarks, icons or similar. That’s not efficient, and that disadvantage becomes even worse with growing number of bookmarks. On the other hand, if a user knows that he’s looking for the 6.006 website, he can just start typing 6.006 in the search field which will display all the corresponding pages. In this sense, I we think search is very efficient plus it preserves visibility. This interface also doesn’t enable user users to label multiple bookmarks at once, so labeling the big library could be a very tedious job. On the other hand, once bookmarks are sorted and labeled, using this design could be very easy and pleasurable. :D
...
Analysis:
Learnability:
We feel that this interface is generally pretty good in aspects of learnability. The interface on the right left is somewhat similar to Gmail tagslabels, which the user might have seen. Furthermore, the tabbed browsing also likely provides familiarity for many users. The bookmarks themselves provide affordances (being boxed) that indicate that it is clickable. Some bad aspects of learnability is that it might be difficult to discover how to add or remove tag labels to bookmarks.
Efficiency:
This interface has both good and bad parts of efficiency. The search, for example, makes finding bookmarks very efficient. Adding a bookmark is also pretty efficient, as is switching between tabs. Adding tags to bookmarks, however, can be inefficient as you have to add tags individually to each bookmark.
Visibility:
Most of the screen real estate is devoted to showing the bookmarks, and pretty large images of it, so in that respect, visibility is good. Also, the most important labels and tabs are visible. Some bad aspects of visibility is that it might be hard to discover how to add tags to a bookmarkyou can only view the contents of one tab at a time.
Error Correction:
The most important part of error correction in this design is the tabbed browsing. If you are unsure of what you are looking for, you can open a new tab, search for what you want, and if you don’t find it, you can go back to the tab you were looking at. Another aspect is feedback during search that gives suggestions as you type. One bad part about error correction is that it is relatively easy to click on a bookmark, so once you click, it opens a new tab/window in your browser, making you have to close that to return to what you were working on. Furthermore, it is easy to open an extra tab for a different label/different shared person.
...
Learnability: The interface is very easy to follow, since it’s very simple. The starting page quickly points explains to the new user how to get going with the page with large input boxes for registration. Once in the user area, the hierarchy of folders,their content and the display page is very logical since it goes from left to right, from most general to least general. The interface is also quite easy to memorize since most things happen on a single page(with addition of a few pop-ups).
Visibility: The visibility of the folders and their content is limited by the size of the two separations “Folders” and “Bookmarks”, but that was a trade of off between efficiency and visibility, because the interface could have been designed to display the folders on the whole page which would allow it to show many more folders at one time than with the separations. However, when opening one of the folders it would lead you to another page with the bookmarks in it, and to view the bookmarks the user would have to go yet to another page and then have to come back by pressing a back button to get to where he started. However, having this separation allows the user to see several things at the same time, so it’s both good and bad vor for visibility.
Error: There are some big problems with errors. For example, the user might accidentally delete a bookmark when he was actually trying to change its URL since the URL and Delete button are right next to each other. In addition it’s very easy to forget to select a folder before trying to add a bookmark to it, and that would result in adding a new folder instead of adding a bookmark to a folder as intended. Also since the add and remove buttons are placed right next to each other, the user might end up removing a folder when they actually intended to add a bookmark to it. The simplest way to deal with this kind of errors would be to display “are you sure?” messages but since those are quite annoying for the users and would take away quite a lot from user satisfaction, so we have decided not to go that route for nowno. However, however, if during user testing the listed errors prove to be serious issues, we might end up deploying a lot of error prevention.
Efficiency: The efficiency is the strongest part of the UI since everything is happening in a single page, such as instantaneous search through both the bookmarks and all of the folders, selecting different folders and viewing their content, moving bookmarks from one folder to another, and even viewing some of the actual content of the bookmarks without having to load a new page of MyWeb. One bad aspect of efficiency is that you have to do three clicks to access a bookmark, and when doing that for your most common bookmarks, it could get very annoying.