Firefox/Features/streamline-search: Difference between revisions

From MozillaWiki
Jump to navigation Jump to search
m (clearing in prep for migration to new feature page format)
mNo edit summary
Line 1: Line 1:
{{FeatureStatus
|Feature name=Streamline the visual appearance of the search field
|Feature stage=Definition
|Feature health=Blocked
|Feature status note=Need to decide that we want to move forward, and then get colors from the various engines.
}}
{{FeatureTeam
|Feature feature manager=Alex Faaborg
|Feature lead engineer=Margaret Leibovic
|Feature qa lead=Simona Badau
|Feature ux lead=Alex Faaborg
|Feature additional members=Kev Needham (bizdev)
}}
{{FeaturePageBody
|Feature open issues and risks=* If we default the search button to green (same as the go button in the location bar) if the search engine has not provided us with a color, will that cause any issues with our relationship with them?


|Feature overview=The favicons in the search field are creating a significant amount of visual complexity in our product. They are using a wide range of colors, and they reduce the relative discoverability of nearby controls like reload and stop.  Additionally the search field is causing a large number of mode errors, as users search the previous engine they selected for a new search term.  This project aims to solve both of these problems.
==== Goals ====
* Pretty
* Reduced mode errors
* Increased focus on various engines as verbs (not that we care that much, but a side effect of the design)
* Increased brand awareness (not that we care that much, but a side effect of the design)
|Feature users and use cases=* Search with a greater awareness of which search engine is activated
* Return to the search field after a long period of time and realize that your default search engine is not the currently active one
* Enjoy the visual simplicity and streamlined appearance of the field when it is not currently focused
|Feature requirements=* Getting major search engines to optionally specify a color that they would like to use when they are active {{bug|634140}}
* Implementing the changes, with engines without specified colors falling back to the same color as the active go button {{bug|592909}}
|Feature non-goals=* Merge the search bar with the location bar (at this point)
|Feature ux design=[https://bug592909.bugzilla.mozilla.org/attachment.cgi?id=500550 Mockup]
|Feature implementation notes=* Reaching out to search engines to get colors {{bug|634140}}
* Implementation {{bug|592909}}
}}
{{FeatureInfo
|Feature priority=P3
|Feature roadmap=User Experience
|Feature list=Desktop
|Feature engineering team=Desktop front-end
}}
{{FeatureTeamStatus
|Feature products status=tbd
|Feature engineering status=tbd
|Feature security status=tbd
|Feature privacy status=tbd
|Feature localization status=tbd
|Feature accessibility status=tbd
|Feature qa status=tbd
|Feature ux status=tbd
}}

Revision as of 13:53, 11 July 2011

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

Status

Streamline the visual appearance of the search field
Stage Definition
Status `
Release target `
Health Blocked
Status note Need to decide that we want to move forward, and then get colors from the various engines.

{{#set:Feature name=Streamline the visual appearance of the search field

|Feature stage=Definition |Feature status=` |Feature version=` |Feature health=Blocked |Feature status note=Need to decide that we want to move forward, and then get colors from the various engines. }}

Team

Product manager `
Directly Responsible Individual Alex Faaborg
Lead engineer Margaret Leibovic
Security lead `
Privacy lead `
Localization lead `
Accessibility lead `
QA lead Simona Badau
UX lead Alex Faaborg
Product marketing lead `
Operations lead `
Additional members Kev Needham (bizdev)

{{#set:Feature product manager=`

|Feature feature manager=Alex Faaborg |Feature lead engineer=Margaret Leibovic |Feature security lead=` |Feature privacy lead=` |Feature localization lead=` |Feature accessibility lead=` |Feature qa lead=Simona Badau |Feature ux lead=Alex Faaborg |Feature product marketing lead=` |Feature operations lead=` |Feature additional members=Kev Needham (bizdev) }}

