Guide
Google Play crash rate and ANR thresholds, explained
Updated
Short answer
Google Play treats an app as having bad technical quality when its user-perceived crash rate is at or above 1.09%, or its user-perceived ANR (App Not Responding) rate is at or above 0.47%, measured over 28 days. Above either line, Google Play can reduce the app’s visibility and show users a warning on its store listing.
What “user-perceived” means
User-perceived rates count only the crashes and ANRs a person actually notices, for example a crash while the app is in the foreground. Background crashes still count toward the plain crash rate but not toward the user-perceived one that Google Play enforces.
The rate is the share of daily active users who hit at least one such crash (or ANR), averaged over the last 28 days and weighted by users.
The two thresholds
Both are measured across all devices over a 28-day window:
- User-perceived crash rate: 1.09%
- User-perceived ANR rate: 0.47%
How to watch them without opening Play Console every day
Android vitals in Play Console shows both rates, but only if someone looks. Plash reads them from the Play Developer Reporting API every 15 minutes, shows the 28-day rate on the app’s dashboard, and sends a critical alert (email, phone push, Slack or Discord) when either rate reaches its threshold.