Firefox/Features/New Tab Page: Difference between revisions

From MozillaWiki
Jump to navigation Jump to search
No edit summary
No edit summary
 
(23 intermediate revisions by 6 users not shown)
Line 1: Line 1:
{{FeatureStatus
{{FeatureStatus
|Feature name=New Tab Page
|Feature name=New Tab Page
|Feature stage=Design
|Feature stage=Landed
|Feature status=In progress
|Feature status=Complete
|Feature version=Firefox 9
|Feature version=Firefox 13
|Feature health=OK
|Feature health=OK
|Feature status note=Design iteration and active prototyping.
|Feature status note=Landed in Fx13.  New design has been updated and everyone should download Nightly and test/send feedback when launching a new tab.  Great work by the whole team.
}}
}}
{{FeatureTeam
{{FeatureTeam
|Feature product manager=Asa Dotzler
|Feature product manager=Chris Lee
|Feature feature manager=Jennifer Boriss
|Feature feature manager=Chris Lee
|Feature lead engineer=Margaret Leibovic
|Feature lead engineer=Tim Taubert
|Feature qa lead=Virgil Dicu
|Feature qa lead=Virgil Dicu
|Feature ux lead=Jennifer Boriss
|Feature ux lead=Jennifer Boriss
}}
}}
{{FeaturePageBody
{{FeaturePageBody
|Feature open issues and risks=* Performance or memory degradation  
|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.
|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.


Line 24: Line 23:
* Load instantly
* Load instantly
* Not be so distracting as to take users mentally away from their intended task and into an unintended one
* Not be so distracting as to take users mentally away from their intended task and into an unintended one
* Does not require configuration to be useful
* Be useful without any configuration, yet can be easily configured and disabled
* Can be configured entirely or disabled completely
* Does not embarrass the user
* Does not embarrass the user
|Feature users and use cases=* Navigating to a location from a new tab page
* Opening a new tab page without being sure of what task to begin
* Making navigation to a site the user has been to before faster
|Feature requirements===Phase 1: Minimal Needed for Release==
Display:
* Titles of top sites
Customization:


The simplest functionality would include the following:
* Ability to remove a particular top site from new tab page
** Ability for user to undo removal of a site from new tab page
* Ability to disable new tab page and restore blank page


This is intended to be the simplest possible version of a new tab page. The requirements are:
Performance:


* Show a grid of top 9-16 sites when opening a new tab
* No performance impact in browsing session
* Responsiveness of new tab shouldn't appreciably decrease
* Loads instantly
* 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 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)


This feature falls primarily in the '''Discovery''' category (from the "Discover, Experience, and Connect" vision statement.)
==Phase 2: Main Functionality in Place==
|Feature users and use cases=* Searching from a new tab page
 
* Navigating to a location from a new tab page
Customization:
* Opening a new tab page without being sure of what task to begin
 
|Feature non-goals=* Implement a very feature-rich version
* Ability to reorder displayed top sites
* Replace or complement the Home Tab approach; this is a separate issue (that may inform our decisions on that front)
* Ability to modify the titles of top sites
|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)
* Ability to to “lock” a site into place
* Ability to add a new site to new tab page
* Ability to replace displayed items with recent bookmarks, recently closed tabs, history, etc
 
==Phase 3: Future==
 
Features:
 
* Possibly Partial thumbnails of top sites (pending testing)
* Ability to bookmark an item from the new tab page itself
* Sites synced across devices and profiles
* Ability replace sites with tabs from other computers
* Possible ability to add a persona or background image to new tabs
* Ability to navigate sites wholly via keyboard
* Possible display of large icons rather than thumbnails, dependent on wide availability of high-resolution artwork, either provided by sites or generated by us


==== Design Questions ====
Spinoffs:
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 ====
* Similar-but-mobile new tab page on mobile Firefox
* 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.


==== Next Steps ====
==== Next Steps ====
* Initial wireframe design
* [https://jboriss.wordpress.com/2011/06/15/research-spinning-up-on-new-tab-page/ User research projects]
* Iterate on prototype in UX branch
* Iterate on prototype in UX branch
* Use feedback from prototype and user research to generate final design
|Feature ux design=[https://wiki.mozilla.org/File:New_tab_page_first_iteration_design_spec1.png First iteration spec]
}}
}}
{{FeatureInfo
{{FeatureInfo
|Feature priority=P1
|Feature priority=P1
|Feature rank=5
|Feature theme=Discover
|Feature roadmap=User Experience
|Feature roadmap=User Experience
|Feature secondary roadmap=Firefox Desktop
|Feature list=Desktop
|Feature list=Desktop
|Feature engineering team=Desktop front-end
|Feature engineering team=Desktop front-end
}}
}}
{{FeatureTeamStatus}}
{{FeatureTeamStatus
|Feature security status=sec-review-unnecessary
|Feature security health=OK
|Feature qa status=Signed-off
|Feature qa notes=[https://wiki.mozilla.org/Firefox/Features/New_Tab_Page/Test_Plan Test Plan]
}}

Latest revision as of 12:52, 5 June 2012

Please use "Edit with form" above to edit this page.

Status

New Tab Page
Stage Landed
Status Complete
Release target Firefox 13
Health OK
Status note Landed in Fx13. New design has been updated and everyone should download Nightly and test/send feedback when launching a new tab. Great work by the whole team.

{{#set:Feature name=New Tab Page

|Feature stage=Landed |Feature status=Complete |Feature version=Firefox 13 |Feature health=OK |Feature status note=Landed in Fx13. New design has been updated and everyone should download Nightly and test/send feedback when launching a new tab. Great work by the whole team. }}

Team

Product manager Chris Lee
Directly Responsible Individual Chris Lee
Lead engineer Tim Taubert
Security lead `
Privacy lead `
Localization lead `
Accessibility lead `
QA lead Virgil Dicu
UX lead Jennifer Boriss
Product marketing lead `
Operations lead `
Additional members `

{{#set:Feature product manager=Chris Lee

|Feature feature manager=Chris Lee |Feature lead engineer=Tim Taubert |Feature security lead=` |Feature privacy lead=` |Feature localization lead=` |Feature accessibility lead=` |Feature qa lead=Virgil Dicu |Feature ux lead=Jennifer Boriss |Feature product marketing lead=` |Feature operations lead=` |Feature additional members=` }}

