Google Play sets new app memory limits for February 2027, Zero-Tap Sign-In to follow in April

Google Play is introducing new technical quality requirements for Android apps and games, with memory usage and code optimization thresholds taking effect in February 2027 and a separate Zero-Tap Sign-In requirement arriving in April 2027. Apps that fail to meet the standards may face reduced visibility and publishing capabilities on Google Play.

The changes come as Google responds to what it describes as significant hardware supply constraints affecting the amount of memory available on mobile devices. Android 17 introduced per-app memory limits starting on Pixel devices, and Google has said an increasing number of Android manufacturers will adopt those limits across devices ranging from 4GB to more than 16GB of RAM. Apps that exceed Android’s system-level limits can be slowed down and, if memory consumption continues to rise, terminated.

Google Play’s new requirements build on those Android-level protections by establishing measurable thresholds across dynamic memory usage, bitmap memory usage and DEX code optimization.

Dynamic memory usage will be measured using Anonymous RSS + Swap, covering private memory used by an app, including active and compressed memory, while excluding files stored on the device such as code and assets. Google will evaluate consumption across different app states and device RAM categories.

The limits vary depending on whether the software is an app or game, the amount of RAM available on the device and whether the process is in the foreground, providing a user-perceived service or running in the background. Games receive higher thresholds than apps in several categories because of their typically greater memory requirements.

For example, on devices in Google’s 4GB RAM tier, regular apps have a foreground Anonymous RSS + Swap threshold of 2GB, compared with 2.25GB for games. On 8GB devices, those thresholds increase to 2.25GB for apps and 3.5GB for games, while 16GB devices have respective limits of 4.25GB and 5GB.

Google is separately measuring bitmap memory usage, with the company warning that bitmaps should not remain in memory for extended periods when an app is no longer visible. Under the published thresholds, apps and games have a 90th-percentile bitmap memory limit of 200MB for user-perceived services, 200MB in the background and 400MB when cached.

Code optimization will become another requirement. Android App Bundles published through Google Play must reach at least 25% coverage for optimization, shrinking and obfuscation, using R8 or another shrinking tool. Google says optimized DEX code can reduce an app’s memory footprint while improving startup, rendering and runtime performance and reducing application-not-responding events.

Google has already begun adding tools to Play Console to help developers prepare. Android vitals now provides dynamic and bitmap memory metrics that can be analyzed across percentiles and RAM categories, while a new Crashes and ANRs filter can identify instances where Android terminated an app because of severe memory pressure.

Play Console is also adding DEX optimization insights for newly uploaded app bundles and proactive warnings when an app or game exceeds the upcoming thresholds. Developers can additionally receive alerts for issues including unoptimized bitmaps, limited DEX optimization and limited split-bundle usage. Google says further diagnostics will arrive later this year, including information about time spent in different app states and deeper visibility into Android’s Memory Limiter.

Beginning in February 2027, compliance will no longer be advisory. Apps and games will be expected to stay within their respective thresholds for Anonymous RSS + Swap memory, bitmap memory and DEX optimization. Google says titles that fail to meet the requirements may see reduced Google Play visibility and publishing capabilities, with further enforcement details due later this year.

A second requirement will follow two months later. Starting in April 2027, apps that support user accounts — whether sign-in is optional or mandatory — will need to support Google’s Zero-Tap Sign-In standard when users migrate to a new Android device.

The requirement uses the Android Restore Credentials API to restore a user’s authenticated state during device-to-device transfer or cloud backup. When users open a restored app on their new device for the first time, the system is designed to recognize and sign them in without requiring them to enter their credentials again.

Google says apps that do not meet the Zero-Tap Sign-In requirement could lose full publishing capabilities and optimal Play Store visibility. Games are currently exempt, although Google plans to provide dedicated guidance for more complex game authentication scenarios in 2027. Games that use a single-account sign-in system are being encouraged to adopt the Restore Credentials API in the meantime.

The two deadlines give Android developers separate compliance windows for performance and onboarding. Memory usage, bitmap consumption and code optimization will begin affecting Google Play standing in February 2027, followed by mandatory account restoration for applicable apps in April. Together, the requirements expand the role of technical quality metrics in determining how apps can be published and surfaced through Google Play.