Read the current metric definition
The Android vitals documentation, reviewed on 22 September 2026, describes user-perceived crash rate and the participating Play/device population. It is not simply “all crash events divided by all sessions” from any analytics system.
The published overall bad-behavior threshold is 1.09%, with separate per-device thresholds. Recheck the official table before using a threshold in a later release review.
Keep population and window visible
| Dimension | Why it changes the comparison |
|---|---|
| Install source | Play data does not represent every sideloaded build |
| User data-sharing eligibility | Not every installation contributes |
| Daily users vs sessions/events | Denominator changes the percentage |
| Version and device filters | A small affected cohort can disappear in an aggregate |
A low overall rate can coexist with a serious failure on one device family.
Prioritize by affected users and severity
Use the crash investigation guide to identify the largest actionable clusters. A repeated startup crash deserves attention even when a newer low-volume release has not accumulated much data.
Do not optimize the metric by merely suppressing reporting. Fix the user-visible failure or make the unsupported scenario fail safely.
Verify the fix before broad rollout
Reproduce the issue with the affected version/device conditions, validate an optimized release and use a controlled rollout where appropriate. Monitor the new version separately before expecting an aggregate window to recover.
Keep the static checker in context
APKLint's Vitals Checker can help organize a release review, but it does not read Play Console metrics or calculate your actual crash rate. Record the dashboard definition, window, filters and fixed crash cluster alongside the release decision so later comparisons remain meaningful.
Sources and further reading
Reference review: 22 September 2026. Examples illustrate the workflow; check your installed versions, release artifact and account-specific Console requirements before applying them. This guide is not a claim that APKLint executed your project or verified your private account.
Android inspection tools and practical release guides. About APKLint · Report a correction
