Google Play memory limits: RAM is now a distribution rule

Google Play just turned memory usage into a distribution requirement. In an Android Developers post published August 27, Google set enforceable thresholds for how much RAM your app consumes — and said apps that exceed them face reduced Play Store visibility and publishing capability starting February 2027. If you ship an Android app, memory optimization stopped being hygiene and became a ranking input.

What actually happened

Three thresholds land in February 2027, measured through Android vitals:

Dynamic memory usage — anonymous RSS plus swap, the private data your app holds in active and compressed memory. It excludes code and asset files. Thresholds vary by device RAM tier and by app state, and differ for apps versus games.

Bitmap memory usage — how much memory images hold. Google's specific complaint: bitmaps that stay resident when the app is backgrounded or cached.

Optimized DEX code — a floor of 25% coverage for optimization, shrinking and obfuscation via R8 or an equivalent. Google's stated payoff is lower memory, faster start, fewer ANRs.

Exceed a "bad behavior" threshold and Play may reduce your title's visibility and show a warning on your store listing. Play Console is getting the instrumentation to match: dynamic memory metrics in Android vitals, an out-of-memory crash filter, DEX optimization insights and proactive alerts. Exact numbers arrive later in 2026.

A second deadline rides along. From April 2027, apps with sign-in must restore session state automatically on device migration through the Restore Credentials API. Games are exempt for now.

Why memory thresholds matter for your business

Here is the part Google does not spell out. AI datacenters are consuming memory production, and the squeeze lands hardest on budget phones. Google is not asking developers to be tidy — it is rationing a constrained resource by pushing the cost onto app builders instead of onto device makers who cannot get chips.

For a small business with a customer-facing app, that reprices a specific kind of technical debt:

• Bitmaps are the usual culprit. Full-resolution product photos cached in memory, image libraries with no eviction policy, a gallery that never releases. Cheap to fix, expensive to ignore.
• R8 is probably already in your build and probably not on. A 25% floor is not aggressive. Check your release config before you plan anything harder.
• Test on the cheap phone. Thresholds are tiered by device RAM. Your flagship test device will pass a bar your actual customers' 4 GB phone fails.
• Fix it now, not in Q4 2026. Enforcement is February 2027 and the exact numbers land before then. Instrumentation is already shipping in Play Console — start reading your own vitals this quarter and you will know where you stand before the threshold is published.

The deeper read: platform owners are starting to enforce efficiency because compute and memory are no longer abundant. Expect the same logic to reach other surfaces. Build lean because the platform will eventually make you.

Sources: Android Developers Blog, TechCrunch.