Google has told app developers that the per-app memory limits it shipped in Android 17 on Pixel phones will spread across the wider Android ecosystem over the next year, reaching devices with anywhere from 4GB to more than 16GB of RAM. The instruction went out in a developer blog post dated 19 August, and the reason Google gives for it is one phone buyers have been living with all year: memory has become expensive, so phones are no longer getting more of it.
What Android 17 app memory limits actually do to your phone
The limits are a ceiling on how much memory a single app is allowed to hold. Cross it and Android does not simply let the app carry on. It first pushes the app’s memory pages into zRAM, a compressed section of RAM, which Google concedes adds CPU overhead and can result in noticeable UI jank and slowdowns. Keep climbing past the zRAM threshold and the system kills the app outright.
In practice that means two things you will notice without ever opening a developer tool. A heavy app — a game, a camera app, a social feed with a long scroll history — may stutter where it used to run smoothly. And an app you left in the background may be gone when you switch back to it, having lost whatever you had typed or scrolled to.
Google’s own framing in the Android 17 behaviour-changes documentation is that the limits exist to catch memory leaks and other outliers before they destabilise the whole system, on the theory that one badly behaved app should not drag the whole phone down. That is a real problem and a defensible fix.
Why this is happening now: RAM got expensive
The part worth sitting with is Google’s stated motivation, written by Blair Harmon, Director of Product Management for the Android Platform:
Across the ecosystem, new devices are maintaining or even decreasing their physical memory capacity in response to memory price increases, yet users continue to expect the same seamless, high-performance app experience.
Read plainly, that is Google acknowledging that phones are shipping with the same or less RAM than they used to because memory costs more — the same cost pressure Google itself blamed for the Pixel 11’s price increase and that Amazon cited when raising Echo, Fire TV and Kindle prices. The buyer is being asked to absorb that twice: once at the till, and again in the form of an operating system that is now stricter about what your apps are allowed to use.
The 4GB end of Google’s stated range is where this will bite hardest. Budget phones already juggle background apps aggressively; a formal, enforced ceiling on top of that is not a feature entry-level buyers asked for.
What you can and cannot do about it
Nothing, directly — there is no user-facing setting for this. The enforcement is at the OS level and the fix has to come from app developers trimming their memory use, which is exactly what Google’s post is prodding them to do. Google has given them the diagnostics to find it: an app killed this way reports an exit reason of REASON_OTHER with a description containing MemoryLimiter:AnonSwap, so developers can see the kills in the field rather than guessing.
Google has not named which manufacturers are adopting the limits or given a date for any of them beyond “over the coming year.” Until they do, Pixel owners on Android 17 are the only ones living with it today.
