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

Right now we’re bringing you Android 16 beta 4, the final scheduled replace in our Android 16 beta program. Be certain that your app or recreation is prepared. It is also the final probability to offer us suggestions earlier than Android 16 is launched.

Android 16 Beta 4

That is our second platform stability launch; the developer APIs and all app-facing behaviors are remaining. Apps focusing on Android 16 could be made obtainable in Google Play. Beta 4 consists of our newest fixes and optimizations, providing you with the whole lot you’ll want to full your testing. Head over to our Android 16 abstract web page for an inventory of the options and conduct modifications we have been masking on this collection of weblog posts, or learn on for a number of the prime modifications of which try to be conscious.

Now obtainable on extra gadgets

The Android 16 Beta is now obtainable on handset, pill, and foldable type components from companions together with Honor, iQOO, Lenovo, OnePlus, OPPO, Realme, vivo, and Xiaomi. With extra Android 16 companions and gadget sorts, many extra customers can run your app on the Android 16 Beta.

Get your apps, libraries, instruments, and recreation engines prepared!

In case you develop an SDK, library, instrument, or recreation engine, it is much more necessary to organize any crucial updates now to forestall your downstream app and recreation builders from being blocked by compatibility points and permit them to focus on the most recent SDK options. Please let your builders know if updates to your SDK are wanted to completely assist Android 16.

Testing entails putting in your manufacturing app or a check app making use of your library or engine utilizing Google Play or different means onto a tool or emulator working Android 16 Beta 4. Work by all of your app’s flows and search for practical or UI points. Evaluate the conduct modifications to focus your testing. Every launch of Android comprises platform modifications that enhance privateness, safety, and total person expertise, and these modifications can have an effect on your apps. Listed here are a number of modifications to concentrate on that apply, even should you aren’t but focusing on Android 16:

• Broadcasts: Ordered broadcasts utilizing priorities solely work inside the identical course of. Use different IPC should you want cross-process ordering.
• ART: In case you use reflection, JNI, or every other means to entry Android internals, your app may break. That is by no means a finest observe. Check completely.
• 16KB Web page Measurement: In case your app is not 16KB-page-size prepared, you should use the new compatibility mode flag, however we advocate migrating to 16KB for finest efficiency.

Different modifications that will probably be impactful as soon as your app targets Android 16:

Get your app prepared for the long run:

• Native community safety: Think about testing your app with the upcoming Native Community Safety characteristic. It would give customers extra management over which apps can entry gadgets on their native community in a future Android main launch.

Keep in mind to completely train libraries and SDKs that your app is utilizing throughout your compatibility testing. You might must replace to present SDK variations or attain out to the developer for assist should you encounter any points.

When you’ve revealed the Android 16-compatible model of your app, you can begin the method to replace your app’s targetSdkVersion. Evaluate the conduct modifications that apply when your app targets Android 16 and use the compatibility framework to assist shortly detect points.

Two Android API releases in 2025

This Beta is for the subsequent main launch of Android with a deliberate launch in Q2 of 2025 and we plan to have one other launch with new developer APIs in This fall. This Q2 main launch would be the solely launch in 2025 that features conduct modifications that would have an effect on apps. The This fall minor launch will decide up characteristic updates, optimizations, and bug fixes; like our non-SDK quarterly releases, it is not going to embody any intentional app-breaking conduct modifications.

We’ll proceed to have quarterly Android releases. The Q1 and Q3 updates present incremental updates to make sure steady high quality. We’re placing extra vitality into working with our gadget companions to convey the Q2 launch to as many gadgets as potential.

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 annually, tied to the main API degree.

Get began with Android 16

You may enroll any supported Pixel gadget to get this and future Android Beta updates over-the-air. In case you don’t have a Pixel gadget, you’ll be able to use the 64-bit system photos with the Android Emulator in Android Studio. In case you are at the moment on Android 16 Beta 3 or are already within the Android Beta program, you can be provided an over-the-air replace to Beta 4.

Whereas the API and behaviors are remaining and we’re very near launch, we would nonetheless such as you to report points on the suggestions web page. The sooner we get your suggestions, the higher probability we’ll be capable to tackle it on this or a future launch.

For the most effective improvement expertise with Android 16, we advocate that you simply use the most recent Canary construct of Android Studio Narwhal. When you’re arrange, listed below are a number of the issues it is best to do:

• Compile in opposition to the brand new SDK, check in CI environments, and report any points in our tracker on the suggestions web page.

We’ll replace the beta system photos and SDK usually all through the Android 16 launch cycle. When you’ve put in a beta construct, you’ll routinely get future updates over-the-air for all later previews and Betas.

For full data on Android 16 please go to the Android 16 developer web site.