Silent Update not now prompt: Difference between revisions

Jump to navigation Jump to search

Silent Update not now prompt (view source)

Revision as of 21:31, 16 November 2011

95 bytes removed ,  16 November 2011
no edit summary
No edit summary
No edit summary
Line 14: Line 14:
}}
}}
{{FeaturePageBody
{{FeaturePageBody
|Feature overview=Related to the Add-ons Compatibility Check [https://wiki.mozilla.org/Features/Add-ons/Add-ons_Default_to_Compatible feature], users who have Add-ons that are unsupported when a silent update takes place in the background, Firefox will deliver the following experiences:
|Feature overview=Related to the Add-ons Compatibility Check [https://wiki.mozilla.org/Features/Add-ons/Add-ons_Default_to_Compatible feature], Firefox will need to carefully handle each user's experience differently depending on their add-on compatibility situation.  We have carefully outlined the requirements here that determine how Firefox should work based on a user's scenario. 


#All users without Add-ons or have all compatible Add-ons are updated on release date
#Users with 1 or more incompatible Add-ons, we will offer a 7-day grace period with no prompt to update Firefox (assuming this passes security review)
#Users will auto update anytime with the 7-day grace period when 1 or more of their Add-ons become compatible
#Update today's incompatible Add-on prompt with a more positive tone (UX to provide specs below)
#On the 7th day of the grace period if there are still incompatible Add-ons, we will skip updating the user for this release and wait for the N+1 release
|Feature users and use cases=Sandra is using Firefox to check her email and at the same time in the background, Firefox is being updated to the latest version.  However, as Firefox runs through the installation process it also checks for add-ons compatibility and identifies two add-ons that are unsupported with the new version of Firefox.  
|Feature users and use cases=Sandra is using Firefox to check her email and at the same time in the background, Firefox is being updated to the latest version.  However, as Firefox runs through the installation process it also checks for add-ons compatibility and identifies two add-ons that are unsupported with 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 unimportant to her or 2) select "not now" where Firefox will check on a daily basis AMO to see if the specific add-ons have been updated to become compatible.   
Given there are incompatible add-ons, Firefox will not update Sandra to the latest version of Firefox and enter a 7 day grace period that will continue to check in the background if her incompatible add-ons become compatible.   


There are two scenarios that can take place here:
There are a few things to note here:


#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.
#Both add-ons become supported within the 7 day grace period and the Firefox update happens in the background successfully and Sandra is able to use the most secure, full-feature browser in the market.
#Zero or one of two add-ons become supported, but because there's at least one add-on that is still unsupported, we don't remind or bring up any additional prompts until all add-ons are supported or two? (TBD) weeks have elapsed since the initial update process.   
#Sandra continues to have at least 1 incompatible add-on on the final day of the grace period and Firefox will skip the update process this release and wait for the next release to update.
#This check will go on for Sandra for every Firefox release.  However, if she reaches 3 consecutive releases where 1 or more incompatible add-on does not become compatible in the 7 day grace period after the release date, Firefox will prompt Sandra and let her know that Firefox will be updated even with an incompatible add-on.   


<b>Things to note here</b> -- the reason to go down the path of a "required" update is the following:
<b>Things to note here</b> -- the reason to go down the path of a "required" update is the following:


#Based on our data, we have learned over time that 99% of active add-on developers update their add-ons to become compatible with the latest version of Firefox. Add-ons that are not updated within 2(?) weeks of a Firefox release in general will not be supported moving forward. (we should get hard data from Fligtar on this.) 
#Based on our data, we have learned over time that 99% of active add-on developers update their add-ons to become compatible with the latest version of Firefox.  
#To reduce product fragmentation and user confusion, our goal is to offer the most secure, feature-rich and optimized browsing experience that continues to move the web forward.  All Firefox users should be offered that opportunity and we're fully aware that certain add-on functionality is critical to users' workflow and will do our best to work with developers to stay updated.   
#To reduce product fragmentation and user confusion, our goal is to offer the most secure, feature-rich and optimized browsing experience that continues to move the web forward.  All Firefox users should be offered that opportunity and we're fully aware that certain add-on functionality is critical to users' workflow and will do our best to work with developers to stay updated.   
#Users will continue to have the option to turn off 'Updates' in general, but are encouraged to leave that checked so they have the best experience.  Not only will we continue to innovate by delivering new features, but enhancements under the hood like memory reduction/performance/etc. will help create new experiences across the web.
#Users will continue to have the option to turn off 'Updates' in general, but are encouraged to leave that checked so they have the best experience.  Not only will we continue to innovate by delivering new features, but enhancements under the hood like memory reduction/performance/etc. will help create new experiences across the web.
|Feature requirements=Leveraging the new changes to the Add-on compatibility checker, Firefox will create a new dialog showing users all unsupported Add-ons (in any).
|Feature requirements=#All users without Add-ons or have all compatible Add-ons are updated to the latest version of Firefox on release date
 
#For users with 1 or more incompatible Add-ons, we will offer a 7-day grace period with no prompt to update Firefox (assuming this passes security review)
Dialog should offer two options:
#As Add-ons become compatible on subsequent days post release, users will auto update anytime within the 7-day grace period when all of their incompatible Add-ons become compatible
#"Update" (users can manually decide to continue the update since they don't care about the incompatible Add-ons)
#On the 7th day of the grace period if there are still incompatible Add-ons, we will skip updating the user for this release and wait for the N+1 release
#"Not now" (wait X days and continue to check if there are new updates for the unsupported Add-ons)
#For users who have incompatible Add-ons for 3 consecutive release, we will display the incompatible Add-on prompt on the 7th day of the 3rd release where they've had incompatible Add-ons and inform users that we are auto-updating them regardless of the incompatible Add-on (this has been approved by both Product and UX teams)
 
#We will update today's incompatible Add-on prompt with a more positive tone (UX to provide specs below)
Once two weeks have elapsed, Firefox will automatically update to the latest version in the background without interrupting the user. (this is still an area open for discussion. -Asa)
}}
}}
{{FeatureInfo
{{FeatureInfo
Clee
canmove, Confirmed users, Bureaucrats and Sysops emeriti
496

edits

Retrieved from "https://wiki.mozilla.org/Special:MobileDiff/370374"

Navigation menu