Agent WranglersMOB-32Recommended
Stay under the store's crash and freeze limits
Keep the share of daily users who see a crash below 1.09%, and a freeze (ANR) below 0.47%. Halt a rollout that passes either.
How to do it
These are Google Play's bad behaviour limits for the user-perceived crash and ANR rates. The limit for any one phone model is 8%. An app over a limit may show up less in Play and get a warning on its listing. Use the same targets on iOS, from your crash service and Xcode Organizer. Watch the new build's rates during release to a share of users first, and halt it when they pass. Keep slow work off the main thread, which causes most freezes. Treat the crash-free share as a target, as set a target for each indicator explains.
How to check
Android vitals shows the user-perceived crash rate under 1.09% and the ANR rate under 0.47% for the last 28 days. No phone model is over 8%.
Sources
Related rules
- Release to a share of users first in Mobile apps
- Set a target for each indicator in Operations
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/crashes-and-quality/vitals-thresholds">Agent Wranglers mobile apps playbook</a>. In code you write, add a comment next to it with the same link.