Google launches Android 16 Developer Preview for Pixel

With Android 16 set to launch in the second quarter of 2025, Google is starting the Developer Preview for Pixel devices today.

For the past five releases, Developer Previews have started in February. Android 16 DP1 coming three months earlier reflects how the public launch is moving from Q3 to Q2 of 2025. Officially, this is to “better align with the schedule of device launches across our ecosystem, so more devices can get the major release of Android sooner.” 

The features being highlighted by Google today (before we get DP1 installed on devices) are for developers. New APIs for the system photo picker will allow apps to provide a more embedded — in the view hierarchy — experience and interface.

This allows it to feel like a more integrated part of the app while still leveraging the process isolation that allows users to select media without the app needing overly-broad permissions.

Health Connect will let apps “read and write medical records in FHIR format with explicit user consent” (early access program). Similarly, this release has the latest version of Privacy Sandbox for Android.

There will be six major releases before the final release in Q2 of 2025. A second Developer Preview is coming next month, while Beta releases start in January. At that time, the Android 16 Beta Program will go live, with installs today only available via flashing or sideloading.

Google is targeting Platform Stability (with final SDK/NDK APIs, internal APIs, and app-facing system behaviors) in March 2025, or Beta 3. 

At launch, Android 16 Developer Preview system images are available for the Pixel 6, Pixel 6 Pro, Pixel 6a, Pixel 7, Pixel 7 Pro, Pixel 7a, Pixel Tablet, Pixel Fold, Pixel 8, Pixel 8 Pro, Pixel 8a, Pixel 9, Pixel 9 Pro, Pixel 9 Pro XL, and Pixel Pro Fold, as well as the Android Emulator.

If you’re running Android 15 QPR2 Beta 1, “you will not be able to move to the Android 16 Developer Preview program without wiping your device.”

Consider avoiding installing future betas to transition to the next developer preview build without a data wipe.