Features/Jetpack/Jetpack-Move-Widgets-to-top
Status
Move Widgets to Top of Browser | |
Stage | Draft |
Status | In progress |
Release target | ` |
Health | OK |
Status note | ` |
Team
Product manager | Dave Mason |
Directly Responsible Individual | Alex Poirot |
Lead engineer | contributor |
Security lead | ` |
Privacy lead | ` |
Localization lead | ` |
Accessibility lead | ` |
QA lead | ` |
UX lead | Stephen Horlander |
Product marketing lead | ` |
Operations lead | ` |
Additional members | ` |
Open issues/risks
`
Stage 1: Definition
1. Feature overview
This feature is simply about moving the placement of widgets created in the Add-on SDK to the top of the browser. Currently, widgets are automatically placed in the "addon bar" at the very bottom of Firefox. This places the widget out of the way of the user and makes the discovery of the widget much harder for the user.
We want to move these widgets to the top, either in the url bar or off to the right of the search box depending on consensus of placement and functionality agreed to with the UX team.
2. Users & use cases
Use-cases pending upon consensus with UX team - see UX Design section below
3. Dependencies
`
4. Requirements
`
Non-goals
`
Stage 2: Design
5. Functional specification
`
6. User experience design
We have already had one meeting with the UX team on this issue and agreed that it is a good idea to move these widgets but are currently unsure as to how the widgets would behave if they lived to the right of the search box.
If a user adds multiple widgets forcing us to move them from view (with a carrot of some sort to discover the hidden widgets) how would they behave? How discoverable would they be when hidden?
In addition, do we limit what can be done with these widgets? Currently we allow any html content which means these widgets can grow in size and show just about anything.
Do we still give the option of using the lower addon bar? or is this just bad UI that should disappear?
These questions must be figured out before implementation can begin.
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
Priority | Unprioritized |
Rank | 999 |
Theme / Goal | ` |
Roadmap | ` |
Secondary roadmap | ` |
Feature list | ` |
Project | ` |
Engineering team | ` |
Team status notes
status | notes | |
Products | ` | ` |
Engineering | ` | ` |
Security | ` | ` |
Privacy | ` | ` |
Localization | ` | ` |
Accessibility | ` | ` |
Quality assurance | ` | ` |
User experience | ` | ` |
Product marketing | ` | ` |
Operations | ` | ` |