We released Android 14 and pushed the Android 14 source to the Android Open Source Project (AOSP). Thank you again for taking part in our developer preview and beta programs, sharing your feedback, and making sure your apps deliver a great experience on Android 14.
The post covers some of the impact of performance and efficiency changes in Android 14; it explained how freezing cached applications, optimizing broadcasts, and reducing the memory footprint of ART code allowed Android to increase long-standing limits around cached applications, leading to fewer cold starts; fewer cold starts means faster app launches that use less power.
Finally, the post covered the Android SDK upgrade assistant within Android Studio, and how to use it to assist you in updating your app for the latest targetSDK version.
We announced that the Pixel Watch 2 is here and it ships with Wear OS 4, joining the Samsung Galaxy Watch 4, 5, and 6 series devices on the platform. The first gen Pixel Watches will receive a system update to Wear OS 4 over the coming weeks in phases depending on carrier and device. Wear OS 4 includes the declarative XML Watch Face Format, supports transferring data from one Wear OS watch to another using cloud backup and restore, allows users to transfer their watch to a new phone without needing to perform a factory reset, offers enhanced capabilities for tiles, and more.
Chris covered Device Streaming in Android Studio, an early-access service powered by Firebase that allows you to manually interact with and test your app on real physical devices located in Google’s secure data centers directly from within Android Studio. Select the device you want, connect, and, in moments, you’ll have a direct ADB connection to the device, allowing you to use your favorite tools both within and outside of studio, such as Logcat, the debugger, Profilers, UI design tools, and more — just like you would with a local device. To learn more and register for the program, visit the sign-up page.
We had some fun shorts hit the channel, including Building UIs for all form factors, a reminder that Jetpack Compose can be used to target phones, foldables, tablets, watches, and TVs — as well as laptops and PCs too.
WindowSize — With new display modes like multi-window, you should check how much window space is currently available to your app instead of using the device display size and then use the WindowSize classes to implement an adaptive layout.
Optimize for foldables — You can use the WindowInfoTracker to query the state, occlusionType, orientation, bounds of FoldingFeatures to implement things like tabletop mode
Showing two activities side by side — The library also provides you the ActivityEmbedding APIs to implement things like List/Detail layout with minimal code changes but embed an activity from another app into yours, so. your users can perform other tasks without losing context.
Future releases plan to add APIs for concurrent display modes, for example, to take selfies using the better rear camera.
Finally, we covered when to use Google Pay vs. Google Play billing. Google Play’s billing system is a service that enables you to sell digital products and content in your Android app, while Google Pay billing covers other things your app might sell like physical content.
We had several launches in Android Jetpack:
Browser 1.7 alpha01 added a bunch of new APIs providing more control around CustomTabs, including enabling the bookmarks and download button in the overflow menu, enabling sending initial URLs to external handler apps, specifying the target language the Translate UI should be triggered with, and more.