Most organisations treat crash rate as an internal engineering metric. Google Play treats it as a ranking input, and the list of inputs is getting longer.
Quality Is a Distribution Lever
Google's Android vitals documentation says it without hedging: core vitals "affect the visibility of your app on Google Play," and if an app exceeds a threshold, "Play may reduce the visibility of your title" and "may also show users a warning on your store listing." On specific phone models, Google Play "will steer users on those devices away from these titles" (Play Console Help).
The thresholds are precise: a user-perceived crash rate of 1.09% or an ANR (frozen app) rate of 0.47% across all devices, or 8% on any single phone model. Google evaluates the last 28 days, so one bad release keeps costing placement for a month.
Why Google Cares
Google has explained its reasoning for years. In 2017 it found that "half of 1-star reviews mentioned app stability." In 2022 it moved to user-perceived metrics because they showed "a stronger correlation with uninstalls."
The Scope Is Expanding
- Battery, 2026. Excessive background wake locks became a core metric in November 2025, and from March 1, 2026 apps over the threshold may be excluded "from prominent discovery surfaces such as recommendations."
- Memory and code optimization, 2027. Google states that apps exceeding thresholds for "memory usage, bitmap memory usage, or code optimization may see store visibility impact starting from February 2027." Play's technical quality requirements also set a minimum of "25% optimization, obfuscation and shrinking" for larger apps.
What Leadership Should Change
Put the vitals on the same dashboard as revenue and acquisition, because they feed both. Alert per device model, not just on the average. Gate staged rollouts on them. And budget the 2027 memory work now, while it is an engineering project rather than a visibility incident. The Play Developer Reporting API makes the data available to any internal reporting stack.
-Rocky
#AndroidVitals #AppQuality #GooglePlay #EngineeringDreams #StrategiaX
Originally published on ANDROID-ARCHITECT, the Android engineering blog of Strategia-X.
