Android XR Jetpack SDK beta release artwork from Android Developers

Jetpack XR Core Hits Release Candidate. Compose for XR Still Alpha.

by

Google’s Jetpack XR core stack just crossed another gate. On September 9, 2026, the AndroidX release notes moved Jetpack SceneCore, ARCore for Jetpack XR, and XR Runtime to 1.0.0-rc01 — the first Release Candidate for the libraries that power immersive apps on Android XR headsets and wired XR glasses. Jetpack Compose for XR remains on the alpha track.

Android XR Jetpack SDK release artwork
Jetpack XR SDK artwork from the Android Developers Blog. Image: Google / Android Developers.

That RC lands three weeks after Google’s August 18 developer post announced that SceneCore, ARCore for Jetpack XR, and XR Runtime had reached beta — with Compose for XR “to follow soon.” The Maven coordinates in that post still pointed at 1.0.0-beta02. The docs pages for each library now list RC01 dated September 9 as the latest update, with no stable release yet.

What RC01 actually ships

Per the Android Developers release notes (last updated September 9):

  • SceneCore 1.0.0-rc01 — adds an xr:scenecore:scenecore-openxr library, removes several deprecated APIs ahead of 1.0 stable, and fixes a memory leak that could retain an Activity after destroy.
  • ARCore for Jetpack XR 1.0.0-rc01 — Release Candidate cut; the notes page does not list additional API churn beyond the beta-era perception stack (anchors, planes, hit testing, depth).
  • XR Runtime 1.0.0-rc01 — improved internal lifecycle handling. The same day also opened a parallel 1.1.0-alpha01 line that adds SPATIAL_API_V4 to SpatialApiVersions.

Google’s August beta write-up still frames the product story: SceneCore for the 3D scene graph and spatial audio; ARCore for Jetpack XR for depth, persistent anchors, hit tests, and planes; XR Runtime for session lifecycle; Compose for XR for spatial UI (still alpha in the sample Gradle block, at 1.0.0-alpha17 in that post).

Android XR development illustration
Android XR illustration from Google’s developer materials. Image: Google / Android Developers Blog.

Why the timing matters

Samsung’s Galaxy XR is already shipping as the first Android XR headset. Fall display-glasses timelines from Samsung, XREAL, and partners keep adding surfaces that need the same Jetpack APIs. Moving the core three libraries from beta to RC is the signal developers wait for before locking production Gradle pins — even while Compose for XR stays experimental.

Beta already brought the API cleanups Google flagged in August: expanded testing hooks for spatial audio and devices, Session.create as a suspend function, and the rename of AnchorEntity to AnchorSpace under a shared SpaceEntity base. RC01 is the “freeze for 1.0” cut, not a second marketing launch.

Jetpack XR SDK banner
Jetpack XR SDK banner from the Android Developers Blog. Image: Google.

What is still open

Google has not published a calendar day for 1.0 stable. Compose for XR is explicitly still alpha in the August post. Dependency snippets on the SceneCore, ARCore, and Runtime docs pages still show example lines at beta02 in places even as the version table header lists RC01 — treat the version table and changelog as authoritative, and pin the coordinate you intend to ship.

Primary sources: Android Developers Blog, August 18, 2026; SceneCore release notes; ARCore for Jetpack XR release notes; XR Runtime release notes (all three listing 1.0.0-rc01 on September 9, 2026).

Leave a Comment