Changes

Jump to: navigation, search

Firefox/Features/New Tab Page

2,555 bytes added, 00:07, 26 July 2011
update
{{FeatureStatus
|Feature name=New Tab Page
|Feature stage=DefinitionDesign|Feature status=In progress|Feature version=Firefox 9
|Feature health=OK
|Feature status note=Design iteration and active prototyping.
}}
{{FeatureTeam
|Feature feature manager=Jennifer Boriss
|Feature lead engineer=Margaret Leibovic
|Feature qa lead=George Carstoiu
|Feature ux lead=Jennifer Boriss
}}
{{FeaturePageBody
|Feature open issues and risks=* Performance or memory degradation
* Scope creep
|Feature overview=Whenever Firefox users open a new tab, their goal is to use it to navigate somewhere. Firefox currently displays a blank page when Firefox users open a new page. This is guaranteed to not help them perform their next task.
* Does not embarrass the user
What The simplest functionality can make users more efficient would include the following: This is intended to be the simplest possible version of a new tab page. The requirements are: * Show a grid of top 9-16 sites when opening a new tab* Responsiveness of new tab shouldn't appreciably decrease* It should be possible to remove sites that show up in the list* It should be possible to rearrange the list* It should be possible to manually add a new site to the list* When opening a new tab navigation without distracting them?using keyboard shortcuts, we should visually de-emphasize the grid. (Current direction: desaturate colors to black & white, fade in colors if mouse is being used)
|Feature users and use cases=* Searching from a new tab page
* Navigating to a location from a new tab page
* Opening a new tab page without being sure of what task to begin
|Feature non-goals=* Implement a very feature-rich version
* Replace or complement the Home Tab approach; this is a separate issue (that may inform our decisions on that front)
|Feature ux design=* Latest design: [http://people.mozilla.com/~faaborg/temp/uxmeeting/homeTabNewTab-i1.png Faaborg's iteration 1, referenced in UX meeting] (May 2011)
 
==== Design Questions ====
These are almost all inter-dependent questions, so an answer to one directs the answer to others. A complete design should address all of these.
* Should items link to individual pages or entire domains?
* Should removing an item delete the item only from the new tab page, delete the page from browser history, or forget the entire domain (this would require a confirmation dialog)?
* How often should we change/update the items shown on the page? Changing more frequently would reflect frecency but reduce consistency.
* Should we keep these items the same once the user modifies them?
* Do we want this to be a curated collection or a smart browser-generated set?
* Only keep items the user explicitly decides to keep?
* Remember which items the user removed so that we don't add them back?
* What kind of UI should we provide for adding items?
 
==== Older Designs ====
* Mozilla Labs was at one time [https://mozillalabs.com/blog/2009/03/new-tab-page-proposed-design-principles-and-prototype/ prototyping this in an add-on]:
** [http://www.azarask.in/blog/post/firefox-31-new-tab-spec/ Aza's blog post about the spec]
** [http://mozilla.seanmartell.com/newTab_1.jpg mart3ll's visual treatment]
** [http://mozilla.seanmartell.com/newTab_versionEleventy.jpg mart3ll's visual treatment]
* [https://mozillalabs.com/blog/2008/08/new-tab-concepts This] is another Mozilla Labs blog post that might be useful.
|Feature ux design===== Next steps Steps ====* Identify what to examine in user testingInitial wireframe design* Identify relevant [https://jboriss.wordpress.com/2011/06/15/research and data that can be used to narrow down functionality-spinning-up-on-new-tab-page/ User research projects]* Create designs based Iterate on the above prototype in UX branch
}}
{{FeatureInfo
|Feature priority=UnprioritizedP1|Feature roadmap=Firefox DesktopUser Experience
|Feature list=Desktop
|Feature engineering team=Desktop front-end
}}
{{FeatureTeamStatus}}
Confirm
954
edits

Navigation menu