Google is preparing to tighten memory-usage requirements for Android apps and games, warning developers that applications consuming excessive amounts of RAM could face slower performance, termination and eventually reduced visibility or publishing capabilities on Google Play. The new requirements are being introduced as Android faces broader memory constraints across devices, with Google saying manufacturers are expected to apply per-app memory limits across phones with configurations ranging from 4GB to more than 16GB of RAM.
The changes represent a significant shift in how Google evaluates Android app quality. Starting in February 2027, apps and games will have to meet new thresholds covering dynamic memory usage, bitmap memory and DEX code optimization. Google has already begun adding diagnostic tools to Play Console and Android vitals so developers can identify memory-heavy applications before enforcement begins. Apps that fail to meet the requirements could see their Google Play visibility and publishing capabilities affected.
Google Tightens Android App Memory Rules
Google’s new policy is designed to reduce the amount of device memory consumed by poorly optimized applications.
The company says the mobile industry is facing significant hardware supply constraints that are changing device memory availability, making efficient software increasingly important.
Android 17 has already introduced per-app memory limits based on a device’s total RAM.
These limits are designed to prevent individual applications from consuming so much memory that the entire device becomes unstable.
Android Memory Policy At A Glance
| Particular | Details |
|---|---|
| Company | |
| Platform | Android / Google Play |
| New memory rules | Announced August 2026 |
| Android version introducing limits | Android 17 |
| Enforcement begins | February 2027 |
| Main metrics | Anonymous RSS + Swap, bitmap memory |
| Code requirement | Minimum 25% optimization/shrinking/obfuscation where applicable |
| Affected form factors | Phones and tablets for memory metrics |
| Possible consequence | Reduced Play visibility/publishing capabilities |
Google describes the requirements as part of a broader effort to maintain app quality as available device memory becomes more constrained.
Android 17 Introduces Per-App Memory Limits
Android 17 introduced app memory limits based on total device RAM.
The goal is to catch memory leaks and other outlier behavior before it causes wider system instability, such as interface stuttering, increased battery consumption or Android terminating applications.
Google says most app sessions are expected to experience minimal impact, but developers are being encouraged to establish memory baselines and test applications under the new constraints.
How Android’s Memory Limiter Works
Android device
│
▼
Available system memory
│
▼
Per-app memory limit
│
▼
Application usage monitored
│
├── Within limit
│ ▼
│ Normal operation
│
└── Exceeds limit
▼
Memory intervention
│
├── Slowdown
└── Possible termination
Developers can use Android debugging tools to test applications against these limits.
Google Will Evaluate Memory Usage Through Android Vitals
Google Play is adding memory consumption to its app-quality monitoring framework.
The new metrics include Anonymous Resident Set Size (Anon RSS) plus Swap and bitmap memory usage.
Google uses aggregated and anonymized data from opted-in devices to evaluate app performance.
The company uses the 90th percentile of collected measurements to determine whether an app exceeds certain bad-behavior thresholds.
Key Memory Metrics
| Metric | What It Measures |
|---|---|
| Anonymous RSS | Memory directly allocated by the application |
| Swap | Memory compressed or paged into zRAM |
| Anon RSS + Swap | Dynamic memory footprint |
| Bitmap memory | Memory used by image bitmaps |
| P90 | 90th-percentile performance measurement |
For example, a P90 memory value means 90% of sampled observations were below that level, while 10% were above it.
Android Memory Limits Depend On Device RAM
Google is not imposing one universal memory ceiling on every Android device.
Instead, the thresholds vary according to the device’s RAM tier.
This is intended to recognize the difference between a 4GB smartphone and a 16GB handset.
Android App Memory Thresholds
| Device RAM Tier | Foreground | User-Perceived Services | Background |
|---|---|---|---|
| 4GB | 2.00GB | 1.00GB | 1.00GB |
| 6GB | 2.25GB | 1.25GB | 1.25GB |
| 8GB | 2.25GB | 1.50GB | 1.50GB |
| 12GB | 3.25GB | 1.75GB | 1.75GB |
| 16GB | 4.25GB | 2.00GB | 2.00GB |
| 16GB+ | No threshold listed | No threshold listed | No threshold listed |
These are Google’s 90th-percentile bad-behavior thresholds for apps, beginning in February 2027. Google defines the RAM tiers using total memory ranges rather than simply relying on a phone’s advertised RAM specification.
Games Get Higher Memory Allowances
Google’s thresholds are different for games because modern mobile games can require substantially more memory than ordinary applications.
Android Game Memory Thresholds
| Device RAM Tier | Foreground | User-Perceived Services | Background |
|---|---|---|---|
| 4GB | 2.25GB | 2.00GB | 2.00GB |
| 6GB | 2.75GB | 2.50GB | 2.50GB |
| 8GB | 3.50GB | 2.75GB | 2.75GB |
| 12GB | 4.00GB | 3.20GB | 3.20GB |
| 16GB | 5.00GB | 3.50GB | 3.50GB |
| 16GB+ | No threshold listed | No threshold listed | No threshold listed |
The higher limits reflect the larger memory requirements of graphics-intensive games.
Bitmap Memory Is Also Being Restricted
Google is separately targeting excessive use of bitmap memory.
Bitmaps are commonly used to display images, but keeping large numbers of them in memory when they are no longer visible can unnecessarily consume RAM.
Google says developers should avoid holding onto bitmaps for extended periods when an app is in the background or cached state.
Bitmap Memory Thresholds
| App State | Threshold |
|---|---|
| Foreground | No listed bad-behavior threshold |
| User-perceived service | >200MB |
| Background | >200MB |
| Cached | >400MB |
The thresholds apply to both apps and games under Google’s current requirements.
Google Also Wants Developers To Optimize Code
Memory is not the only area covered by the new policy.
Google is introducing a DEX code optimization requirement designed to reduce application size and improve runtime performance.
Beginning in February 2027, apps and games with sufficiently large DEX code must achieve at least 25% optimization, shrinking and obfuscation coverage using R8 or another appropriate tool.
DEX Optimization Requirement
| Category | Requirement |
|---|---|
| Standard apps | 25% minimum |
| Games | 25% minimum |
| Apps covered by size threshold | >10MB DEX |
| Games covered by size threshold | >50MB DEX |
| Enforcement | February 2027 |
Google says optimized DEX code can help applications start faster, use less memory, reduce ANRs and improve rendering and runtime performance.
Why Is Google Doing This Now?
The policy arrives amid a broader memory shortage affecting the technology industry.
AI data centers require enormous quantities of high-performance memory, increasing demand for DRAM and other components.
At the same time, smartphone manufacturers are dealing with higher memory costs and, in some cases, reducing the amount of RAM included in devices.
Google’s response is to make software more efficient rather than allowing increasingly memory-hungry applications to compensate for hardware limitations.
Memory Supply Pressure
AI data centers
│
▼
Higher memory demand
│
▼
Tighter memory supply
│
▼
Higher RAM costs
│
▼
Some phones use less RAM
│
▼
Greater pressure on Android apps
│
▼
Google tightens memory requirements
The policy therefore connects software development with a much larger hardware-supply issue.
Low-RAM Android Phones Could Benefit
One of the biggest potential beneficiaries of the policy could be users of lower-memory Android phones.
When a device has limited RAM, a single poorly optimized application can consume a disproportionate amount of available memory.
That can force Android to terminate background applications or cause the interface to become less responsive.
What Excessive Memory Usage Can Cause
| Problem | User Impact |
|---|---|
| Memory pressure | Slower device |
| Background app termination | Apps reload frequently |
| Excessive swapping | Reduced responsiveness |
| Memory leaks | Increasing RAM consumption |
| Bitmap bloat | Higher memory usage |
| Large code footprint | Longer startup / higher resource use |
| Out-of-memory conditions | App crashes or termination |
Google says its memory limits are intended to prevent this type of system-wide instability.
Google Will Warn Developers Before Enforcement
Developers are not being asked to discover memory problems only after their apps are penalized.
Google has already begun rolling out new diagnostic capabilities in Play Console and Android vitals.
These tools can show dynamic memory and bitmap usage across different device RAM categories.
New Developer Tools
| Tool | Purpose |
|---|---|
| Memory metrics in Android vitals | Monitor memory consumption |
| Memory percentile data | Identify high-usage devices |
| Out-of-memory crash filter | Find memory-related terminations |
| DEX optimization insights | Check code efficiency |
| Performance alerts | Warn when thresholds are exceeded |
| Future Memory Limiter insights | Diagnose memory-limit behavior |
Google says additional diagnostic capabilities will arrive later in 2026.
Apps Could Face Google Play Visibility Penalties
The most significant part of the announcement is that this is not simply technical advice.
Starting in February 2027, apps and games that fail to meet the new thresholds may face reduced visibility and publishing capabilities on Google Play.
Google has not yet provided all details about how these publishing consequences will work.
Potential Enforcement Path
Excessive memory usage
│
▼
Android vitals warning
│
▼
Developer optimization
│
▼
Still exceeds threshold
│
▼
February 2027 enforcement
│
▼
Potentially reduced
Play Store visibility
or publishing capabilities
This gives developers several months to make changes.
Memory Rules Apply Beyond Android 17
An important detail is that the Google Play memory requirements are not limited to devices running Android 17.
Google’s Play Console documentation says it will evaluate memory data for supported app versions where data is available, including Android 13 and later for the memory metrics.
This means developers cannot simply assume that older Android devices are outside the new Play Store quality framework.
Android Version Scope
| Requirement | Scope |
|---|---|
| Android 17 memory limiter | Android 17+ devices |
| Google Play memory metrics | Android 13+ where data is available |
| Memory usage requirement | Mobile/tablet |
| DEX optimization | All applicable form factors |
| Enforcement | February 2027 |
The distinction between the Android operating-system limiter and Google Play’s quality requirements is important.
Developers Have Several Ways To Reduce Memory Use
Google’s recommendations include releasing resources when they are no longer needed and avoiding memory leaks.
For example, applications can use lifecycle-aware components, respond appropriately to onTrimMemory(), profile allocations and analyze heap dumps.
For image-heavy applications, developers can downsample images to match their actual display dimensions and use memory-conscious image-loading libraries.
Memory Optimization Strategies
| Problem | Recommended Approach |
|---|---|
| Memory leaks | Use lifecycle-aware components |
| Temporary allocations | Release memory when no longer needed |
| Background memory | Respond to onTrimMemory() |
| Large images | Downsample to display size |
| Bitmap bloat | Release unused bitmaps |
| Large DEX footprint | Use R8/shrinking |
| Unknown memory spikes | Use profiling and heap dumps |
| Long background tasks | Minimize unnecessary execution |
The objective is not simply to reduce memory consumption at all costs but to prevent inefficient use that can degrade the broader device experience.
Developers Will Need To Monitor Multiple RAM Tiers
An application that performs well on a 16GB smartphone may still cause problems on a 4GB handset.
This is why Google has created different thresholds based on device RAM.
Developers therefore need to examine performance across a range of hardware rather than optimizing only for premium devices.
4GB device ─────┐
6GB device ─────┤
8GB device ─────┤
12GB device ────┤──► App memory analysis
16GB device ────┤
16GB+ device ───┘
This could particularly affect applications that have historically assumed that users have increasingly large amounts of RAM.
The Policy Could Change Android App Design
Google’s requirements could encourage developers to reconsider how applications manage images, background processes and temporary data.
Apps that currently keep large amounts of information in memory for convenience may need to become more dynamic.
Developers may also reduce unnecessary libraries and code.
Areas Likely To Receive More Attention
| Area | Expected Focus |
|---|---|
| Images | Smaller and more efficiently managed bitmaps |
| Background tasks | Reduced persistent activity |
| Code | More aggressive shrinking |
| Caching | Smarter cache management |
| Memory leaks | Earlier detection |
| App architecture | Lifecycle-aware resource handling |
| Testing | More RAM-tier coverage |
The changes could ultimately produce lighter applications, particularly on lower-end hardware.
Google Is Also Introducing A Separate Sign-In Requirement
The memory policy is one of two new Google Play quality requirements announced together.
The second concerns Zero-Tap Sign-In during device migration.
Beginning in April 2027, apps on Google Play will need to support the restoration of users’ sign-in state when they move to a new Android device, using the Android Restore Credentials API, in order to maintain full publishing capabilities and optimal visibility.
2027 Google Play Requirements
| Requirement | Enforcement Date |
|---|---|
| Memory usage thresholds | February 2027 |
| Bitmap memory thresholds | February 2027 |
| DEX optimization | February 2027 |
| Zero-Tap Sign-In | April 2027 |
Games currently have an exemption from the Zero-Tap Sign-In requirement, although Google says dedicated guidance for gaming authentication use cases is expected in 2027.
Android’s Memory Crisis Is Becoming A Software Issue
The memory shortage was initially most visible through hardware.
Consumers have seen changes in device specifications, component prices and availability.
Google’s latest move shows that the problem is now affecting software development as well.
Instead of assuming that every future phone will have more memory, developers are being asked to build applications that work efficiently within tighter constraints.
Hardware To Software Shift
Hardware shortage
│
▼
Less available / more expensive RAM
│
▼
Smartphone memory constraints
│
▼
Android memory limits
│
▼
Google Play thresholds
│
▼
Developers optimize apps
The result could be a broader industry shift toward memory-efficient software.
Users Should Not Expect Every Large App To Be Removed
Google’s announcement does not mean that any application using a large amount of RAM will automatically be removed from the Play Store.
The thresholds are based on percentile measurements, device RAM tiers, app state and application category.
Google describes exceeding the thresholds as a strong indicator of degraded user experience and potential Android termination, while Play Store consequences can include reduced visibility and publishing capabilities.
The policy is therefore more nuanced than a simple fixed “RAM limit” for every Android application.
The Bigger Picture
Google’s new Android memory requirements mark a major change in how mobile software efficiency will be enforced. From February 2027, apps and games on Google Play will have to meet thresholds for dynamic memory usage, bitmap memory and DEX code optimization. Applications that repeatedly exceed the relevant bad-behavior thresholds could face reduced visibility and publishing capabilities on Google Play, while Android itself can slow or terminate applications that exceed device-specific memory limits.
The timing is closely connected to the broader memory crunch affecting the technology industry. AI data centers are consuming huge quantities of memory, putting pressure on supply and costs while some smartphone manufacturers are reducing RAM configurations. Google’s approach is therefore to make Android software more efficient across devices ranging from roughly 4GB to 16GB-plus memory configurations, potentially helping lower-end phones remain responsive even when hardware resources are constrained.
Looking Ahead
Developers now have several months to prepare before the February 2027 enforcement deadline. Google has already introduced memory metrics, out-of-memory crash filters, DEX optimization insights and performance alerts in Play Console, while additional Memory Limiter diagnostics are expected later this year. Developers that proactively reduce memory leaks, optimize images, shrink unnecessary code and limit background activity should be better positioned to meet the new requirements.
For Android users, the policy could ultimately produce lighter and more efficient applications, particularly on phones with limited RAM. The broader significance is that the industry’s AI-driven memory shortage is beginning to influence software design as well as hardware specifications. If memory remains expensive or constrained, Google’s approach could encourage other platforms and developers to prioritize resource efficiency rather than assuming that every generation of smartphones will simply provide more memory.
Get the day’s top stories in your inbox
One concise email. No spam, unsubscribe anytime.
