Technical guide · Google Play
Android Vitals: The Crash & ANR Rates That Hurt Visibility
The exact Android Vitals crash rate and ANR thresholds that reduce your app's visibility on Google Play, and why testing on real devices before launch keeps you under them.
Android Vitals isn't just an info panel in Play Console: two of its metrics — user-perceived crash rate and ANR rate— are core vitals, meaning crossing certain thresholds directly reduces how much Google Play recommends your app, with or without changes to your listing or keywords.
The exact thresholds
| Metric | Overall threshold | Per-device threshold |
|---|---|---|
| Crash rate (user-perceived) | ≥ 1.09% of daily active users | ≥ 8% on a single model |
| ANR rate (user-perceived) | ≥ 0.47% of daily active users | ≥ 8% on a single model |
Cross the overall threshold and your app becomes less discoverable on every device. Cross the per-device threshold on a specific phone model and Google Play stops recommending your app to users on that model, possibly with a warning on the store listing.
Why this can catch you off guard
The per-device threshold (8%) is easy to cross without noticing: your overall crash rate might look perfectly healthy, but if a budget model or a specific manufacturer accounts for only 3-4% of your users and its crash rate there is 15%, you're already penalized on that segment — even though the aggregate number hides it.
How this connects to pre-launch testing
Catching these issues in production means you've already crossed the threshold and are losing visibility while you fix it. The alternative is covering varied manufacturers and device categories in your closed test before requesting production — exactly what Tester Marketplace campaigns support with manufacturer and device-category targeting (phone, tablet, foldable) and a dedicated device compatibility test focus.