Firefox/Projects/Pages: Difference between revisions

From MozillaWiki
Jump to navigation Jump to search
No edit summary
Line 17: Line 17:
* Tabs don’t scale.
* Tabs don’t scale.
* It’s time consuming to switch between tabs.
* It’s time consuming to switch between tabs.
* We work in semantic groups; our browser don’t. No understanding of search. Only basic understanding of “apps”.
* 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.
* Bookmarks are to heavy, tabs are too light. No metaphors for saving/sharing/viewing what we are seeing.
* No incentive to clean up.
* No incentive to clean up.
* We spend over 70% of time on first & last tab [check this]
* We spend 76% of time on first & last tab.


= Goals / Use Cases =
= Goals / Use Cases =
Line 26: Line 27:
* Make switching between tabs easier
* Make switching between tabs easier
* Make grouping, saving, and managing 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 =
= Non-goals =
Line 33: Line 34:


= Bugs =
= Bugs =
{{bug|480350}}
{{bug|455650}}


= Design =
= Design =
[http://people.mozilla.com/~faaborg/files/shiretoko/awesomeBari2.png Faaborg's initial mock-ups]
* More detailed designs coming soon
* See the [http://www.slideshare.net/guestab5fefd/tab-candy-presentation-short presentation].
http://img.skitch.com/20100226-r17g931yh7959abc9ie7cr5t6e.png
http://img.skitch.com/20100226-jpirgqa5spbj6k94qw228uc5t9.png


[http://limi.net/articles/tab-matching-in-the-location-bar Limi's follow-up blog post with some suggested changes]
= Prototype =
 
* Get the [http://code.google.com/p/tabcandy/source/browse/ source code] for the Firefox extension.


= Testing =
= Testing =
* [https://wiki.mozilla.org/Firefox/Projects/Tab_Matches_in_Awesomebar/TestPlan Test Plan]
* TBD

Revision as of 19:06, 26 February 2010

Do not edit this page RESTRICTED Do not edit this page
Please do not edit this page without permission; comments should be added to the discussion page.

Overview

Description
Rethink the basic way we interact with multiple web-pages (tabs) and the jump-off navigation point.


Current Status

What Is This All About

See the presentation

Problems

  • 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

  • Promote tab searching over other types of revisitation (for instance placing all of the tab results on top)
  • Overly complicate the current design of the awesome bar (through things like the introduction of additional icons, arrows, or moving the focus right/left in addition to up/down)

Bugs

Design

20100226-r17g931yh7959abc9ie7cr5t6e.png 20100226-jpirgqa5spbj6k94qw228uc5t9.png

Prototype

Testing

  • TBD