Android Play Developer Console: Vitals, Pre-Launch Reports and Quality

Play Console Store team

November 19, 2026

Share:

Table of Contents

Estimated progress
Interactive Guide

The Android Play developer console ships with a quality-monitoring suite most developers ignore until it hurts them: Android vitals, pre-launch reports, and the device catalog. Here’s what many don’t realize — Google uses your vitals data in ranking. Apps that cross the bad-behavior thresholds for crashes and ANRs get demoted in search and browse. Quality isn’t just user experience; it’s discoverability.

In short: Android vitals directly affect your Play Store ranking, so treat quality as discoverability. Keep crash rates below about 1.09 percent of sessions and ANR rates below about 0.47 percent, set vitals alerts, gate every release promotion on a clean pre-launch report, and use the device catalog to isolate device-specific problems.

This guide covers the quality side of the console in depth: what vitals measure and the exact thresholds, how to read and act on pre-launch reports, managing the device catalog, and the crash-fixing workflow that keeps you above the thresholds. For the publishing pipeline, see our Play Store dev console guide.

Android Vitals: The Metrics That Affect Your Ranking

Console path: Quality → Android vitals.

Vitals tracks three core metrics against Google’s bad-behavior thresholds:

Crash rate

Percentage of daily sessions ending in a crash. The bad-behavior threshold sits around 1.09% of sessions (Google adjusts it periodically — check the vitals page for the current figure). Cross it and your app is flagged; sustained violation affects discoverability.

ANR rate (Application Not Responding)

Percentage of sessions with an ANR — the infamous “app isn’t responding” dialog. Threshold is around 0.47% of daily sessions. ANRs usually come from doing heavy work on the main thread: network calls, database queries, or image decoding blocking the UI.

Excessive wakeups and stuck partial wake locks

Background battery abuse. Less visible to users than crashes but flagged in vitals and increasingly enforced.

How to read the dashboard: vitals shows your rate vs. the threshold as a timeline, broken down by app version, device, and Android version. The breakdowns are the diagnostic gold — a crash rate that’s fine overall but terrible on one device model points at a device-specific issue (GPU driver, manufacturer skin), not your code generally.

The table below summarises the core vitals metrics and their thresholds:

MetricBad-behaviour thresholdNotes
Crash rateAround 1.09% of daily sessionsPercentage of daily sessions ending in a crash; sustained violation affects discoverability
ANR rateAround 0.47% of daily sessionsPercentage of sessions with an “app isn’t responding” dialog, usually from heavy work on the main thread
Excessive wakeups and stuck partial wake locksFlagged in vitalsBackground battery abuse; less visible to users than crashes but increasingly enforced
Android vitals metrics and their quality thresholds infographic
Infographic — Android vitals metrics and their quality thresholds

Setting Up Vitals Alerts (Do This Today)

Console path: Quality → Android vitals → Manage alerts (bell icon).

Configure alerts for:

  • Crash rate crossing the bad-behavior threshold — the critical one.
  • ANR rate crossing threshold.
  • New crash clusters appearing in a fresh release — catches regressions within hours of rollout.

Route alerts to the email (or group alias) your on-call developers actually read, plus enable push via the Play Console mobile app. The difference between catching a crash spike at hour 2 vs. day 3 is often a full star of rating.

Pre-Launch Reports: Free Testing on Real Devices

Console path: Quality → Pre-launch report (generated automatically for every AAB uploaded to any track).

Every upload gets robo-tested on roughly 10 real device models in Google’s lab. The report includes:

  • Crashes found, with stack traces and the exact robo-crawl steps to reproduce.
  • Screenshots of every screen the crawler reached — review these for layout breakage on odd aspect ratios.
  • Performance data: startup time, slow rendering frames.
  • Accessibility issues: tiny touch targets, missing content descriptions.
  • Security warnings: vulnerable libraries, exposed secrets.

Workflow: make the pre-launch report a release gate — no promotion from closed to open testing (or to production) until the report is clean or its findings are triaged. The most valuable catches are device-specific crashes you’d never reproduce on your own Pixel: Samsung-specific WebView quirks, Xiaomi background restrictions killing your service, foldable layout breaks.

Pro tip: the crawler can’t log in. If your app requires authentication, provide demo credentials in the pre-launch report settings so the crawler tests behind the login wall — otherwise half your app goes untested.

Device Catalog: Know Your Install Base

Console path: Quality → Device catalog (and Reach and devices).

The catalog lists every device model your app supports, with per-device install and vitals data. Use it to:

  • Exclude problematic devices deliberately (Device catalog → select device → Exclude) instead of letting them generate 1-star reviews. Legitimate for devices with broken drivers your app can’t work around.
  • Decide minSdkVersion with data: Reach and devices shows your audience by Android version. If 0.3% of users are on Android 8, dropping support is a business decision you can defend.
  • Prioritize testing: sort by install base and ensure your top 20 device models are in your physical or cloud test lab.

Caution: exclusions reduce your addressable market and can look like you’re hiding from bad reviews if overused. Exclude for genuine incompatibility, not to dodge vitals thresholds — Google sees through that.

The Crash-Fixing Workflow That Works