Open issues/risks

  • Performance or memory degradation

Stage 1: Definition

1. 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.

We'd like to implement a page which displays on new tabs and helps users complete their next task. This will likely include offering options that are most likely to include the user's next task so that valuable time and steps are saved.

Such a page must meet certain requirements:

  • Load instantly
  • Not be so distracting as to take users mentally away from their intended task and into an unintended one
  • Be useful without any configuration, yet can be easily configured and disabled
  • Does not embarrass the user

2. Users & use cases

  • Navigating to a location from a new tab page
  • Opening a new tab page without being sure of what task to begin
  • Making navigation to a site the user has been to before faster

3. Dependencies

`

4. Requirements

Phase 1: Minimal Needed for Release

Display:

  • Titles of top sites

Customization:

  • Ability to remove a particular top site from new tab page
    • Ability for user to undo removal of a site from new tab page
  • Ability to disable new tab page and restore blank page

Performance:

  • No performance impact in browsing session
  • Loads instantly

Phase 2: Main Functionality in Place

Customization:

  • Ability to reorder displayed top sites
  • Ability to modify the titles of top sites
  • Ability to to “lock” a site into place
  • Ability to add a new site to new tab page
  • Ability to replace displayed items with recent bookmarks, recently closed tabs, history, etc

Phase 3: Future

Features:

  • Possibly Partial thumbnails of top sites (pending testing)
  • Ability to bookmark an item from the new tab page itself
  • Sites synced across devices and profiles
  • Ability replace sites with tabs from other computers
  • Possible ability to add a persona or background image to new tabs
  • Ability to navigate sites wholly via keyboard
  • Possible display of large icons rather than thumbnails, dependent on wide availability of high-resolution artwork, either provided by sites or generated by us

Spinoffs:

  • Similar-but-mobile new tab page on mobile Firefox

Next Steps

  • Iterate on prototype in UX branch
  • Use feedback from prototype and user research to generate final design

Non-goals

`

