...
1. |
| Homepage. |
2. |
| Private Editing Page.
|
2.1 |
| Save Dialog Box.
|
3. |
| Dashboard Page. |
4. |
| Collaborative Editing Page. |
Usability Analysis
Learnability:
- When the webpage is presented to the user, it tries to show affordances for editing by displaying section borders and the 'close' button on mouse over, but it is not obvious what editing tools are provided; the user has to click or select text in order for the editing buttons to show. A tooltip on mouse over saying 'Click to show edit options' may help, but may also be annoying if it is constantly showing and covering up the content of the webpage below it. A panel at the top or either side containing all possible editing buttons is another option that may improve learnability of the editing feature.
- In the collaborative editing mode, it may not be easy for the user to figure out exactly which part is not editable due to other's actions on the same page.
- The design does not provide user any help information or functionality. A quick help page for new users may be useful.
- The two shared modes in the Share Dialog Box, Publish and Collaborate, are not explained.
- The editing interface is implementing direct manipulation, where effects are immediately visible to the user, which helps learnability. It also is a familiar interface that can be related to many existing interfaces such as Adobe Acrobat, and in real world a metaphor of making notes on paper.
...
1 | | The homepage is the same as the one in Design 1. When Jim loads the URL for the "Worse is Better" paper, he will see the screen on the left. Note that the note page on the right is not titled. Jim can rename it by typing over the word "Untitled Note Page." If Jim wants to perform an action on some text, he would first highlight it. In this case, he chooses "MIT approach." Then he right-clicks, which pops up a menu. The menu contains the two actions he can perform: copy and annotate. Let's say Jim decides to annotate the text, so he clicks "annotate." A cursor immediately appears on a new line in the note page, prompting Jim to type a note. Jim types "is AWESOME!" | |
2 | | Now the note "Is AWESOME" is associated with "MIT approach." When Jim hovers over "is AWESOMe!" a dotted enclosing box appears and the text "MIT approach" is highlighted, indicating the association. | |
3 | | Jim could also start by typing a note in the note page. Once he finishes the note, he hovers over the border of the note, the cursor changes shape. At this point, if Jim right-clicks, a menu pops up. In this case, Jim wants to associate the new note to the picture on the webpage, so he clicks "Associate." | |
4 | | Now Jim has to choose a section on the webpage to associate to the new note. Before he chooses one, the note page is frozen: no more edition can be done on it. In this case, Jim hovers over the picture. A dotted enclosing box appears and Jim clicks within the box. This associates the picture with the new note. | |
5 | | The UI for saving and giving permission to other users is the same as Design 1. Now Sam and Jim are collaboratively annotating the webpage. The only difference in UI here is the addition of colored circles. All note page results marked by red circles were performed by Jim and all the ones marked by green circles were performed by Sam. |
Usability Analysis
Learnability:
- This UI exhibits metaphorical consistency. The interface imitates a notebook, which is what most users use to take notes.
- When the user hovers over a note or a copy, the associated section on the webpage will be highlighted. This is good feedback.
- On the down side, the UI is overly simplified and does not provide enough information scent. A new user might not know how to use it without playing around a bit.
...
1.1 | | To use WebAnnotator, Jim first logins by entering his username and password. |
1.2 | | He then gets to the Summary Page, in which there are two separate sections showing his previously saved pages and pages shared with other users. The pages are labeled by their titles and other properties. |
1.3 | | He types/pastes the URL of the page to be annotated into the text box (labeled by “pale” URL) and enters/clicks on the “refresh” button. In this case, the URL links to the “Worst is Better” paper for 6.033. |
1.4 | | He then has entered the edit mode. The window is divided into two sections. The left one is just the webpage (Worst is Better). |
1.5 |
| Jim begins to annotate by highlighting some text and inserting a popup comment box as shown in the picture. To facilitate viewing, WebAnnotator automatically reveals the difference between the webpage and the annotated version by drawing red squares to the middle bar. |
2.1 |
| To return to his previously annotated page before recitation, Jim logins again and clicks on the page labeled by “Worst is Better” on the Summary Page. |
2.2 |
| This brings him back to the annotated version he made last time. |
3.1 |
| To share his annotation with Sam, Jim simply opens his annotated page again and clicks on “SHARE!”. A popup window will then appear. |
3.2 |
| Sam will receive an email notification of this, with a hyperlink linked to Jim’s annotation. Once he follows the link, he will be able to view Jim’s annotation in share mode, which is highly analogous to edit mode, described above. On the left side is Jim’s annotated version. The version on the right is editable and identical to the left at the beginning. |
3.3 |
| To add his own new annotation, Sam uses the toolbar described previously to insert a new popup comment box. Again, this change is indicated by the red square (at the same height) shown in the middle bar to make newly added annotations more easily traceable. |
Usability Analysis
...
Learnability:
...
This design contains an internally consistent conceptual model, namely that the raw version is always displayed in the left subwindow and the annotatable version is always displayed on the right. With the aid of externally consistent standard editing tools, new users can quickly discover how to use this UI relatively quickly. The editing tools and the comparison middle bar also provide good affordances to help users explore this new application.
However, this design does not perform well in terms of feedback and information scent. For example, currently there is no mechanism to notify a user (Jim) that his annotated page has been viewed by another user (Sam) with whom he shared his page. Moreover, due to the inherent limitations of sketches, this current design also lacks adequate information scent for other actions, e.g. to share an annotated page, one must open it and click “SHARE!”. However, there is no information about this in the Summary Page.
...
Efficiency:
...
With standard editing tools and shortcut keys, users can quickly format their annotations. There are no steering tasks associated with this design. Having a Summary Page also makes retrieval easy and fast if they are not many saved pages as users can readily select their intended pages.
One possible improvement in efficiency is to design a better UI to display saved pages and shared pages in the Summary Page. A user with more than 100 pages saved may experience difficulty in finding a particular one to be retrieved. The same is true for sharing: if a page is to be shared among many people, entering each of their usernames is an inefficient task. Constructs like user groups can be a solution to this. Finally, the editing icons like highlight have not been optimized in terms of their locations in the window. Based on user statistics, the frequently used icons should be placed in easily clickable region, minimizing the time needed to complete the pointing task.
...
Safety:
...
The standard editing interface provides maximum user freedom in terms of annotation flexibility. They can annotate in whatever way they want and hence is less likely to make errors. Furthermore, most errors are easily recoverable by invoking the standard “undo” instruction. As a new design substantially different from PDF annotation tools, our design is free from capture errors that would otherwise be caused because of similar interfaces.
One possible drawback of the consistent conceptual model presented above is that users may be confused whether they are in edit mode or share mode. The indication to this is currently minimal. One other sources of errors is that sharing is currently an irreversible action. Thus a user cannot “un-share” a shared page.