Google Locks Android 17 APIs as General Availability Approaches

With Beta 3 marking Platform Stability and a June release window in view, Google's latest mobile OS is entering its final stretch before landing on Pixel devices worldwide.

Google has confirmed that Android 17 reached Platform Stability with the release of Beta 3, signaling that the operating system's API surface is now locked and the platform is entering its final phase before a public release. The milestone marks a critical checkpoint for app developers, SDK maintainers, and OEM hardware partners who must complete compatibility testing and publish updated packages to the Google Play Store ahead of the stable launch.

The development follows a substantially altered release cadence compared to prior Android versions. For the first time in several years, Google bypassed traditional Developer Preview builds entirely, routing early engineering work through a new Canary channel that allowed continuous API and feature testing throughout late 2025. The first public-facing Beta arrived on February 14, 2026, with Beta 2 following on February 27 and Platform Stability achieved with Beta 3 on March 28.

A Redesigned Release Pipeline

Google's decision to retire standalone Developer Previews in favor of the Canary channel reflects a broader push toward faster, more continuous iteration. Under the old model, developers had to wait for discrete preview drops before they could assess compatibility with new APIs. The Canary approach effectively compressed that window, giving the ecosystem more time to adapt before the first public beta even shipped.

Internally, Android 17 carries the codename Cinnamon Bun, continuing Google's long-running tradition of assigning dessert names to Android releases. The version is expected to ship as API level 37 and follows Android 16, which Google codenamed Baklava when it launched in June 2025.

What Platform Stability Means for Developers

Platform Stability is not a feature freeze — it is an API freeze. Google has stated that the final APIs are now locked, and the company is urging SDK authors, library maintainers, and game engine developers to release their updates immediately so that downstream developers are not blocked when targeting the latest SDK features. Apps not yet updated risk compatibility issues once the stable release reaches consumer devices.

> "If you develop an SDK, library, tool, or game engine, it is critical to release your updates now so downstream developers are not blocked from targeting the latest SDK features."

>

> — Android Developers, Beta 3 Release Notes

Several notable APIs were introduced across the beta cycle. Beta 2 brought a new Handoff API enabling developers to specify application state that can be resumed on a second Android device, a feature Google officially announced as part of its cross-device continuity push. The same release added an EyeDropper API allowing apps to capture pixel colors from anywhere on the display without requiring screen capture permissions, and a Contacts Picker providing session-based access to specific contact fields rather than demanding full READ_CONTACTS permissions.

Beta 3 introduced Photo Picker Customization, allowing developers to modify the grid view aspect ratio of the system photo picker using the PhotoPickerUiCustomizationParams API. It also added support for RAW14 image capture, enabling professional camera applications to record 14-bit per pixel RAW images from compatible sensors for maximum color depth and detail.

Key Features Heading Into General Availability

Beyond the developer-facing API changes, Android 17 carries a range of user-facing improvements that have accumulated across the beta cycle.

Local Network Access Permission. Android 17 introduces the ACCESS_LOCAL_NETWORK permission, grouped under NEARBY_DEVICES, to protect LAN communication. Apps that communicate over local networks will need to declare this permission explicitly.

NPU Declaration Requirement. Apps targeting Android 17 that wish to access the Neural Processing Unit directly must declare the FEATURE_NEURAL_PROCESSING_UNIT hardware feature. The change is part of Google's broader effort to formalize hardware feature access.

SMS OTP Protection. To reduce the risk of one-time password hijacking, Android 17 delays programmatic access to OTP messages by three hours for most applications. Google is directing developers to migrate toward the SMS Retriever or SMS User Consent APIs as more secure alternatives.

Vulkan Graphics Transition. Building on a policy announced in March 2025, Android 17 requires new devices to use ANGLE for most applications, effectively shifting from an allowlist model to a denylist model. Google has designated Vulkan as the official graphics API for Android, with the goal of establishing it as the hardware abstraction layer for all GPU operations across the platform.

ICU 78 and Unicode 17. Updated internationalization libraries arrive with this release, expanding support for the latest Unicode standard.

The Road to General Availability

Google I/O 2026, scheduled for May 19, is expected to serve as the formal public stage for Android 17, where the company will likely detail final feature additions and confirm the stable release window. Based on Google's recent release patterns, the stable build is anticipated to ship in June 2026, with Google Pixel devices receiving the update first.

Pixel phones from the Pixel 6 through the Pixel 10 series are confirmed to support Android 17. Manufacturers including Samsung, OnePlus, and Xiaomi are expected to follow with their own customized implementations in the months after the stable Pixel release, with most flagship devices from 2025 and 2026 likely to receive the update by October 2026.

The accelerated beta timeline this cycle, combined with an earlier-than-usual Platform Stability declaration, suggests Google is on track for a June general availability window without slippage. For developers who have not yet begun compatibility testing, the window is narrow. With the API surface locked and the final release weeks away, the time to act is now.

Android 17 Beta 3 release notes are available at developer.android.com. Pixel devices running the Android Beta Program can enroll to receive pre-release builds ahead of the stable launch.