Stage 2: Design

5. Functional specification

`

6. User experience design

First iteration spec

Stage 3: Planning

7. Implementation plan

`

8. Reviews

Security review

`

Privacy review

`

Localization review

`

Accessibility

`

Quality Assurance review

`

Operations review

`

Stage 4: Development

9. Implementation

`

Stage 5: Release

10. Landing criteria

` {{#set:Feature open issues and risks=* Performance or memory degradation |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.

We'd like to implement a page which displays on new tabs and helps users complete their next task. This will likely include offering options that are most likely to include the user's next task so that valuable time and steps are saved.

Such a page must meet certain requirements:

  • Load instantly
  • Not be so distracting as to take users mentally away from their intended task and into an unintended one
  • Be useful without any configuration, yet can be easily configured and disabled
  • Does not embarrass the user

|Feature users and use cases=* Navigating to a location from a new tab page

  • Opening a new tab page without being sure of what task to begin
  • Making navigation to a site the user has been to before faster

|Feature dependencies=` |Feature requirements===Phase 1: Minimal Needed for Release==

Display:

  • Titles of top sites

Customization:

  • Ability to remove a particular top site from new tab page
    • Ability for user to undo removal of a site from new tab page
  • Ability to disable new tab page and restore blank page

Performance:

  • No performance impact in browsing session
  • Loads instantly

Phase 2: Main Functionality in Place

Customization:

  • Ability to reorder displayed top sites
  • Ability to modify the titles of top sites
  • Ability to to “lock” a site into place
  • Ability to add a new site to new tab page
  • Ability to replace displayed items with recent bookmarks, recently closed tabs, history, etc

Phase 3: Future

Features:

  • Possibly Partial thumbnails of top sites (pending testing)
  • Ability to bookmark an item from the new tab page itself
  • Sites synced across devices and profiles
  • Ability replace sites with tabs from other computers
  • Possible ability to add a persona or background image to new tabs
  • Ability to navigate sites wholly via keyboard
  • Possible display of large icons rather than thumbnails, dependent on wide availability of high-resolution artwork, either provided by sites or generated by us

Spinoffs:

  • Similar-but-mobile new tab page on mobile Firefox

Next Steps

  • Iterate on prototype in UX branch
  • Use feedback from prototype and user research to generate final design

|Feature non-goals=` |Feature functional spec=` |Feature ux design=First iteration spec |Feature implementation plan=` |Feature security review=` |Feature privacy review=` |Feature localization review=` |Feature accessibility review=` |Feature qa review=` |Feature operations review=` |Feature implementation notes=` |Feature landing criteria=` }}

Feature details

Priority P1
Rank 5
Theme / Goal Discover
Roadmap User Experience
Secondary roadmap Firefox Desktop
Feature list Desktop
Project `
Engineering team Desktop front-end

{{#set:Feature priority=P1

|Feature rank=5 |Feature theme=Discover |Feature roadmap=User Experience |Feature secondary roadmap=Firefox Desktop |Feature list=Desktop |Feature project=` |Feature engineering team=Desktop front-end }}

Team status notes

  status notes
Products ` `
Engineering ` `
Security sec-review-unnecessary `
Privacy ` `
Localization ` `
Accessibility ` `
Quality assurance Signed-off Test Plan
User experience ` `
Product marketing ` `
Operations ` `

{{#set:Feature products status=`

|Feature products notes=` |Feature engineering status=` |Feature engineering notes=` |Feature security status=sec-review-unnecessary |Feature security health=OK |Feature security notes=` |Feature privacy status=` |Feature privacy notes=` |Feature localization status=` |Feature localization notes=` |Feature accessibility status=` |Feature accessibility notes=` |Feature qa status=Signed-off |Feature qa notes=Test Plan |Feature ux status=` |Feature ux notes=` |Feature product marketing status=` |Feature product marketing notes=` |Feature operations status=` |Feature operations notes=` }}


Retrieved from "https://wiki.mozilla.org/index.php?title=Firefox/Features/New_Tab_Page&oldid=437744"