\n
![](\"https:\/\/blogger.googleusercontent.com\/img\/b\/R29vZ2xl\/AVvXsEjc6KbFCPUa_RB6bL1i4NhyphenhyphencptybHQM-joo2Bj19ZMT8wtRnHHHQPMcWnudH1X5rh5i7JJt81hPBw6WSB5joOyCEswbtfONT8qG_CtHZelak8VFk2sUvzkxeVCt6Tc3MZUUFsSdrnGMr19cTLzEFtaA7zSGVdqH3iXr6rF-qL2Ll2iQ8cWZUzqvNjHXPeU\/s1600\/A16-moving.gif\")
<\/p>\n Posted by Matthew McCullough \u2013 VP of Product Management, Android Developer<\/em><\/p>\n Today we’re bringing you Android 16 beta 4, the last scheduled update in our Android 16 beta program. Make sure your app or game is ready. It’s also the last chance to give us feedback<\/a> before Android 16 is released.<\/p>\n This is our second platform stability<\/a> release; the developer APIs and all app-facing behaviors are final. Apps targeting Android 16 can be made available in Google Play. Beta 4 includes our latest fixes and optimizations, giving you everything you need to complete your testing. Head over to our Android 16 summary page<\/a> for a list of the features and behavior changes we’ve been covering in this series of blog posts<\/a>, or read on for some of the top changes of which you should be aware.<\/p>\n <\/image><\/p>\n The Android 16 Beta is now available on handset, tablet, and foldable form factors from partners<\/a> including Honor, iQOO, Lenovo, OnePlus, OPPO, Realme, vivo, and Xiaomi. With more Android 16 partners and device types, many more users can run your app on the Android 16 Beta.<\/p>\n <\/image><\/p>\n If you develop an SDK, library, tool, or game engine, it’s even more important to prepare any necessary updates now to prevent your downstream app and game developers from being blocked by compatibility issues and allow them to target the latest SDK features. Please let your developers know if updates to your SDK are needed to fully support Android 16.<\/p>\n Testing involves installing your production app or a test app making use of your library or engine using Google Play or other means onto a device or emulator running Android 16 Beta 4. Work through all your app’s flows and look for functional or UI issues. Review the behavior changes<\/a> to focus your testing. Each release of Android contains platform changes that improve privacy, security, and overall user experience, and these changes can affect your apps. Here are several changes to focus on that apply, even if you aren’t yet targeting Android 16:<\/b><\/p>\n Other changes that will be impactful once your app targets Android 16:<\/p>\n Get your app ready for the future:<\/p>\n Remember to thoroughly exercise libraries and SDKs that your app is using during your compatibility testing. You may need to update to current SDK versions or reach out to the developer for help if you encounter any issues.<\/p>\n Once you\u2019ve published the Android 16-compatible version of your app, you can start the process to update your app’s targetSdkVersion<\/span><\/a>. Review the behavior changes that apply when your app targets Android 16<\/a> and use the compatibility framework<\/a> to help quickly detect issues.<\/p>\n This Beta is for the next major release of Android with a planned launch in Q2 of 2025 and we plan to have another release with new developer APIs in Q4<\/a>. This Q2 major release will be the only release in 2025 that includes behavior changes that could affect apps. The Q4 minor release will pick up feature updates, optimizations, and bug fixes; like our non-SDK quarterly releases, it will not include any intentional app-breaking behavior changes.<\/p>\n <\/image><\/p>\n We’ll continue to have quarterly Android releases. The Q1 and Q3 updates provide incremental updates to ensure continuous quality. We\u2019re putting additional energy into working with our device partners to bring the Q2 release to as many devices as possible.<\/p>\n There\u2019s no change to the target API level requirements and the associated dates for apps in Google Play; our plans are for one annual requirement each year, tied to the major API level.<\/p>\n You can enroll any supported Pixel device<\/a> to get this and future Android Beta updates over-the-air. If you don\u2019t have a Pixel device, you can use the 64-bit system images with the Android Emulator<\/a> in Android Studio. If you are currently on Android 16 Beta 3 or are already in the Android Beta program, you will be offered an over-the-air update to Beta 4.<\/p>\n While the API and behaviors are final and we are very close to release, we’d still like you to report issues<\/a> on the feedback page<\/a>. The earlier we get your feedback, the better chance we’ll be able to address it in this or a future release.<\/p>\n For the best development experience with Android 16, we recommend that you use the latest Canary build of Android Studio Narwhal<\/a>. Once you\u2019re set up, here are some of the things you should do:<\/p>\n We\u2019ll update the beta system images<\/a> and SDK regularly throughout the Android 16 release cycle. Once you\u2019ve installed a beta build, you\u2019ll automatically get future updates over-the-air for all later previews and Betas.<\/p>\n For complete information on Android 16 please visit the Android 16 developer site<\/a>.<\/p>\n<\/div>\n![](\"https:\/\/blogger.googleusercontent.com\/img\/b\/R29vZ2xl\/AVvXsEjTbEtmcMRsVnZNjDLfHHmaHRbWrOxiuKlPvOEKOdTQv5zdrBXiwR2seAo7nH7WHr5OBn-40Cokd-O8A39uNI8YPwNPS0KyNKmR5KfMdKWylTB2urSRAtJKSybArxjCTCi5dJghCUPgA49ZVOn3_4TLqppzii0bc5PDKdbeHzGfG0DrNeAyjbt5VSoOVYI\/s1600\/image1.gif\")
<\/a><\/div>\nAndroid 16 Beta 4<\/span><\/h2>\n
<\/div>\nNow available on more devices<\/span><\/h2>\n
<\/div>\nGet your apps, libraries, tools, and game engines ready!<\/span><\/h2>\n
\n
\n
\n
\n
\n
\n
Two Android API releases in 2025<\/span><\/h2>\n
<\/div>\nGet started with Android 16<\/span><\/h2>\n
\n
\n