202
edits
Changes
no edit summary
However, other important use-cases are not handled well. Some of the use-cases we would like to handle (see also [[Bookmarks Use Cases]] for lots of ideas) are:
* '''Research:''' The user is researching a topic such as airline flights. They want to collect certain pages together and possibly remember key information from them such as time and cost. The user may, but does not necessarily, care about convenient future access.
* '''To-do list:''' The user wants to remember a page to come back to. For example, directions to a party on the weekend, or an article to finish reading. They want to come back to it no more than a few times, and is not interested in permanent storage.
* '''Long-term recall:''' The user wants to remember a page, but is not interested in accessing it frequently. For example, a HOWTO on configuring a piece of hardware that would not be needed until the OS is re-installed, or an obscure but potentially useful page on the company intranet.
There are other goals:
* It should be as easy as possible to get a basic amount of bookmarking and recall, even for new users. The current system doesn't do this. Most users use autocomplete + Google.
* If the previous goal is successful, we will need to be able to handle large numbers of bookmarks smoothly. The current system does not handle more than about 20 bookmarks in the menu.
* Don't significantly change the UI for people that have learned to use the current system. Most people will not want to learn something new, and will be upset if their bookmarks have moved. It should be possible to slowly transition to the new features.
