Android 17 final beta targets bloated apps: New memory limits can shut them down to keep phones fast

Google has released the fourth and final beta of Android 17, moving the platform into its stability phase ahead of a broader rollout expected around June.

The update is aimed squarely at performance and predictability, with new controls designed to rein in apps that consume excessive resources.

The biggest shift is stricter, device-specific RAM limits that allow Android to enforce hardware-level memory boundaries.

Paired with anomaly detection, the system can actively monitor apps and terminate those that exceed defined baselines, a change intended to reduce slowdowns and crashes caused by runaway memory use.

More control shifts to Android

Google says the goal is to make Android more deterministic, where the operating system dictates key resource limits rather than leaving them to developers.

For users, that could translate into smoother multitasking and fewer performance dips from bloated or poorly optimized apps.

For developers, the final beta is a signal that major behavior changes are largely locked in, making this an important test window. With the platform nearing release, app makers are expected to validate performance under the new memory rules and ensure stability across supported devices.

Tablets and foldables get stricter rules

Android 17 also tightens expectations for large-screen support by ending opt-out compatibility on tablets and foldables.

Apps will be required to handle resizability and orientation changes, pushing developers to better support different aspect ratios and screen sizes.

The change reflects Android’s ongoing push toward more consistent experiences on big screens, where apps that fail to adapt can feel outdated or awkward. Over time, this should reduce the number of phone-only layouts that waste space on tablets and foldables.

Security and future-proof cryptography

On security and privacy, Android 17 increases default restrictions, including blocking local network access by default and requiring permission for persistent connectivity.

The platform is also advancing Certificate Transparency support, part of a broader effort to make sensitive access more explicit and auditable.

Google is additionally preparing for longer-term threats by integrating NIST-standardized quantum-resistant digital signatures into hardware via the Android Keystore.

While it may not deliver an immediate benefit, the move is designed to help Android transition more smoothly as post-quantum security becomes a practical necessity.