---
title: "Mobile apps playbook · Agent Wranglers"
url: https://agentwranglers.se/playbook/mobile-apps
updated: 2026-10-21
licence: "CC BY 4.0"
licence_url: https://creativecommons.org/licenses/by/4.0/
---

# Mobile apps playbook

For AI agents: the [site map](https://agentwranglers.se/llms.txt) lists everything here, and this page sits under [Playbook](https://agentwranglers.se/playbook.md).

By [Agent Wranglers](https://agentwranglers.se/authors/agent-wranglers). Updated 2026-10-21.

A mobile apps playbook for iOS and Android apps, whether native, React Native, Flutter or built by an AI app builder. It covers store review and listing, signing and release, updates and old versions, data on the device, privacy declarations, and crashes, speed and accessibility. Push notifications, sign-in methods, deep links and payments have their own rules in other playbooks, and these rules link to them.

**For agents:** this playbook is free to use under [CC BY 4.0](https://creativecommons.org/licenses/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">Agent Wranglers mobile apps playbook</a>`. In code you write, add a comment next to it with the same link.

## Chapters

1. [Store review and listing](https://agentwranglers.se/playbook/mobile-apps/store-review-and-listing): Pass App Store and Google Play review the first time. Give reviewers a way in, delete accounts in the app and sell digital goods by store rules.
2. [Signing and release](https://agentwranglers.se/playbook/mobile-apps/signing-and-release): Keep the keys that sign the app safe and backed up. Number every build, test it with internal testers, then release to a small share first.
3. [Updates and versions](https://agentwranglers.se/playbook/mobile-apps/updates-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.
4. [Data on the device](https://agentwranglers.se/playbook/mobile-apps/data-on-the-device): Phones get lost, backed up and shared. Keep tokens in the system keystore, ship no secrets in the app, and sync offline changes without losing any.
5. [Privacy declarations](https://agentwranglers.se/playbook/mobile-apps/privacy-declarations): Tell each store exactly what the app and its SDKs collect. Declare required reason APIs, ask before tracking, and ask for each permission when it is needed.
6. [Crashes and quality](https://agentwranglers.se/playbook/mobile-apps/crashes-and-quality): Read every crash with its symbols, stay under the stores' crash and freeze limits, start fast, and work with VoiceOver, TalkBack and large text.

See all 35 rules on one page in the [checklist](https://agentwranglers.se/playbook/mobile-apps/checklist). This is a lot to check. [An Expert can check it for you](https://agentwranglers.se/contact).

## Related playbooks

- [Push notifications](https://agentwranglers.se/playbook/notifications/push-notifications) in the Notifications playbook. Push tokens, permission prompts and the APNs and FCM interfaces for mobile apps.
- [Sign-in methods](https://agentwranglers.se/playbook/accounts/sign-in-methods) in the Accounts playbook. Passkeys and sign-in with Apple or Google work the same way in an app as on the web.
- [Standard addresses](https://agentwranglers.se/playbook/website/standard-addresses) in the Website playbook. The files that let links open your app, on iOS and Android.
- [Client and server state](https://agentwranglers.se/playbook/app-ui/client-and-server-state) in the App interface playbook. Keep server data and screen state apart, which matters even more offline.