Google has released the first beta of Android 17, marking the next major step in the evolution of the world’s most widely used mobile operating system.
The update, now available to enrolled Pixel devices and developers via the Android Emulator, signals more than just new features. It reflects a broader shift in how Google plans to deliver Android updates — faster, more continuous, and increasingly focused on large-screen experiences, performance efficiency, and tighter privacy controls.
Here’s a detailed look at what Android 17 brings.
A New Release Model: From Developer Preview to Canary
One of the biggest structural changes in Android 17 is not a feature users will see — but one developers will feel.
Google has replaced the traditional “Developer Preview” program with a continuous Canary channel. Instead of quarterly preview drops, features will now land as soon as they pass internal testing.
The move is designed to:
- Deliver APIs faster
- Improve beta stability through early testing
- Support OTA updates without manual flashing
- Integrate more easily with CI workflows
Platform Stability is targeted for March, after which final SDK and NDK APIs will be locked. A broader public release is expected later in 2026.
Android 17 Focuses on Large Screens
Android’s future clearly extends beyond phones.
With foldables, tablets, and desktop-style windowing environments gaining ground, Android 17 (API level 37) removes the ability for developers to restrict orientation and resizability on large-screen devices.
Apps targeting SDK 37 must now:
- Support both portrait and landscape layouts
- Adapt dynamically to window resizing
- Respect different aspect ratios
- Function properly on devices with a width ≥ 600dp
Manifest attributes like screenOrientation, resizeableActivity, and aspect ratio limits will be ignored on larger displays.
Games are exempt. Phones under 600dp remain unaffected.
The message is clear: Android apps must work everywhere.
Smarter Activity Handling
To reduce unnecessary interruptions — such as video playback restarting or input being dropped — Android 17 changes how configuration updates are handled.
Instead of automatically recreating activities for changes like:
- Keyboard appearance
- Touchscreen changes
- Navigation mode
- UI mode adjustments
The system will now deliver updates via onConfigurationChanged() by default.
If developers require full recreation, they must explicitly opt in using the new android:recreateOnConfigChanges attribute.
The result should be fewer user-facing disruptions.
Performance Improvements: Under the Hood
Android 17 introduces several deep system optimizations.
Lock-Free MessageQueue
Apps targeting SDK 37 will use a new lock-free implementation of android.os.MessageQueue, reducing frame drops and improving responsiveness.
However, apps relying on reflection into private fields may break.
Generational Garbage Collection
Android Runtime (ART) now includes generational garbage collection in its Concurrent Mark-Compact collector.
In practice, this means:
- More frequent small memory cleanups
- Fewer long pauses
- Lower overall CPU usage
Importantly, ART improvements will reach devices running Android 12 and above via Google Play System updates.
Static Final Fields Enforcement
In Android 17, “static final” fields become truly immutable. Reflection-based modification attempts will throw IllegalAccessException, and JNI attempts will crash the app.
This allows the runtime to optimize more aggressively.
Media and Camera: Professional-Grade Upgrades
Android 17 brings significant upgrades for camera and media developers.
Dynamic Camera Session Updates
A new method, updateOutputConfigurations(), allows developers to modify camera output surfaces without recreating the entire session.
This reduces memory overhead and eliminates glitches when switching between photo and video modes.
Logical Multi-Camera Metadata
Developers can now access metadata from all active physical cameras in a logical multi-camera device — useful during zoom transitions or sensor switching.
VVC (Versatile Video Coding) Support
Android 17 adds support for VVC, the next-generation video compression standard. Devices with compatible hardware will benefit from improved compression efficiency.
Constant Quality Video Mode
The new setVideoEncodingQuality() API enables constant quality (CQ) video recording, offering finer control beyond bitrate tuning.
Background Audio Restrictions
To prevent unintended playback, background audio APIs now fail if triggered outside a valid lifecycle state. Audio focus requests may return AUDIOFOCUS_REQUEST_FAILED.
Privacy and Security Tightened
Android 17 continues Google’s steady push toward stricter defaults.
Cleartext Traffic Deprecation
The android:usesCleartextTraffic The attribute is deprecated. Apps targeting Android 17 must use Network Security Configuration files for HTTP traffic control.
Cleartext will default to blocked without proper configuration.
HPKE Hybrid Cryptography
Android 17 introduces support for HPKE (Hybrid Public Key Encryption), enabling stronger secure communication models that combine public-key and symmetric encryption.
Connectivity and Telecom Enhancements
Android 17 also updates VoIP and proximity capabilities.
Enhanced VoIP Call History
Users gain more granular control over how VoIP apps integrate with system call logs. Caller avatars and participant URIs can now appear directly in the system dialer.
Wi-Fi Ranging and Proximity Detection
New APIs enable continuous ranging and secure peer discovery. Improvements include support for Wi-Fi 11az secure ranging with PMKID caching.
Developer Tools and Companion Devices
Companion device management has been streamlined.
Two new device profiles are introduced:
- Medical Devices – Simplified permission requests
- Fitness Trackers – Clearer role distinction and iconography
Association flows now allow Nearby permission prompts to be bundled into a single dialog, reducing friction.
Additionally, new ProfilingManager triggers help diagnose:
- Cold starts
- Out-of-memory events
- Excessive CPU usage kills
A Year of Incremental Releases
Android 17 will follow a quarterly update cadence.
- Q2 2026: Only planned app-breaking changes
- Q4 2026: Minor SDK update with new APIs
Google appears to be aiming for a more predictable and modular update cycle.
How to Get Android 17 Beta
Developers can:
- Enroll supported Pixel devices for OTA updates
- Use 64-bit system images in Android Studio
- Test apps targeting
targetSdkPreview = "CinnamonBun"
Google recommends compiling against the new SDK and thoroughly testing compatibility before Platform Stability in March.
The Bigger Picture
Android 17 is not a flashy redesign. There is no dramatic visual overhaul.
Instead, it reflects a maturing platform focused on:
- Adaptability across form factors
- Under-the-hood performance gains
- Stricter security defaults
- Professional-grade media capabilities
- A faster developer feedback loop
For users, most improvements will be subtle — fewer glitches, better multitasking, more reliable apps.
For developers, however, Android 17 represents a clear signal: the future of Android is flexible, secure, and built for every screen.
More updates are expected as the beta progresses toward final release later this year.