In response to the “significant hardware supply constraints that are altering device memory availability,” Google aims to reduce the memory usage of <a href="https://myappsplus.com/colorful-glass-slab-wallpapers-for-iphone-and-<a href="https://myappsplus.com/how-to-sideload-android-apps-on-your-phone-in-2026/” title=”How to sideload Android apps on your phone in 2026″>android/” title=”Colorful glass slab wallpapers for iPhone and Android”>Android apps.
On Android 17, this involves per-app memory limits that are first available on Pixel devices but will soon be adopted by an “increasing number of manufacturers.” Applications that exceed these limits “will be slowed down and may be terminated.”
Meanwhile, Google Play is establishing performance thresholds across three areas:
- Dynamic memory usage (anonymous RSS + swap): This tracks the memory used for your app’s private data storage, including both active and compressed memory. It excludes files stored on the device, such as code or assets. We will assess this usage across different app states (like when your app is in use or running in the background) and device performance categories.
- Bitmap memory usage: This evaluates the memory consumed by bitmaps. While bitmaps occupy memory when your app is in the foreground, they should not be held in memory for extended periods of time in non-visible app states such as background and cached.
- Optimized DEX code: A well-optimized Android App Bundle uses less memory, starts faster, reduces ANRs, and improves rendering and runtime performance. To ensure an optimized footprint, apps published on Google Play apps published on Google Play must be optimized with a minimum of 25% coverage across optimization, shrinking, and obfuscation using a tool such as R8 or any other shrinking tool.
Memory enforcement starts in February 2027, with Google offering several Play Console tools and metrics. Apps and games that don’t meet these thresholds “will see reduced app visibility and publishing capabilities on Google Play,” with more details coming later this year.
Today’s other announcement is a “requirement for app developers to make log-ins faster and safer during device transfers.” This will be done through a Zero-Tap Sign-In standard that requires apps to “automatically restore a user’s sign-in state when they move from one Android device to another with the Android Restore Credentials API.”
This API ensures that when a user opens your app on their new Android device for the very first time, they are instantly recognized and securely signed in without additional taps.
This will be required by Google Play starting in April 2027. Games are currently exempt, with more plans coming next year.
You’re reading 9to5Google — experts who break news about Google and its surrounding ecosystem, day after day. Be sure to check out our homepage for all the latest news, and follow 9to5Google on Twitter, Facebook, and LinkedIn to stay in the loop. Don’t know where to start? Check out our exclusive stories, reviews, how-tos, and subscribe to our YouTube channel