When vitals flags an issue:

  1. Triage by impact: sort crash clusters by affected sessions, not raw count — one crash hitting 5% of users beats ten crashes hitting 0.01%.
  2. Read the vitals stack traces first, then reproduce with the pre-launch report’s steps or Firebase Crashlytics breadcrumbs.
  3. Check the version breakdown: did the crash start with your latest release? If yes, it’s a regression — consider halting the rollout (Release → Production → Halt rollout) while you fix.
  4. Fix, then verify in pre-launch before shipping the hotfix — don’t let the fix introduce its own crash.
  5. Ship via staged rollout and watch vitals for 48 hours before going to 100%.
  6. Post-mortem: add a regression test; update your release checklist if the process failed.

For release-track mechanics, see our release management guide.

Vitals and Store Programs

Quality metrics gate more than ranking — they affect program eligibility:

  • Editorial featuring: Google’s editorial team considers vitals when selecting featured apps. A crash rate above thresholds disqualifies you regardless of design quality.
  • Designed for Families: stricter vitals expectations apply; family apps are held to higher stability bars.
  • Play Points partnerships and similar programs factor in sustained quality signals.
  • Pre-registration campaigns: launching a broken build to a pre-registered audience wastes the entire campaign — vitals-gate your launch build the same way you gate production releases.

Treat vitals as a product requirement, not a dashboard — “ship only when crash-free sessions exceed 99.5%” belongs in your definition of done alongside feature completeness. Our publishing pipeline guide shows where the quality gates fit in the release sequence.

Benchmarks: What’s “Good”?

  • Crash-free sessions: top apps run 99.5%+. Below 99% and you’re in the danger zone.
  • ANR-free sessions: target 99.5%+; ANRs are more user-visible than most crashes (the dialog invites a force-close + 1-star review).
  • Startup time: under 2 seconds cold start on mid-range devices keeps users; over 5 seconds bleeds them.
  • APK/AAB size: every 6MB of size costs roughly 1% of installs (Google’s own data) — vitals-adjacent, but size discipline is quality discipline.

Google’s official vitals documentation lives in the Play Console Help Center.

The table below summarises the quality benchmarks given above:

MetricBenchmark
Crash-free sessionsTop apps run 99.5%+; below 99% is the danger zone
ANR-free sessionsTarget 99.5%+
Startup timeUnder 2 seconds cold start on mid-range devices; over 5 seconds bleeds users
APK/AAB sizeEvery 6MB of size costs roughly 1% of installs (Google’s own data)

Android Play Developer Console: Key Takeaways

The Android Play developer console quality suite — vitals with ranking-linked thresholds, free pre-launch device testing, and the device catalog — makes quality measurable and actionable. Set vitals alerts today, gate every promotion on pre-launch reports, and treat threshold crossings as P0 incidents. Quality isn’t just UX; it’s discoverability.

Pre-launch reports testing on real devices before release in the Android Play developer console
Pre-launch reports testing on real devices before release

Frequently Asked Questions

What are Android vitals bad-behavior thresholds?

Google’s published limits for crash rate (~1.09% of daily sessions), ANR rate (~0.47%), and background battery abuse. Crossing them flags your app in the console and can reduce your discoverability in Play Store search and browse. Check Quality → Android vitals for current figures.

Do crashes really affect my Play Store ranking?

Yes. Google has confirmed that technical quality signals — primarily crash and ANR rates vs. thresholds — feed into ranking. An app with a 3% crash rate will rank below an equivalent-quality app at 0.2%, all else equal.

What is a pre-launch report in the Play Console?

An automated test report generated for every AAB upload: Google’s robo-crawler runs your app on ~10 real devices and reports crashes, screenshots, performance, accessibility, and security issues. It’s free — use it as a release gate before every promotion.

How do I exclude a device from my app?

Quality → Device catalog, find the device, and set it to Excluded. Use this for genuine incompatibility (broken drivers, missing hardware), not to hide from bad vitals — and remember exclusions shrink your market.

Why is my crash rate fine overall but terrible on one device?

Device-specific issues: GPU driver bugs, manufacturer Android skins, aggressive background killers (common on some Chinese OEMs), or foldable form factors. Use the vitals version/device breakdown to isolate, then exclude or work around the specific device.

Conclusion

The Android Play developer console’s quality tools — vitals with its ranking-linked thresholds, free pre-launch device testing, and the device catalog — turn quality from a vague aspiration into measured, alerted, actionable work. Set up alerts today, gate releases on pre-launch reports, and treat threshold crossings as the P0 incidents they are.

Play Console Store is an independent marketplace helping Android developers with quality monitoring, crash triage, and vitals recovery. Explore our Google Play services to keep your metrics green.

KNOWLEDGE BASE

Related Android Developer Field Manuals

Developer Play Store Console: Review Management and Rating Recovery

Your app’s rating is part of your store listing — users see it before your screenshots — and in the

Android Play Developer Console: Vitals, Pre-Launch Reports and Quality

The Android Play developer console ships with a quality-monitoring suite most developers ignore until it hurts them: Android vitals, pre-launch

Play Store Google Console: ASO, Listings and Conversion Guide

Inside the Play Store Google Console (play.google.com/console), the section that most directly controls your revenue isn’t Release or Monetize —

Get notified when Google updates Play Console policies or SDK requirements.

Join 12,000+ Android developers who receive our quarterly policy diff summaries, rejection workarounds, and ready-to-use boilerplate releases.