Add notifications to nag and/or force users to update to the latest version of the app. The priority of each release can be set during our CI process.
My proposed update forcing strategy is below. The intent is to limit the number of older releases we have to maintain compatibility with, so this is intentionally aggressive.
If the app update priority is 5, it has to be installed immediately
If the app update priority is 4, and the update staleness (days since update was released) is <=1 day, show an optional update prompt. If the update staleness is at least 1 day, immediately install the update.
If the update priority is 3 and the update staleness is at least 4 days, show an optional update prompt.
If the update staleness is at least 14 days regardless of priority, show an optional prompt.
If the update staleness is at least 21 days regardless of priority, immediately install the update.
Minor UI improvements: Low-priority update; request neither an optional update nor an immediate update. Update only when the user isn't interacting with your app.
Performance improvements: Medium-priority update; request an optional update.
Critical security update: High-priority update; request an immediate update.
Update priority
Description
Examples
Update timeline for users
0/1/2
Very low or low priority
UI touchups that don't impact functionality, releases with options to opt-in to beta features
No prompt initially. Optional prompt starting 14 days after release. Immediate update 21 days after release.
Add notifications to nag and/or force users to update to the latest version of the app. The priority of each release can be set during our CI process.
My proposed update forcing strategy is below. The intent is to limit the number of older releases we have to maintain compatibility with, so this is intentionally aggressive.
App update priorities, inspired by Google's suggestions: