Google has announced a significant shift in how it will regulate memory usage for Android applications, attributing this move to the ongoing global shortage of RAM. Starting in February 2027, applications that exceed the newly established memory limits may face two potential consequences: Android could throttle their performance or terminate them, while the Play Store might reduce their visibility.
These new requirements were detailed in a recent post on the Android Developers Blog, with TechCrunch being among the first to highlight the changes. Google has pointed out that the mobile industry is grappling with “significant hardware supply constraints that are altering device memory availability.” In a more direct statement, the company warned of an “ecosystem-wide memory crisis” due to escalating RAM costs.
What the limits actually are
The memory thresholds are designed to scale with the device’s specifications. For instance, on a smartphone equipped with 8GB of RAM, an app can utilize a maximum of 2.25GB in the foreground, alongside 1.5GB for user-perceived services and another 1.5GB in the background. Devices boasting more than 16GB of RAM are largely exempt from these restrictions.
Google defines the primary memory usage metric as the Anonymous Resident Set Size plus Swap, which refers to the memory an app occupies without backing files. Additionally, bitmap memory has its own limits that apply universally across devices, allowing apps 200MB for user-perceived services and background processes, and 400MB for cached data. Notably, games have slightly different thresholds.
For mid-range devices, these limits are quite stringent. A contemporary application featuring a substantial image cache and an integrated browser could easily approach these caps without any unusual behavior. Furthermore, the guidelines stipulate that DEX code, which contains a compressed version of an app’s Java bytecode, must be optimized for efficient memory use, quicker launches, and enhanced runtime performance.
The penalty is distribution
Google has made it clear that non-compliance with these memory limits will have tangible repercussions. “If your app exceeds these limits, it will be slowed down and may be terminated,” the documentation states. However, the more pressing concern for developers lies in the potential reduction of app visibility on the Google Play Store. Apps that fail to meet these thresholds may find their publishing capabilities diminished, leading to lower search rankings and, consequently, fewer installations and revenue. Google has promised to provide further details on this aspect later in the year.
Where the shortage came from
The surge in demand for memory is largely driven by the booming AI data center industry, which has been consuming the resources that were once allocated for smartphones. Reports indicate that the rising costs associated with Nvidia AI servers are expected to increase by over 15% starting early next year, primarily due to memory expenses. This trend has already impacted consumers, as evidenced by Amazon’s decision to raise prices on its Echo, Kindle, and Fire TV devices by up to 60% in August. Similarly, Xiaomi has reported declining profits as the RAM shortage continues to squeeze its smartphone margins.
In response to these challenges, smartphone manufacturers have begun to reduce the amount of RAM in their devices. For example, the base models of the Pixel 11 Pro and 11 Pro XL now feature less memory than their predecessors. Google acknowledged the rising costs of RAM in July, announcing that it was reworking Android to be more memory-efficient, a change that is now being formalized as a rule applicable to all developers.
It starts with Pixel and spreads
The new per-app memory limits will first roll out with Android 17 on Pixel devices, with Google indicating that other manufacturers will soon follow suit. “Over the coming year, an increasing number of manufacturers will leverage the Android per-app memory limits across their portfolio of device RAM configurations from 4GB to 16GB+ devices,” the company stated.
This initiative builds on a previous announcement made in June, which aimed to prevent a single poorly performing app from disrupting the multitasking capabilities and overall stability of a user’s device. Google highlighted the risk posed by a single app that experiences a memory leak, consuming excessive resources and forcing Android to terminate other applications.
The squeeze lands hardest on cheap phones
Google’s guidelines encompass devices ranging from 4GB to 16GB and above, but the apps most likely to struggle will be those designed for the lower end of this spectrum. Such devices are predominantly sold in regions like Europe, India, Brazil, and Africa, rather than in tech hubs like Silicon Valley. Google positions these rules as a protective measure for users of lower-end devices, where limited RAM means that one malfunctioning app can compromise the entire system. However, a counter-argument emerges: developers are now shouldering the burden of a shortage that was largely driven by the demands of data center operators.
On-device AI is part of the problem
In addition to these memory regulations, Google is encouraging developers to implement AI models directly on devices through its Gemini Nano platform. These models will occupy the same memory that the new rules are designed to manage. The Register has pointed out the inherent tension in this directive, suggesting that on-device AI may not be contributing positively to the situation. Google has yet to address this conflict directly but is rolling out tools to alert developers when their apps approach the new memory thresholds. More comprehensive diagnostics, including a Memory Limiter feature, are expected to be introduced later this year to help manage memory consumption.
A second deadline in April
Google’s memory regulations are just one part of a broader strategy to enhance user experience. In addition to the memory limits, the company is changing the requirements for apps when users transition to new devices. By April 2027, every app available on the Play Store that offers sign-in functionality must support zero-tap credential restoration for users moving to a new phone. Google frames this requirement as a security measure, emphasizing that manual sign-ins can create friction and expose users to phishing risks. Developers are encouraged to utilize the Android Restore Credentials API to comply with this new standard.
With two significant deadlines approaching—memory and code thresholds in February 2027 and the sign-in requirement in April—developers are left to navigate the implications of these changes. However, Google has yet to clarify the extent of visibility an app may lose for failing to meet either requirement.
