Anti-minimalistic redundant app button and home tab
Status
| Anti-minimalistic redundant app button and home tab | |
| Stage | Draft |
| Status | ` |
| Release target | ` |
| Health | OK |
| Status note | ` |
{{#set:Feature name=Anti-minimalistic redundant app button and home tab
|Feature stage=Draft |Feature status=` |Feature version=` |Feature health=OK |Feature status note=` }}
Team
| Product manager | ` |
| 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=`
|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
I see add-on icons in the menu bar, the toolbar and the add-on bar. If you deprecate the menu bar, so that people will use the app button, add-on authors will have to use the add-on bar, because you lead them, so they will follow.
My things are my bookmarks, my history, my downloads, my add-ons, my preferences etc.
Since a link to a dialog must be in only one place, because of redundancy and minimalism, my things can be in the app button or in the home tab.
If you place all my things in the home tab, I would be forced to use the Firefox Home, because links to dialogs would be there and if I change the url to somewhere else, I wouldn't be able to access my preferences again.
If you give more space to the app button, that is, if you turn the app button into a page, you can place all my things in about:appbutton and even add-on authors can place all their things in about:appbutton.
Finally, I see Bookmarks in home tab AND the app button, so it should be in about:appbutton only. I see lots of other things twice like History and Downloads, so they should be in about:appbutton only.
This is just a complaint and not a feature, so I moved it to Draft.
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=I see add-on icons in the menu bar, the toolbar and the add-on bar. If you deprecate the menu bar, so that people will use the app button, add-on authors will have to use the add-on bar, because you lead them, so they will follow.
My things are my bookmarks, my history, my downloads, my add-ons, my preferences etc.
Since a link to a dialog must be in only one place, because of redundancy and minimalism, my things can be in the app button or in the home tab.
If you place all my things in the home tab, I would be forced to use the Firefox Home, because links to dialogs would be there and if I change the url to somewhere else, I wouldn't be able to access my preferences again.
If you give more space to the app button, that is, if you turn the app button into a page, you can place all my things in about:appbutton and even add-on authors can place all their things in about:appbutton.
Finally, I see Bookmarks in home tab AND the app button, so it should be in about:appbutton only. I see lots of other things twice like History and Downloads, so they should be in about:appbutton only.
This is just a complaint and not a feature, so I moved it to Draft. |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=` }}