Data collector
The Design Need:
A user is searching through a large amount of content and wants to collect a subset of items that (might) comply with what they are looking for.
Design Examples:
Design Solution:
Allow users to select and store the content items of their choice. Offer a link to this collection alongside the content. If your users might want future access to their lists, allow storage in their accounts.
- Offer “save” and “add to list” links next to the content items the user might want to collect.
- Provide feedback if an item is added to the list.
- Offer a link to the collection next to the content that is being browsed.
- Allow the user to move back and forth between the list and the content.
- Allow the user to manipulate the content in the list.
When to use:
Users who navigate through a large amount of content might want to create their own subset of items. Example situations are:
- Searching for a specific product on an e-commerce site
- Surfing a news site
- Browsing a content database for specific information
- Searching for jobs on a jobsite
Why use this solution (rationale):
We all make lists/collections of some sort when we browse through large amounts of content in real life, e.g.:
- Shopping lists
- Wish lists
- Dog ears in books and magazines
- Quotes from suppliers.
Applying the same principle online, users should be able to create subsets to help make selections or collect for later use.
More info elsewhere:
A related design pattern on www.welie.com
