Google Play to Enforce Android 17 Per-App Memory Limits Starting February 2027

Google will begin enforcing Android 17's per-app memory limits through Google Play in February 2027, with apps exceeding device-specific memory thresholds facing reduced visibility, throttling, and outright process termination. The enforcement timeline was detailed in a memo published in August 2026 and first reported by TechCrunch on August 27 (The Verge).

Android 17 introduced per-app memory limits based on a device's total RAM, creating what Google describes as a more stable and deterministic execution environment (Android Developers). The system enforces these limits by abruptly terminating processes that exceed them. Pixel devices were the first to ship with the feature active (The Verge).

Google's August memo, titled "Preparing your app for broader memory limits," states that over the coming year an increasing number of manufacturers will enforce per-app memory limits across device RAM configurations ranging from 4GB to 16GB+ (Android Developers Blog). Apps that breach the limits will be slowed down and may be terminated. The Play Store layer adds commercial consequences: apps and games that do not meet the memory thresholds may see reduced app visibility and restricted publishing capabilities on Google Play, with Google promising additional details later in 2026.

The enforcement operates at two levels. The OS-level mechanism, built into Android 17 itself, handles the runtime behavior: throttling and killing processes that exceed per-app ceilings derived from total device RAM. The Play Store enforcement, starting in February 2027, adds a distribution and discoverability penalty on top of the OS behavior. Developers face a window of roughly five months between the August 2026 memo and enforcement to audit and optimize their memory footprints.

This arrives alongside Google Play's existing target API level deadline of August 31, 2026, part of its annual policy update announced July 15 (Google Play Help). Developers who have not yet targeted the current API level face separate enforcement action on that track. The two policies are distinct but converging: the target API requirement pushes apps toward the latest Android version, and the memory limits are a behavioral change within that version.

The broader context here is one of finite hardware resources meeting expanding software demands. Google's move to police memory-hungry Android apps is described as a direct response to what The Verge characterizes as a RAM shortage crisis (The Verge). The verified sources do not enumerate the specific supply-chain or silicon-level factors behind that characterization, but the policy signal is unambiguous: Google is using both the operating system and the distribution layer to constrain per-app memory consumption, rather than relying on device manufacturers to ship more RAM.

Android 17 has progressed through its fourth beta release as of the developer documentation (Android Developers), meaning the per-app memory limits are already in the hands of developers testing against the preview builds. Google's developer blog posts, including "Prioritizing Memory Efficiency: Essential Steps for Android 17" (Android Developers) and the August preparation memo, urge developers to profile memory usage now rather than waiting for enforcement to begin.

For developers, the practical steps are straightforward: profile app memory consumption across the 4GB-to-16GB+ device range, identify processes that trigger the per-app ceiling, and reduce footprint before February 2027. Games are likely to be the most affected category, given their typically large working sets. The penalty for non-compliance is not merely technical (process termination at runtime) but commercial (reduced Play Store visibility), which raises the stakes considerably for studios whose acquisition depends on discoverability.

Google has not yet published the specific memory thresholds per RAM tier, nor the exact Play Store visibility criteria. Both are promised for later in 2026. In the interim, the Android 17 developer documentation provides the behavioral details developers need to begin profiling against the system-level limits, even without knowing the precise Play Store enforcement parameters.

What this enables, ultimately, is a more predictable Android ecosystem for low-RAM devices, where a single memory-hungry app can no longer degrade system-wide performance or battery life for the user. The trade-off is a new optimization burden on developers, particularly those building resource-intensive applications. Five months is a workable runway for teams with mature profiling workflows. For others, the February 2027 deadline is close enough to warrant immediate attention.