Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add a force upgrade path? #41

Open
Gregliest opened this issue Feb 9, 2017 · 0 comments
Open

Add a force upgrade path? #41

Gregliest opened this issue Feb 9, 2017 · 0 comments

Comments

@Gregliest
Copy link
Collaborator

Basically, how do we want to encourage or force people to upgrade the app? Android users are generally bad about upgrading, and if we ever deprecate part of the API, or make other breaking changes, we may want a way to make sure no one is using the affected old versions.

There are generally two ways to go about this:

  1. Soft upgrade (dismissable)
  • Something like an in app modal or push notification that's dismissable, alerting the user that there's a new version, and/or that their current version is now broken.
  • Pros: Not as intrusive.
  • Cons: Not 100% effective.
  1. Force upgrade
  • Lock the user out of the app with a link to the Play store to upgrade.
  • Pros: It guarantees that we get users off the affected old versions.
  • Cons: It's obviously intrusive to the user.

In my opinion, if we include a force upgrade code path, it should be for emergencies only. Emergencies can include hotfixes (if we release a version that is unusable for some reason). I would generally shy away from using the force upgrade to move users off of old versions, unless those versions are REALLY old, and they are becoming a significant maintenance burden.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant