Google Play to enforce Android app memory limits in 2027
Developed over time first seen 2 months ago
Google will enforce Android app memory limits through the Play Store from February 2027, potentially reducing the visibility and publishing options of apps and games that fail to comply. The move matters because developers will face both performance penalties and commercial consequences as Google responds to tighter hardware memory constraints.
The per-app limits arrived with Android 17, initially on Pixel devices, and are expected to extend across manufacturers’ phones with 4GB to more than 16GB of RAM. Apps that exceed their allowance may be slowed down or terminated, while Google plans to publish further details on Play Store enforcement later in 2026.
- Google Play will enforce app memory limits from February 2027.
- Non-compliant apps may lose visibility and publishing capabilities.
- Android 17 limits will cover devices from 4GB to 16GB-plus RAM.
New here? Start with this
Android is the operating system used by many smartphones and tablets, while Google Play is the main app store for Android devices. Google sets technical rules for apps offered there, although phone makers such as Samsung and Xiaomi also adapt Android for their own products.
The policy concerns RAM, the short-term memory a phone uses to keep apps running smoothly. An app that uses too much RAM can make a device slower, force other apps to close or use more battery, particularly on less powerful phones.
Google, app developers and device manufacturers all have a role in how these limits work. The rules matter because they could influence how developers design apps and games, and how reliably those products run for Android users on different devices.
Both sides, in good faith
The strongest fair case each way — we don't pick a winner.
The case for
Supporters argue that Play Store enforcement gives developers a necessary incentive to use memory responsibly, improving reliability, battery life and responsiveness for users, particularly on lower-end phones. They contend that common limits can reduce wasteful app design and help manufacturers manage finite hardware resources across a fragmented Android ecosystem. Linking compliance to distribution is seen as proportionate because poor memory behaviour can harm the wider device experience, not only the app concerned.
The case against
Critics argue that reduced visibility or publishing capabilities could punish legitimate, resource-intensive apps and games whose memory needs reflect sophisticated features rather than careless engineering. They may question whether a single set of per-app limits can fairly accommodate devices with vastly different RAM capacities, use cases and accessibility requirements. Strong commercial penalties, announced before detailed implementation guidance, could also favour larger developers with more optimisation resources and constrain innovation.
Full account
Google says it will begin enforcing new memory-efficiency requirements for Android apps and games distributed through Google Play from February 2027. The policy follows Android’s introduction of per-app memory limits, initially on Pixel devices with Android 17, and is intended to reduce the effect of applications that consume excessive memory on a handset’s responsiveness and multitasking.
The company frames the change against tighter hardware conditions and a wider range of Android devices, from models with 4GB of RAM to those with 16GB or more. Under Android’s existing approach, an app that exceeds its allocated limit may be slowed or ended by the system. Google has indicated that developers whose products do not meet the forthcoming Play thresholds could also face reduced visibility or limits on publishing through the store, with fuller enforcement details promised later in 2026.
One report highlights technical measures described in Google’s documentation. These include limits based on anonymous resident-set memory plus swap space, bitmap-memory use and optimisation of DEX application code. The thresholds vary by a device’s installed RAM and by app category: on an 8GB phone, for example, the cited foreground allowance is 2.25GB, while user-perceived-service and background allowances are each 1.5GB. Larger devices with more than 16GB are said to be largely outside the main limits, while games have somewhat different rules.
The same documentation also sets out a separate requirement due in April 2027: support for zero-tap restoration of sign-in credentials during device migration. Google recommends its Restore Credentials API, arguing that avoiding manual sign-in during setup can both simplify onboarding and reduce exposure to phishing or credential theft. Taken together, the measures make Play policy part of Google’s broader effort to push developers towards more efficient memory use and smoother transitions between Android devices.
Where outlets differ
Source 1 concentrates on the prospective Play Store penalties, Android 17’s arrival on Pixel phones and the broader pressure created by expensive RAM; it presents the policy chiefly as a stronger enforcement mechanism.
Source 2 provides substantially more technical detail, including example memory allowances, bitmap and DEX requirements, exemptions for high-RAM devices, and the separate April 2027 credential-restoration deadline.
Source 2 characterises the situation more directly as an imminent ecosystem-wide memory crisis, whereas Source 1 stresses hardware-market constraints and their possible influence on handset RAM configurations.
More coverage
Art Business Celebrity Companies Culture Entertainment Gadgets Software Technology
Read the full article at the source →
Originally published by The Verge as “Google tells Android app developers to cool it on memory use, or else”.