Google introduces Android app memory thresholds amid supply constraints
Google has announced new Android app quality requirements that set performance thresholds for memory use and code optimisation, citing significant hardware supply constraints that are changing the amount of memory available in devices. Android app and game developers have until February 2027 to meet the new thresholds.
The changes cover dynamic memory usage and bitmap usage. Google is also introducing code-optimisation requirements intended to reduce performance-related app slowdowns and crashes. The company presents the measures as a way to preserve app quality as memory becomes less readily available, especially in lower-cost devices where pricing is a central constraint.
Memory efficiency becomes an Android quality requirement
The policy reflects an industry-wide memory chip shortage driven by demand from AI data centres. For mobile developers, the practical result is that an app's memory footprint may have a more direct effect on the experience delivered to users, particularly on devices with tighter hardware limits.
Google says it will establish performance thresholds across several areas rather than treating memory optimisation as a purely voluntary engineering goal. Apps that use excessive dynamic memory or bitmap resources can place more pressure on a device, while inefficient code can contribute to slowdowns and crashes.
To support adoption, Google is rolling out tools that will alert developers when their apps exceed the new thresholds. Additional diagnostic capabilities are planned for later this year. These include deeper insights from a Memory Limiter feature, which prevents apps from consuming too much device memory.
Credential restoration gains a separate deadline
Google is coupling the memory initiative with a requirement for smoother device migration. By April 2027, all Play Store apps with optional or mandatory user sign-in must meet the Zero Tap Sign-In requirement when users move between Android devices.
The standard requires apps to restore a user's sign-in state automatically through the Android Restore Credentials API. This is distinct from the memory thresholds, but it places another deadline on teams responsible for Android release quality, identity flows and migration testing.
What development teams should prepare
The requirements are documented on Google's Android Developer site and give teams a long implementation window. That window can be used to measure dynamic allocations and bitmap use, investigate performance failures identified by Google's alerts, and incorporate the forthcoming diagnostics into testing processes.
For businesses operating Android apps, the immediate implication is to treat memory consumption and credential restoration as release-planning work now: efficient code and assets can help maintain app quality on constrained devices, while tested sign-in restoration can reduce friction when customers change phones.