How do updates reach users, and how are older versions supported?
Web users always have the latest version as soon as it is deployed. Mobile updates go through app store review and reach users gradually, so some users will be several versions behind at any time. The backend must therefore continue to support older app versions, with APIs versioned and changed in a backward-compatible way.
Two features should be part of the first release: remote configuration, which allows behaviour to be changed without a new build, and a minimum-version check, which allows unsupported or insecure versions to be retired.
Forced updates should be used only for security issues or genuine incompatibility.
API changes should be additive: adding new fields and endpoints rather than renaming or changing existing ones, and removing old versions only when usage data shows it is safe.
We recommend publishing a clear support window, such as the current version and the two previous versions.
Related service
Mobile App DevelopmentiOS and Android apps from one codebase, with offline support and app store submission.
Was this helpful?