Open issues/risks

  • If we default the search button to green (same as the go button in the location bar) if the search engine has not provided us with a color, will that cause any issues with our relationship with them?

Stage 1: Definition

1. Feature overview

The favicons in the search field are creating a significant amount of visual complexity in our product. They are using a wide range of colors, and they reduce the relative discoverability of nearby controls like reload and stop. Additionally the search field is causing a large number of mode errors, as users search the previous engine they selected for a new search term. This project aims to solve both of these problems.

Goals

  • Pretty
  • Reduced mode errors
  • Increased focus on various engines as verbs (not that we care that much, but a side effect of the design)
  • Increased brand awareness (not that we care that much, but a side effect of the design)

2. Users & use cases

  • Search with a greater awareness of which search engine is activated
  • Return to the search field after a long period of time and realize that your default search engine is not the currently active one
  • Enjoy the visual simplicity and streamlined appearance of the field when it is not currently focused

3. Dependencies

`

4. Requirements

  • Getting major search engines to optionally specify a color that they would like to use when they are active bug 634140
  • Implementing the changes, with engines without specified colors falling back to the same color as the active go button bug 592909

Non-goals

  • Merge the search bar with the location bar (at this point)

Stage 2: Design

5. Functional specification

`

6. User experience design

Mockup

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=* If we default the search button to green (same as the go button in the location bar) if the search engine has not provided us with a color, will that cause any issues with our relationship with them? |Feature overview=The favicons in the search field are creating a significant amount of visual complexity in our product. They are using a wide range of colors, and they reduce the relative discoverability of nearby controls like reload and stop. Additionally the search field is causing a large number of mode errors, as users search the previous engine they selected for a new search term. This project aims to solve both of these problems.

Goals

  • Pretty
  • Reduced mode errors
  • Increased focus on various engines as verbs (not that we care that much, but a side effect of the design)
  • Increased brand awareness (not that we care that much, but a side effect of the design)

|Feature users and use cases=* Search with a greater awareness of which search engine is activated

  • Return to the search field after a long period of time and realize that your default search engine is not the currently active one
  • Enjoy the visual simplicity and streamlined appearance of the field when it is not currently focused

|Feature dependencies=` |Feature requirements=* Getting major search engines to optionally specify a color that they would like to use when they are active bug 634140

  • Implementing the changes, with engines without specified colors falling back to the same color as the active go button bug 592909

|Feature non-goals=* Merge the search bar with the location bar (at this point) |Feature functional spec=` |Feature ux design=Mockup |Feature implementation plan=` |Feature security review=` |Feature privacy review=` |Feature localization review=` |Feature accessibility review=` |Feature qa review=` |Feature operations review=` |Feature implementation notes=* Reaching out to search engines to get colors bug 634140

|Feature landing criteria=` }}

Feature details

Priority P3
Rank 999
Theme / Goal `
Roadmap User Experience
Secondary roadmap `
Feature list Desktop
Project `
Engineering team Desktop front-end

{{#set:Feature priority=P3

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

Team status notes

  status notes
Products tbd `
Engineering tbd `
Security tbd `
Privacy tbd `
Localization tbd `
Accessibility tbd `
Quality assurance tbd `
User experience tbd `
Product marketing ` `
Operations ` `

{{#set:Feature products status=tbd

|Feature products notes=` |Feature engineering status=tbd |Feature engineering notes=` |Feature security status=tbd |Feature security health=` |Feature security notes=` |Feature privacy status=tbd |Feature privacy notes=` |Feature localization status=tbd |Feature localization notes=` |Feature accessibility status=tbd |Feature accessibility notes=` |Feature qa status=tbd |Feature qa notes=` |Feature ux status=tbd |Feature ux notes=` |Feature product marketing status=` |Feature product marketing notes=` |Feature operations status=` |Feature operations notes=` }}


Retrieved from "https://wiki.allizom.org/index.php?title=Firefox/Features/streamline-search&oldid=327507"