Google to Limit Android App Memory Use from 2027

The new requirements, detailed this week on the Android Developers Blog, were first spotted by TechCrunch. Google cites significant hardware supply constraints as the driving force, and its technical documentation bluntly warns of an ecosystem-wide memory crisis tied to rising RAM costs, a detail first noted by The Register.

The global AI data center boom is consuming vast amounts of memory, leaving less available for smartphones. Consumers are already feeling this squeeze. TNW reported in May that AI is killing the cheap smartphone, and Nvidia AI server prices are projected to rise over 15% next year due to memory costs. Amazon raised prices on its Echo and Kindle devices by up to 60% overnight in August, Xiaomi’s profit fell again as the squeeze hit phone margins, and manufacturers are responding by simply installing less RAM in new devices.

The new thresholds scale with device memory. On an 8GB RAM phone, an app can use a maximum of 2.25GB in the foreground, 1.5GB for user perceived services, and 1.5GB in the background. Devices with over 16GB of RAM are largely exempt from these limits.

• Google measures memory as Anonymous Resident Set Size plus Swap
• Bitmap memory has a separate cap: 200MB for user perceived services and background, 400MB cached
• These limits are tight for modern apps with large image caches or embedded browsers
• DEX code optimization is also required, aimed at faster launches and better runtime performance on modest memory

Google is clear about the consequences for apps that don’t comply. Its documentation states that a non compliant app will be slowed down and may be terminated. The more serious threat, though, is commercial. Apps that miss these thresholds may see reduced app visibility and publishing capabilities on Google Play, according to Google. Reduced visibility hits installs and revenue directly, and the company says more detail on the scale of that impact is coming later this year.

These memory limits arrived first with Android 17 on Pixel phones. Google confirmed higher Pixel 11 prices in July because of surging RAM costs, and said at the time it was redesigning Android for lower memory use. That rework now extends to every developer on the platform.

The rules span devices from 4GB to 16GB of RAM and above, and phones with just 4GB will face the most pressure, since a single misbehaving app can degrade the entire device. Developers are now absorbing the cost of a shortage created almost entirely by data center demand. Adding to the tension, Google’s own push for on device AI through platforms like Gemini Nano also consumes memory, a conflict the company hasn’t directly addressed.

Memory rationing is only the first of two changes coming to the platform. In April 2027, all Play Store apps offering sign in must support zero tap credential restoration for new device setups. Google frames this as a security measure, arguing that manual sign ins expose users to phishing, and points developers to the Android Restore Credentials API. Two dates now matter for every Android developer: February 2027 for memory and code thresholds, and April 2027 for the sign in requirement. Google has not yet published how much store visibility an app forfeits for missing either deadline.

Hashlytics Take

Google is framing this as an optimization push, but the RAM shortage is really doing double duty here. Data centers get first claim on global memory supply because that’s where the AI money is, and phone manufacturers get what’s left over, which is less and pricier. Google’s answer isn’t to absorb that cost or slow down its own on device AI ambitions. It’s to push the burden onto developers through compliance deadlines with real commercial teeth. The apps that get hurt first won’t be the well funded ones with dedicated performance teams. They’ll be the smaller developers building for budget phones, which is exactly the segment already being squeezed out by rising hardware costs.