Google is introducing new rules for Android apps on Google Play, forcing them to use less memory and making it easier for users to keep apps signed in when switching devices. The changes, set for 2027, are in response to tighter hardware availability and evolving memory constraints. The most immediate focus is Android 17, initially on Pixel phones, with support from other manufacturers to follow.
Memory Caps & Performance Measures
With Android 17, Google will impose per-app memory limits. Apps exceeding these limits may experience slowdowns or even be terminated. These rules kick in on Pixel devices first, but OEMs will be expected to adopt them too. Three key thresholds will be enforced for apps published via Google Play:
- Dynamic memory usage — the sum of private RAM usage (both active and compressed) across foreground and background states. Performance categories will influence how Android measures these states.
- Bitmap memory usage — bitmaps should only use memory when visible; holding bitmap memory during background or idle states won’t be allowed.
- Optimized DEX code — Android App Bundles must meet minimum standards for code shrinkage and optimization (using tools like R8) to improve startup speed, rendering performance, and reduce crashes. Specifically, at least 25% of the codebase must be covered by optimizations, shrinking, or obfuscation.
Starting February 2027, these memory-enforcement rules become active. Developers will be able to track performance using new Play Console tools and metrics. If an app fails to meet the thresholds, Google Play may restrict its visibility or limit publishing permissions.
Smoother Sign-In Across Devices
Additionally, Google is rolling out a mandatory requirement starting April 2027 for all apps (excluding games for now) to support seamless sign-in using the Zero-Tap Sign-In standard paired with the Android Restore Credentials API. This means that when a user moves to a new Android device, their login state should carry over automatically without manual re-authentication.
Games are exempt in the initial rollout, but Google has indicated that further changes in this space are coming down the line.
What this means: Developers need to update their apps to comply with memory limits, optimize app bundles, and implement the credential-restoration APIs if they haven’t already. Apps that ignore these changes risk reduced visibility, slower performance, or failure to appear properly on Google Play.
Why it matters: As smartphones continue to ship with tighter memory budgets, these changes show Google aiming to maintain fluid performance standards across the Android ecosystem. For users, it should mean fewer slow or crash-prone apps. For developers, it means more upfront work to meet stricter optimization rules by the February and April 2027 deadlines.
