Awesome Bar v2

Status

Team

Open issues/risks

`

Stage 1: Definition

1. Feature overview

The Awesomebar is one of the stand-out features of Firefox. We should revisit our algorithms and styling to ensure that users are getting the most from it. In addition, we should make sure that the combination of the inline auto-complete and the Awesomebar pop-up works as well as it can for our users.

User surfing patterns, bookmarking habits, etc. have changed significantly over the last few years. More users are spending more time on fewer sites than ever before. Are we optimized for the user who spends most of her time on Facebook or Twitter? Does our algorithm respond to the changing structure of URLs on the web -- like the increasing usage of hash bang URLs?

I know these are questions and not answers so I'll be working with folks to come up with answers that will become the functional and design specs for this feature.

Here's where the current algorithm (I think the doc is current, not actually sure) is documented https://developer.mozilla.org/en/Places:Awesomebar

2. Users & use cases

`

3. Dependencies

`

4. Requirements

`

Non-goals

`

Stage 2: Design

5. Functional specification

`

6. User experience design

`

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

`

Feature details

Team status notes