The First Developer Preview of Android 16

Posted by Matthew McCullough – VP of Product Administration, Android Developer

Android 16 Developer Preview 1 is offered now to check together with your apps. That is the beginning of Android having extra frequent API releases as a part of our effort to drive quicker innovation in apps and units.

Two Android API releases in 2025

• This preview is for the subsequent main launch of Android with a deliberate launch in Q2 of 2025. This launch is just like all of our API releases previously, the place we are able to have deliberate habits adjustments which might be usually tied to a targetSdkVersion.
• We’re planning the key launch 1 / 4 earlier (Q2 somewhat than Q3 in prior years) to raised align with the schedule of system launches throughout our ecosystem, so extra units can get the key launch of Android sooner. With the key launch coming in Q2, you’ll have to do your annual compatibility testing a number of months sooner than in earlier years to ensure your apps are prepared.
• We plan to have one other launch in This fall of 2025 which additionally will embrace new developer APIs. The Q2 main launch would be the solely launch in 2025 to incorporate deliberate habits adjustments that might have an effect on apps.

Along with new developer APIs, the This fall minor launch will decide up characteristic updates, optimizations, and bug fixes; it is not going to embrace any app-impacting habits adjustments.

We’ll proceed to have quarterly Android releases. The Q1 and Q3 updates in-between the API releases will present incremental updates to assist guarantee steady high quality. We’re actively working with our system companions to convey the Q2 launch to as many units as attainable.

Utilizing new APIs with main and minor releases

Guarding a code block with a test for Android’s API degree is finished right now utilizing the SDK_INT fixed with VERSION_CODES. This may proceed to be supported for main Android releases.

if (SDK_INT >= VERSION_CODES.BAKLAVA) {
  // Use APIs launched in Android 16
}

The brand new SDK_INT_FULL fixed can be utilized for API checks towards each main and minor variations with the brand new VERSION_CODES_FULL enumeration.

if (SDK_INT_FULL >= VERSION_CODES_FULL.[MAJOR or MINOR RELEASE]) {
  // Use APIs launched in a serious or minor launch
}

You can even use the Construct.getMinorSdkVersion() technique to get simply the minor SDK model.

val minorSdkVersion = Construct.getMinorSdkVersion(VERSION_CODES_FULL.BAKLAVA)

These APIs haven’t but been finalized and are topic to vary, so please ship us suggestions when you have any issues.

Word that there’s no change to the goal API degree necessities and the related dates for apps in Google Play; our plans are for one annual requirement every year, and that will probably be tied to the key API degree.

Embedded photograph picker

The photograph picker offers a protected, built-in method for customers to grant your app entry to chose pictures and movies from each native and cloud storage, as a substitute of their total media library. Utilizing a mix of Modular System Parts via Google System Updates and Google Play providers, it is supported again to Android 4.4 (API degree 19). Integration requires only a few traces of code with the related Android Jetpack library.

The developer preview consists of new APIs that allow apps to embed the photograph picker into their view hierarchy. This enables it to really feel like a extra built-in a part of the app whereas nonetheless leveraging the method isolation that permits customers to pick out media with out the app needing overly-broad permissions. To maximise compatibility throughout platform variations and simplify your integration, you will wish to use the forthcoming Android Jetpack library for those who want to combine the embedded photograph picker.

Well being information

The developer preview of Well being Join accommodates an early model of APIs supporting well being information. This enables apps to learn and write medical information in FHIR format with express person consent. This API is at present in an early entry program. Signal as much as be a part of our early entry program.

Privateness Sandbox on Android

Android 16 incorporates the newest model of the Privateness Sandbox on Android, a part of our ongoing work to develop applied sciences the place customers know their privateness is protected. Our web site has extra concerning the Privateness Sandbox on Android developer beta program that can assist you get began. Take a look at the SDK Runtime which permits SDKs to run in a devoted runtime setting separate from the app they’re serving, offering stronger safeguards round person knowledge assortment and sharing.

prepare

Along with performing compatibility testing on the subsequent main launch, just be sure you’re compiling your apps towards the brand new SDK, and use the compatibility framework to allow targetSdkVersion-gated habits adjustments as they grow to be accessible for early testing.

App compatibility

The Android 16 Preview program runs from November 2024 till the ultimate public launch subsequent 12 months. At key improvement milestones, we’ll ship updates on your improvement and testing environments. Every replace consists of SDK instruments, system pictures, emulators, API reference, and API diffs. We’ll spotlight crucial APIs as they’re prepared to check within the preview program in blogs and on the Android 16 developer web site.

We’re concentrating on Late Q1 of 2025 for our Platform Stability milestone. At this milestone, we’ll ship closing SDK/NDK APIs and likewise closing inside APIs and app-facing system behaviors. We’re anticipating to succeed in Platform Stability in March 2025, and from that point you’ll have a number of months earlier than the official launch to do your closing testing. Go to our Android Builders web site for particulars on the discharge timeline.

Get began with Android 16

You may get began right now with Developer Preview 1 by flashing a system picture and updating the instruments. We’re searching for your suggestions so please report points and submit characteristic requests on the suggestions web page. The sooner we get your suggestions, the extra we are able to embrace within the closing launch.

For one of the best improvement expertise with Android 16, we suggest that you simply use the newest preview of the Android Studio Ladybug characteristic drop. When you’re arrange, listed below are among the issues you must do:

• Compile towards the brand new SDK, take a look at in CI environments, and report any points in our tracker on the suggestions web page.
• Take a look at your present app for compatibility, study whether or not your app is affected by adjustments in Android 16, and set up your app onto a tool or emulator working Android 16 and extensively take a look at it.

We’ll replace the preview system pictures and SDK repeatedly all through the Android 16 launch cycle. This preliminary preview launch is for builders solely and never supposed for each day or client use, so we’re making it accessible by guide obtain solely. When you’ve manually put in a preview construct, you’ll mechanically get future updates over-the-air for all later previews and Betas. Go to the Android developer web site for additional info on Android updates.

In the event you’ve already put in Beta 1 from the Android 15 QPR2 Beta program, you will be unable to maneuver to the Android 16 Developer Preview program with out wiping your system. Think about avoiding putting in future betas to transition to the subsequent developer preview construct with out a knowledge wipe.

As we attain our Beta releases, we’ll be inviting customers to attempt Android 16 as properly, and we’ll open up enrollment for Android 16 within the Android Beta program at the moment.

For full info, go to the Android 16 developer web site.