SoftwareNovember 17, 2026

Android XR Supports OpenXR Spatial Containers Now, but Only in Full Space

By Nina Castillo
Staff Writer, VR.org
Share

A spatial container on Android XR is a box the system puts in the room, and your app draws inside it. Two OpenXR extensions describe how, XR_EXT_spatial_container and XR_EXT_spatial_container_self_rendering, and Google's Spatial Containers guide now lists both on Android XR devices running Spatial API Level 4 or higher. When Khronos announced the extensions on October 19, no shipping runtime offered them. Now one platform documents support.

Advertisement
Illustration of a person standing among four yellow blocky ducks on a pale floor, facing a large curved blue panel, after a spatial container has switched to immersive mode
Image: Google / Android Developers, CC BY 2.5. The demo scene from Google's guide after its container switches from bounded to immersive mode.

Ask the runtime, not the OS

Do not branch on the Android release. The guide tells you to query the OpenXR runtime instead: confirm both extensions are listed, then call xrGetSystemProperties with XrSystemSpatialContainerPropertiesEXT chained on and read supportsBounded and supportsImmersive. A runtime only has to implement one of the two modes, so those are separate booleans, and you want both answers before you design around either.

Bounded mode is the box. You suggest a width, a height and a depth in meters, the system allocates a box in the room and clips your content to it, and the person wearing the headset can pinch the container's system handle and move it. Immersive takes the walls away and gives you the whole field of view, the way a full-screen OpenXR session always has. You switch between them at runtime with xrRequestSpatialContainerBoundsModeEXT, no session restart, and the request can be turned down. Unity exposes it as XRSpatialContainerFeature.TryRequestBoundsMode, Godot as OpenXRSpatialContainerExtension.request_main_spatial_container_bounds_mode.

The catch is Full Space

Spatial containers on Android XR require Full Space Managed mode, even for a standalone OpenXR app. In practice that is one manifest property, android.window.PROPERTY_XR_ACTIVITY_START_MODE, set to XR_ACTIVITY_START_MODE_FULL_SPACE_MANAGED instead of the unmanaged value a traditional full-screen OpenXR app declares. Home Space, where Android XR runs apps side by side, is not where containers live. Google's design guidance describes Full Space in two short sentences: "One app runs at a time, with no space boundaries. All other apps are hidden."

So read the capability carefully. Khronos pitched the extensions as cross-platform spatial windowing, and the spec leaves room for several apps sharing one space. Android XR's first implementation is narrower. In native OpenXR your app can hold several containers at once and arrange them in its own Full Space; Unity and Godot put your whole scene in a single primary container for now. Either way, the containers live in a space that, by Google's definition, hides every other app. What this unlocks is one app built from more than one renderer: a Jetpack Compose interface next to a 3D volume drawn by Unity, Godot or native OpenXR. Google's Android Developer Summit post on November 6 points to a session on embedding "Godot and Unity as libraries inside native Jetpack Compose apps using OpenXR Spatial Containers."

Android Dev Summit title card reading Integrate 3D engines with Compose for XR, with photographs of three Google speakers
Watch: Elevate immersive experiences with 3D Engines in Jetpack Compose for XR on YouTube →

The versions, and the half that is still in beta

On the Unity side you need Unity 6 at 6000.0.58f2 or newer and the Android XR Extensions for Unity at 1.5.0 or newer. That package landed on October 27 with XRSpatialContainerFeature, an event for when the runtime refuses a mode switch, and an XRSpatialSdkVersions.XRSpatialApiLevel4 constant that its release notes tie to "the latest Android XR OTA releases." It is the clearest public marker of when this became buildable.

Godot is half there. The OpenXR Vendors Plugin 5.2.0 went stable on November 10, the first stable release since 5.1.0 in May, and its changelog carries the two pieces this needs: PR #536 adds exporting spatial container applications on Android XR, and PR #529 makes Android XR's spatial API version configurable. The engine is the other half. Google's Godot guide asks for 4.8-dev or newer, and 4.8 is still in beta, with beta 3 out November 9. You also have to tick Use Experimental Features under Android XR Features in the export preset. The plugin checks for it whenever Spatial Container is on, and injects com.android.extensions.xr.uses_experimental_openxr_feature into the manifest for you. Workable, and labeled as not finished.

Permissions are lighter than you might expect. A basic container needs no dangerous runtime permissions. Floor snapping is the exception: it wants android.permission.SCENE_UNDERSTANDING_COARSE, which the person has to grant while the app is running.

Google's applicable-devices box lists XR headsets and wired XR glasses, so XREAL AURA is in scope alongside Samsung's Galaxy XR, as long as the device is on an update with Spatial API Level 4. Past Android XR, portability is still a promise. Meta and PICO both put supporting quotes behind the extensions in October, and neither has said when its runtime will offer them. A ratified extension with one implementation is a start. It is also the first time a shipping platform has put these two headers in its own documentation.

Share
Advertisement