Google Play Console metric
Android vitals: user-perceived crash rate
Google Play's bad behavior thresholds for crashes, what happens when you cross them and how to watch the number before a rollout.
Definition
The share of daily active users who saw a crash while using the app. Google Play's bad behavior threshold is 1.09% overall and 8% on any single phone model (4% per watch model), measured over the last 28 days.
Where to find it
The Android vitals dashboard in Play Console, or the Google Play Developer Reporting API
The common mistake
Android vitals counts issues per daily active user, while tools like Crashlytics count per session, so the numbers won't match. Google's example: one crash in three sessions on one day is a 100% crash rate in Android vitals and 33% in Crashlytics. The overall rate can also look fine while one popular phone model is over 8%, so check the device breakdown.
What to use it for
A release gate. During a staged rollout, compare the new version's crash rate with the previous one before raising the percentage. Google says that over a threshold, Play may reduce your app's visibility and show a warning on your store listing.