Silent Update not now prompt
Status
| Silent Update - Create 'not now' dialog for unsupported Add-ons | |
| Stage | Definition |
| Status | In progress |
| Release target | ` |
| Health | OK |
| Status note | ` |
{{#set:Feature name=Silent Update - Create 'not now' dialog for unsupported Add-ons
|Feature stage=Definition |Feature status=In progress |Feature version=` |Feature health=OK |Feature status note=` }}
Team
| Product manager | Chris Lee |
| Directly Responsible Individual | Chris Lee |
| 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=Chris Lee
|Feature feature manager=Chris Lee |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
Related to the Add-ons Compatibility Check feature, users who have Add-ons that are unsupport when a silent update is taking place in the background, Firefox will alert them that certain Add-ons have become invalid and they have one of two options:
1) Continue with the upgrade (more secure, latest features, etc.) because the invalid add-ons are not important to the user.
2) User can select "not now" and wait X days for the Add-on developers to update their code to become compatible with the latest version of Firefox.
The requirement here is to create/modify a dialog prompt that communicates these options.
2. Users & use cases
Sandra is using Firefox checking her email and at the same time in the background, Firefox is being updated to the latest version. However, as Firefox makes all the appropriate checks such as for Add-ons, it identifies 2 Add-ons that are unsupported on the new version of Firefox.
There is a prompt that surfaces to Sandra informing her of the new update and which Add-ons are unsupported. She is given two options to 1) continue with the update and ignore the Add-ons because they are irrelevant to her or 2) select "not now" where Firefox will not check on a daily basis AMO to see if he specific Add-ons have been updated to be compatible.
There are two scenarios that can take place here:
1) Both Add-ons become supported over the next couple days and the Firefox update happens in the background successfully and Sandra is able to use the most secure, full-feature browser in the market
2) Zero or 1 of 2 Add-ons become supported, but because the one Add-on that still isn't supported since the initial "update" process, we don't remind or bring up any additional prompts until all Add-ons are supported or the next Firefox update becomes available.
- Things to note here -- the reason to go down the path of not forcing our users to upgrade if there are unsupported Add-ons is because:
1) Mozilla wants to continue to stand by our mission of user sovereignty and user choice. Forcing users to update doesn't offer them this choice. 2) Although our goal of updating users is primarily around ensuring a safe, secure web browsing experience, some users are comfortable making the trade-off of not being secure for functionality that is important to them. If we force an update and break certain functionality that defines their web experience, we may push them away from Firefox all together. The end result may be users who a) leave Firefox for Chrome/Safari/IE and b) continue to be insecure (threat to others and themselves without knowing it) because they need and expect the functionality the Add-on previously offered them.
3. Dependencies
`
4. Requirements
- Leveraging the new changes to the Add-on compatibility checker, Firefox will create a new dialog showing users any/all unsupported Add-ons
- Dialog should offer two options:
1) Not now (wait X days and continue to check if there are new updates for the unsupported Add-ons) 2) Update (users can manually decide to continue the update since they don't care about the incompatible Add-ons)
- Placeholder, more reqs coming
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=Related to the Add-ons Compatibility Check feature, users who have Add-ons that are unsupport when a silent update is taking place in the background, Firefox will alert them that certain Add-ons have become invalid and they have one of two options:
1) Continue with the upgrade (more secure, latest features, etc.) because the invalid add-ons are not important to the user.
2) User can select "not now" and wait X days for the Add-on developers to update their code to become compatible with the latest version of Firefox.
The requirement here is to create/modify a dialog prompt that communicates these options. |Feature users and use cases=Sandra is using Firefox checking her email and at the same time in the background, Firefox is being updated to the latest version. However, as Firefox makes all the appropriate checks such as for Add-ons, it identifies 2 Add-ons that are unsupported on the new version of Firefox.
There is a prompt that surfaces to Sandra informing her of the new update and which Add-ons are unsupported. She is given two options to 1) continue with the update and ignore the Add-ons because they are irrelevant to her or 2) select "not now" where Firefox will not check on a daily basis AMO to see if he specific Add-ons have been updated to be compatible.
There are two scenarios that can take place here:
1) Both Add-ons become supported over the next couple days and the Firefox update happens in the background successfully and Sandra is able to use the most secure, full-feature browser in the market
2) Zero or 1 of 2 Add-ons become supported, but because the one Add-on that still isn't supported since the initial "update" process, we don't remind or bring up any additional prompts until all Add-ons are supported or the next Firefox update becomes available.
- Things to note here -- the reason to go down the path of not forcing our users to upgrade if there are unsupported Add-ons is because:
1) Mozilla wants to continue to stand by our mission of user sovereignty and user choice. Forcing users to update doesn't offer them this choice. 2) Although our goal of updating users is primarily around ensuring a safe, secure web browsing experience, some users are comfortable making the trade-off of not being secure for functionality that is important to them. If we force an update and break certain functionality that defines their web experience, we may push them away from Firefox all together. The end result may be users who a) leave Firefox for Chrome/Safari/IE and b) continue to be insecure (threat to others and themselves without knowing it) because they need and expect the functionality the Add-on previously offered them. |Feature dependencies=` |Feature requirements=*Leveraging the new changes to the Add-on compatibility checker, Firefox will create a new dialog showing users any/all unsupported Add-ons
- Dialog should offer two options:
1) Not now (wait X days and continue to check if there are new updates for the unsupported Add-ons) 2) Update (users can manually decide to continue the update since they don't care about the incompatible Add-ons)
- Placeholder, more reqs coming
|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 | P1 |
| Rank | 999 |
| Theme / Goal | Experience |
| Roadmap | Firefox Desktop |
| Secondary roadmap | ` |
| Feature list | Desktop |
| Project | ` |
| Engineering team | ` |
{{#set:Feature priority=P1
|Feature rank=999 |Feature theme=Experience |Feature roadmap=Firefox Desktop |Feature secondary roadmap=` |Feature list=Desktop |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=` }}