I’m working on the backend for our app and currently reworking the update logic and am a little unsure about how to deal with the particular case where:
The user hasn’t used the app for a while and skipped a couple of updates which included at least one forced version, but the latest version doesn’t require a force update.
Say the user is at ver1.0, and the current latest version available is ver3.0 which is optional. In between theres 2.0 thats mandatory.
At the moment I have 3 plans in mind:
- Simply inform the user that their current version is out of date and prompt the user to update to the latest version 3.0 despite it being an optional update. This seems logical and feels like what I would like the app the work if I were the user, but I can’t help feeling like I’m not being truthful by forcing the user to update to a version thats in fact not mandatory.
- Prompt the user to update to the last mandatory version they have skipped, in this case 2.0. However, this would mean that soon as the user open the updated app, they’ll get hit with an update prompt again telling them theres a newer version, which might just end up annoying.
- Give user the option to choose whether they want to update to the latest version, or just the latest mandatory version, but this would bring some additional changes needed for the app dev, and I wonder if it’s really necessary in the first place to expose the user with both choices.
Any adivce would be appreciated!
b233 is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.