On Nov 6, 2026 the Android XR team published its Android Developer Summit round-up. The headline is a device: XREAL AURA, described as the first wired XR glasses powered by Android XR, at under 95 grams with a portable compute puck. The part that matters for code is underneath it. The core Jetpack XR libraries and the Studio emulators are now stable, so you can stop treating XR as a preview-only side project. If you followed my earlier Jetpack XR 1.0.0 stable post, this one covers the platform and tooling around it.
Scope note: the post is a summary with links to Dev Summit session videos. It does not publish API signatures or artifact versions, so I have not invented any here. Check the linked release pages for exact versions before you update your build files.
What went stable
- Jetpack SceneCore for building and manipulating the XR scene graph with 3D content.
- ARCore for Jetpack XR for environment perception.
- XR Runtime for standardized session management.
- Android XR emulators in Android Studio, so you can build and visually validate layouts across XR devices without hardware. The post specifically points to virtual devices for glasses form factors.
The practical meaning is long-term API stability. Earlier betas renamed and removed APIs between releases (I covered those in the beta01 breaking-changes post); a stable tier lets teams ship against it.
Geospatial: anchoring content to places
The Geospatial APIs in ARCore for Jetpack XR are now stable. They anchor digital content to real-world coordinates by combining visual positioning with local device tracking, aimed at location-aware experiences on wired XR glasses. For glanceable optical see-through UI the team points to Jetpack Compose Glimmer, and the session "Build world anchored experiences for XREAL AURA wired XR glasses" walks through pairing Glimmer UIs with world anchors.
For Unity teams, a separate session covers mapping physical spaces, persisting 3D placements across sessions and syncing shared multi-user experiences with Spatial Entities, Cloud Anchors and the ARCore Geospatial APIs.
Android XR Engine Hub
If your content lives in a game engine, the Android XR Engine Hub is now stable. It targets Unity, Godot and Unreal Engine and does two things:
- Project scaffolding with pre-configured OpenXR extensions and validated project settings.
- Native profiling workflows to capture and inspect system traces, thermal limits and frame budgets across CPU and GPU cores from inside the engine UI.
Setup is a plugin install for your engine of choice. A related session shows embedding Godot and Unity as libraries inside native Jetpack Compose apps using OpenXR Spatial Containers. As a proof point, Contract XR ported its Unity game Jigsaw Night to XREAL AURA as a collaborative multi-user experience.
Frame budget and thermals are the real constraint on glasses with a tethered puck. Having traces and thermal data inside the engine tooling, rather than a separate profiler, shortens the loop you will spend most of your time in.
Audio-first: ML Kit Text to Speech and earcons
As the lineup includes audio-oriented eyewear, the team introduced the ML Kit GenAI Text to Speech API for natural-sounding on-device voices, plus new design guidance on sound, including earcons for guiding users through audio-first environments. The session "Building audio-first experiences for intelligent eyewear with Gemini Nano 4" combines Jetpack Projected, ML Kit and on-device Gemini Nano for hands-free conversational apps. For the on-device model side, see my Gemma 4 and ML Kit GenAI post.
Existing apps on day one
The post states that XREAL AURA shares a common Android foundation, so existing Android apps work out of the box on day one. That is the cheap first step: install what you have, see how it behaves on glasses, then decide where spatial UI is worth the investment.
What I would do this week
- Update Android Studio to the latest stable and create a glasses virtual device.
- Run your current app on it and note which screens assume a touchscreen or a large window.
- Pick one glanceable surface (a notification, a status card) as a Glimmer prototype.
- If you ship a 3D title, install the Engine Hub plugin and baseline thermals and frame time before optimizing.
- Move any XR dependencies from beta to the stable releases listed on the Android XR developer site.
Sources: the Android Developers Blog post "Build for an expanding lineup of Android XR devices with production-ready tools from Android Developer Summit" (Nov 6, 2026), retrieved Nov 7, 2026.
No comments yet. Be the first to leave one!