Awesome Bar v2
Status
| Awesome Bar v2 | |
| Stage | Definition |
| Status | ` |
| Release target | ` |
| Health | OK |
| Status note | Waiting on UX and UR for guidance |
{{#set:Feature name=Awesome Bar v2
|Feature stage=Definition |Feature status=` |Feature version=` |Feature health=OK |Feature status note=Waiting on UX and UR for guidance }}
Team
| Product manager | Asa Dotzler |
| Directly Responsible Individual | ` |
| Lead engineer | ` |
| Security lead | ` |
| Privacy lead | ` |
| Localization lead | ` |
| Accessibility lead | ` |
| QA lead | ` |
| UX lead | ` |
| Product marketing lead | ` |
| Operations lead | ` |
| Additional members | ` |
{{#set:Feature product manager=Asa Dotzler
|Feature feature manager=` |Feature lead engineer=` |Feature security lead=` |Feature privacy lead=` |Feature localization lead=` |Feature accessibility lead=` |Feature qa lead=` |Feature ux lead=` |Feature product marketing lead=` |Feature operations lead=` |Feature additional members=` }}
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
` {{#set:Feature open issues and risks=` |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 |Feature users and use cases=` |Feature dependencies=` |Feature requirements=` |Feature non-goals=` |Feature functional spec=` |Feature ux design=` |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 | Unprioritized |
| Rank | 999 |
| Theme / Goal | ` |
| Roadmap | ` |
| Secondary roadmap | ` |
| Feature list | ` |
| Project | ` |
| Engineering team | ` |
{{#set:Feature priority=Unprioritized
|Feature rank=999 |Feature theme=` |Feature roadmap=` |Feature secondary roadmap=` |Feature list=` |Feature project=` |Feature engineering team=` }}
Team status notes
| status | notes | |
| Products | ` | ` |
| Engineering | ` | ` |
| Security | ` | ` |
| Privacy | ` | ` |
| Localization | ` | ` |
| Accessibility | ` | ` |
| Quality assurance | ` | ` |
| User experience | ` | ` |
| Product marketing | ` | ` |
| Operations | ` | ` |
{{#set:Feature products status=`
|Feature products notes=` |Feature engineering status=` |Feature engineering notes=` |Feature security status=` |Feature security health=` |Feature security notes=` |Feature privacy status=` |Feature privacy notes=` |Feature localization status=` |Feature localization notes=` |Feature accessibility status=` |Feature accessibility notes=` |Feature qa status=` |Feature qa notes=` |Feature ux status=` |Feature ux notes=` |Feature product marketing status=` |Feature product marketing notes=` |Feature operations status=` |Feature operations notes=` }}