Google Play is introducing new requirements for memory usage, code optimization, and automatic login restoration when users change Android devices. Announced on August 26, 2026, the changes take effect in February and April 2027.
Memory requirements from February 2027
Play will assess dynamic memory usage, measured as anonymous RSS plus swap, and memory held by bitmaps. The thresholds vary by process state, with separate dynamic memory limits for apps and games across device RAM tiers. The Android vitals tables list the applicable limits.
For phones and tablets, Play uses P90 measurements and the last 28 days of data. Evaluation includes available data from Android 13 onward. These requirements therefore reach beyond apps running on Android 17. Measurement scope.
Android 17 also introduces limits enforced by the operating system. Excessive memory use can trigger additional compression work and eventually process termination. Teams should examine memory use across foreground, background, and cached states.
DEX optimization from February 2027
Qualifying uploads must meet a minimum of 25% coverage in each of three areas: optimization, shrinking, and obfuscation. The requirement applies to apps with more than 10 MB of DEX code and games with more than 50 MB. These are DEX code thresholds, not total download sizes. DEX requirements.
Google recommends R8, although another optimizer can meet the requirement. Review optimization settings and keep rules, then inspect the percentages reported for the actual bundle uploaded to Play Console.
Login restoration from April 2027
Apps offering optional or mandatory login must support automatic restoration of the user’s authenticated state when they transfer to another Android device. Google calls this Zero-Tap Sign-In. Games are currently exempt. Migration requirement.
The requirement covers phones and tablets. Apps without accounts are unaffected, and guests should remain guests. Block Store integrations qualify only if they successfully restore login and are in production by September 30, 2026. Other exceptions and exemption criteria are detailed in the technical requirements.
The recommended implementation uses Restore Credentials through Credential Manager. It includes creating a restore key for an authenticated user, handling restoration with the app’s backend, and deleting the key on logout. Plan for both app and backend changes.
Checks to schedule now
Inspect Android vitals memory metrics by device RAM tier and process state, including behavior after leaving the app.
Review the uploaded release bundle’s DEX size and optimization results. Test critical flows after changing R8 rules.
Audit the device migration flow with the authentication team and test both device transfer and cloud restoration.
Google says apps that miss the requirements may face reduced store visibility and publishing capabilities. Further enforcement details are still to come. Check the official announcement and technical requirements when planning releases.
