A developer opening Android Studio to target a headset instead of a phone now has firmer ground to stand on. On 18 August 2026 Android Developers Blog, Google said three core Jetpack XR libraries — SceneCore, ARCore for Jetpack XR, and XR Runtime — have moved from developer preview to beta.
Google said the beta means “the APIs are stabilizing, making it a great time to start integrating them into your production workflows” Android Developers Blog.
Beta is the signal app teams wait for before committing real code. Once interfaces stabilize, the work they ship is far less likely to break with the next release. But the stabilization is incomplete. Jetpack Compose for XR, the spatial-UI toolkit, is still pinned at version 1.0.0-alpha17 — alpha, not beta Android Developers Blog. Concerns linger about building production interface code while that layer stays in flux.
What the three libraries actually do
Each library now covers a distinct layer of an XR app. SceneCore builds and manipulates the 3D scene graph, handling spatial audio and an entity-component system. ARCore for Jetpack XR brings depth estimation, persistent anchors, hit testing, and plane identification into the real world. XR Runtime manages device lifecycle, session creation, and system configuration beneath it all Android Developers Blog.
The device side is still thin. Google said the ecosystem is “expanding, ranging from XR headsets to wired XR glasses” and pointed builders toward Samsung Galaxy XR and the Android XR Emulator for real-hardware testing Android Developers Blog. The headset-and-glasses market remains a fraction of the phone install base. Yet the bet is that stable APIs pull more developers in before the hardware arrives in volume.
The breaking changes beta brings
The beta tightens the developer surface in ways that will require code changes. Session.create is now a suspend function aligned with Kotlin coroutines, and AnchorEntity has been renamed to AnchorSpace, with both ActivitySpace and AnchorSpace now extending a shared SpaceEntity class Android Developers Blog.
Those moves tie the XR stack closer to Google’s broader Jetpack library set, which helps teams follow best practices and cut boilerplate Android Jetpack. The coroutines change also shows how tightly the XR layer now tracks Kotlin’s modern idioms Kotlin on Android.
Android’s surface is shifting elsewhere too. Google’s Pixel 11 Fold changes how Android apps adapt to folding screens, a reminder that the same developers now juggle XR, foldables, and tablets at once zBrandco.
The libraries are stable enough to build on, but the toolkit that draws the interface is not. For Android XR to move from demo to daily driver, that last layer has to clear beta too — and the headsets have to show up.
