Skip to content

Google Play Will Enforce New Android App Memory Limits

Google Play will begin enforcing Android app memory and code-optimization thresholds in February 2027. Here is what developers need to measure, the limits by RAM tier, and what non-compliance could mean.

Google Play Will Enforce New Android App Memory Limits

On this page

Google is giving Android app developers a new deadline to deal with memory-hungry apps: starting in February 2027, Google Play will enforce new quality thresholds for memory usage and code optimization. The change affects mobile apps and games across Android, and it could influence which apps remain highly visible in the Play Store if they consistently use too much memory.

Google is turning memory use into a Play Store quality metric

The new policy is part of Google's broader effort to improve Android app quality. Instead of treating memory consumption as something developers only need to consider when an app crashes or becomes slow, Google Play will measure it as one of its core quality signals. The measurements include Anonymous Resident Set Size plus Swap, which represents memory associated with an app that is actually occupying physical memory or compressed storage, and bitmap memory used for images.

Google says these measurements will be evaluated using the previous 28 days of data. That matters because developers will not be judged solely by an occasional memory spike. An app that repeatedly consumes excessive memory across real-world devices could cross the threshold even if it appears normal during a short developer test.

The limits change depending on how much RAM a phone has

Google is not applying one fixed memory limit to every Android phone. The thresholds vary according to the device's physical RAM because an app that is reasonable on a high-memory phone can be much more disruptive on a low-memory device.

For example, Google's published threshold for an app running in the foreground is 2 GB at the 4 GB RAM tier and 2.25 GB at both the 6 GB and 8 GB tiers. At the 12 GB tier, the foreground threshold rises to 3.25 GB, while the 16 GB tier has a 4.25 GB threshold. Google also defines separate limits for apps running user-perceived services or in the background.

These figures are not recommendations for how much RAM an app should normally consume. They are bad-behavior thresholds used by Google Play to identify apps whose memory footprint is likely to create a poor experience. The distinction is important: an app does not suddenly become unusable because it reaches one of these numbers once.

Why Google is measuring memory across different phones

Android has to manage applications across an unusually wide range of hardware. A budget phone may have 4 GB of RAM, while a premium device can have several times that amount. When an application consumes too much memory, Android may have to terminate background processes to make room for the application the user is actively using.

That can create a problem users notice without knowing the technical reason. They switch from a game to a messaging app and return to find the game restarting. They leave a browser tab for a few minutes and discover that it has reloaded. The operating system is making a memory-management decision, but excessive application memory usage can make those decisions happen more often.

Google's approach therefore focuses on how an app behaves across different RAM tiers rather than assuming that a single memory target works everywhere. The policy applies to mobile phones and tablets, and Google's documentation says the memory measurements cover Android 13 and newer where sufficient data is available.

Games face the same pressure, with different thresholds

Games are included in the new requirements, but Google evaluates them separately from ordinary apps. That distinction makes sense because modern games can legitimately require large amounts of memory for textures, maps, models and other assets.

The goal is not to make every game small. Instead, Google wants developers to keep memory consumption within levels that are reasonable for the hardware on which the game is running. Developers therefore need to look beyond the amount of RAM advertised on a flagship phone and test how the same game behaves on lower-memory devices.

For studios, this can turn memory profiling into a release requirement rather than an optimization task left until the end of development. A game that performs well on a developer's high-end test phone may still have problems on a lower RAM tier, and the new Play metrics are designed to expose that difference.

The policy also targets inefficient compiled code

Memory is only one part of Google's new quality requirements. Google is also introducing thresholds for DEX code optimization. DEX, short for Dalvik Executable, is the format Android uses for compiled application bytecode.

The practical concern is that inefficient application code can increase the amount of work and resources required by the device. Google plans to evaluate code optimization alongside memory behavior, making the policy broader than simply checking how much RAM an application consumes.

This means developers should not treat the new requirements as a request to remove a few large images or reduce a cache. The underlying application architecture, dependency footprint, generated code and runtime behavior can all contribute to the final resource profile.

What happens to apps that miss the thresholds

Google is not saying that an app will immediately disappear from Google Play because it exceeds a memory threshold. Instead, apps and games that do not meet the requirements may face reduced visibility and publishing capabilities once enforcement begins.

That distinction is significant for developers. Google Play visibility affects how easily users discover an application, so a quality problem can eventually become a distribution problem. Developers therefore have a reason to address memory and code efficiency before enforcement rather than waiting for a warning after the policy takes effect.

Google has also described these metrics as indicators of degraded user experiences and on-device application termination. In other words, the policy is connected to a real performance problem rather than being an arbitrary limit imposed solely for compliance.

Developers have until 2027, but the work starts now

Enforcement begins in February 2027, giving developers several months to measure their applications and make changes. Google says additional diagnostic tools are expected later in 2026, including deeper information about how long applications spend in different states and additional insight into Android's memory-limiting behavior.

Developers should not wait for those tools before investigating. The first step is to inspect Android vitals and identify whether memory usage is concentrated in particular device RAM tiers or application states. Large bitmaps, unnecessarily retained objects, aggressive caching, memory leaks and heavyweight third-party libraries are all areas worth investigating when an app consistently approaches its limits.

The important metric is not simply the amount of RAM a developer sees in a local test. Google's evaluation uses real-world data and looks at the 90th percentile, meaning developers need to consider the behavior of the higher-memory-consuming portion of their users rather than relying on an average that can hide problematic devices.

This is also a warning about Android's changing hardware assumptions

The timing of the policy is notable because smartphone memory requirements are moving in two directions at once. Applications are becoming more demanding as artificial intelligence features, richer graphics and more capable local processing become common, while device manufacturers still have to manage component costs and product segmentation.

Google's response is to put more responsibility on software developers to use the available memory efficiently. That does not mean Android phones are suddenly running out of RAM, nor does it mean every application must drastically reduce its memory footprint. It means Google is increasingly treating inefficient resource usage as an ecosystem-level problem rather than something individual developers can ignore.

For users, the best outcome should be less aggressive app termination and more consistent multitasking, particularly on phones with modest RAM. For developers, the trade-off is additional testing, profiling and optimization work across multiple hardware tiers.

What Android developers should check before February

The practical deadline is still months away, but the safest approach is to treat the new requirements as part of the current development roadmap. Developers should review memory usage in Android vitals, examine bitmap allocations, investigate crashes and process termination associated with memory pressure, and test their applications on multiple RAM tiers.

Teams should also audit dependencies and generated code rather than assuming the problem is limited to the user interface. An application can have a visually simple interface and still maintain a large memory footprint because of libraries, caches, background work or inefficient data handling.

There is another reason to act early: memory optimization can expose bugs that are difficult to fix immediately before a release. Finding a leak or excessive allocation pattern months before enforcement gives a development team time to reproduce it, change the architecture where necessary and verify that the fix works across different devices.

Google's new policy does not make RAM usage the only measure of a good Android app. Stability, battery behavior and other Android vitals remain important. But from February 2027, memory efficiency and code optimization will have a much more direct relationship with a developer's ability to maintain strong visibility on Google Play. The developers who start measuring those numbers now will have considerably more room to fix problems before they become a distribution issue.

Copy this post

0 Comments

No comments yet. Be the first to share your thoughts.

Join the conversation

Log in or create a free account to leave a comment. You can edit or delete your own comments any time.