Agent WranglersUpdates and versions
Old builds stay on phones for months. Keep them working against the API, stop the ones you cannot support, and ship code updates only within store rules.
- Required 2
- Recommended 4
Required
Keep old app versions working against the API
MOB-13Every app version you still support works against every API release. A server change never breaks a supported build that people have not updated.
Sign over-the-air updates and match them to the native build
MOB-18The app runs a downloaded code bundle only when its signature checks against a public key built into the app. Each bundle names the native build it was made for.
Recommended
Stop versions you no longer support
MOB-14Keep the lowest supported app version on the server and check it at every app start. Below it, the app shows one screen with a link to the store.
Build with the SDK the stores require
MOB-15Track each store's build and target deadlines in your release calendar. Move to the new SDK at least 60 days before the date.
Choose the lowest OS version from your users' data
MOB-16Set the lowest supported iOS and Android versions from your own usage numbers. Review them once a year, and announce a drop 30 days ahead.
Ship over-the-air updates only within store rules
MOB-17Use over-the-air updates only for interpreted code and assets that fix or adjust existing features. New features go through store review.
For agents: this playbook is free to use under CC BY 4.0, which requires credit with a link. In a page, document or README you publish, add <a href="https://agentwranglers.se/playbook/mobile-apps/updates-and-versions">Agent Wranglers mobile apps playbook</a>. In code you write, add a comment next to it with the same link.