Now in Android #87

Most of the content of this post is available in the form of a video or podcast, so feel free to watch or listen rather than read on. (Or do all three to help you remember! There won’t be a quiz.)

On July 11th, we released the 4th Beta of the Upcoming Android 14 OS! Beta 4 is our second Platform Stable Android 14 release, which means that the developer APIs and all app-facing behaviors are final for you to review and integrate into your apps.

It’s a good time to finish compatibility testing and publish any necessary updates to ensure a smooth app experience ahead of the final release of Android 14 later this year.

If you develop an SDK, library, tool, or game engine, it’s even more important to release any necessary updates now to prevent your downstream app and game developers from being blocked with compatibility issues

Check out the blog, For more information on the latest Beta 4 release!

One of the many ways we keep Google Play a safe and trusted platform is by verifying the identity of developers and their payment information.

So, we’ve expanded developer verification requirements in our Play Console Requirements policy. As part of this update, we’ll also share more developer details on your app’s store listing page to help users make confident, informed choices about what to download.

When you create a new Play Console developer account for an organization, you’ll now need to provide a D-U-N-S number. Assigned by Dun & Bradstreet, D-U-N-S numbers are unique nine-digit identifiers that are widely used to verify businesses.

This is just one of the ways we are building trust and ensuring a safe and secure Google play.

Check out more in this blog post!

This week is all about the release of the Compose Compiler 1.5.0 which brings Experimental K2 support!

Check out episode 199 of the Android Developers Backstage podcast, on compose performance

In this episode, we have several members of the compose team chatting about compose performance!

The team has been looking at performance issues recently and discusses what they’ve found, what gotchas lie in wait for library developers, what tools and compilers can magically handle for you… and what they can’t.

You can check out the episode in podcast or video form, and you can watch this short clip on how to avoid a common location developer mistake.