Firefox/Projects/TabCandy: Difference between revisions
Jump to navigation
Jump to search
(→Work) |
(→Work) |
||
| Line 54: | Line 54: | ||
= Work = | = Work = | ||
* | *'''[[Firefox/Projects/TabCandy/Work|Team Work Page]]''' | ||
*'''[[Firefox/Projects/TabCandy/FAQ|The Tab Candy FAQ]]''' | |||
[[Firefox/Projects/TabCandy/FAQ|The Tab Candy FAQ]] | |||
Revision as of 02:57, 23 July 2010
Overview
- Description
- Why is it that you can remember where the knives are in your kitchen, which has hundreds of things, but have difficulty remember where a particular tab is? TabCandy is a project that helps users deal with the complex ways the modern web is used by providing spatial, touchable groups of tabs and tab groups.
The Pitch
Coming soon
- For now, see the very old original presentation
Current Status
- Have removed jQuery dependency, working now on integration with trunk. See Bug 572889.
Problem Space
- Tabs don’t scale.
- It’s time consuming to switch between tabs.
- We work in semantic groups; our browser don’t.
- Our tabs have no understanding of search. Only basic understanding of “apps”.
- Bookmarks are to heavy, tabs are too light. No metaphors for saving/sharing/viewing what we are seeing.
- No incentive to clean up.
- We spend 76% of time on first & last tab.
Goals / Use Cases
- Make switching between tabs easier
- Make grouping, saving, and managing tabs easier
- Productivity when you increase monitor size goes up by ~30% (recognition+spatial memory), bring this efficiency gain and ease of mind to tabs.
Non-goals
- Whole-sale replacement of tabs (by default)
- Slowing down tab switching (with gratuitous animations, etc)
- Being an alt-tab replacement
Bugs
- All open TabCandy bugs
Design
- More detailed designs coming soon
- Some corollary design from a couple years ago
- See the presentation.