Firefox/Features/Lessen App Update Displayed UI: Difference between revisions

m
no edit summary
mNo edit summary
Line 18: Line 18:
To reduce update fatigue, don't display application update notifications and user interface unless necessary.
To reduce update fatigue, don't display application update notifications and user interface unless necessary.


Twelve hours after an update is downloaded the user is told to restart Firefox by the display of the application update user interface. Instead of always notifying after twelve hours and possibly interrupting the user the notification should only be displayed when it is important for the user to apply the update (e.g. the update contains an important security fix the user should be notified).
Twelve hours after an update is downloaded the user is told to restart Firefox by the display of the application update user interface. Instead of always notifying after twelve hours and possibly interrupting the user the notification should only be displayed when it is important for the user to apply the update (e.g. when the update contains an important security fix the user should be notified).


If there is a pending update it is applied during startup and the updater dialog is displayed. Over the last year there have been several improvements to the updater that have made it apply updates significantly faster. When the update is applied quickly the updater dialog should not be displayed.
If there is a pending update it is applied during startup and the updater dialog is displayed. Over the last year there have been several improvements to the updater that have made it apply updates significantly faster. When the update is applied quickly the updater dialog should not be displayed.
Line 31: Line 31:
== Release Requirements ==
== Release Requirements ==
* Needs to lessen the amount of times the user sees user interface associated with an application update
* Needs to lessen the amount of times the user sees user interface associated with an application update
* The decision to display the notification must be controlled remotely (the update xml)
* The decision when the notification should be displayed must be controlled remotely (the update xml) and have a default amount of time
* Needs to pass a security review
* Needs to pass a security review
* Needs to have tests
* Needs to have tests


== Next Steps & Open Issues ==
== Next Steps & Open Issues ==
* Decide whether this can be implemented using the existing user interface since the new application notification user interface hasn't been created yet. Should be resolved during the kickoff meeting on  5/24/11.
* {{Bug|353804}} - Automatic update does not check for newer versions before resuming an update download on startup - Tim Taubert - in progress
* {{Bug|353804}} - Automatic update does not check for newer versions before resuming an update download on startup - Tim Taubert - in progress
* {{Bug|657472}} - Replace notification that an update has been downloaded / please restart with new notification system TBD
* {{Bug|659425}} - get average session length from crash stats and Test Pilot studies -  Robert Strong - in progress
* {{Bug|659181}} - 'Tune' when the updater dialog is displayed - Robert Strong
* {{Bug|657472}} -'Tune' the time to wait before displaying the update been downloaded / restart notification and provide ability to override in the update xml -  Tim Taubert. Waiting on {{Bug|659425}}
* Decide what applying an update 'quickly' means as it relates to {{Bug|659181}}
* {{Bug|659181}} - 'Tune' when the updater dialog is displayed - Robert Strong. Currently working on what 'quickly' means as it relates to when the dialog is displayed.
* Bug for collecting data to determine when we nag people - {{Bug|659425}}


== Related Bugs & Dependencies ==
== Related Bugs & Dependencies ==
Line 49: Line 47:


== Risks ==
== Risks ==
* New notification interface hasn't been created yet. This can be mitigated by using the existing interface for the time being.
* None at present.


== Use Cases ==
== Use Cases ==
Line 67: Line 65:
* Implementing a background method for updating the application ({{bug|481815}})
* Implementing a background method for updating the application ({{bug|481815}})
* Avoid having to ask for administrator password ({{bug|481815}})
* Avoid having to ask for administrator password ({{bug|481815}})
* Do the slow parts of the update asynchronously ({{bug|307181}})
* Preparing an update asynchronously to a copy of the application ({{bug|307181}})


__NOTOC__
__NOTOC__
Confirmed users
1,041

edits