If you watched Google I/O 2026 and found yourself confused about where Android XR ends and Project Aura begins, you’re not alone. Google has been telling the Android XR story in pieces since last year — the operating system, the Samsung Galaxy XR partnership, the developer preview — and it wasn’t until this month that the full picture snapped into focus. Here’s what actually changed, and what it means if you’re building for the platform.
What Google Announced (the Actually Important Bits)
The headline hardware reveal was XREAL’s Project Aura: lightweight smart glasses running Android XR natively, with a 70-degree field of view, pass-through cameras, and no tethering required. They’re not a dev kit — they’re a consumer product, and XREAL is positioning them as the accessible entry point into the Android XR ecosystem alongside Samsung’s bulkier headset. A 70-degree FOV is meaningfully wider than what most current smart glasses offer, though still narrower than a full AR headset. Think of them as a capable middle ground between Ray-Ban Meta (audio plus camera, no display) and something like a HoloLens 2.
The more significant announcement for developers, though, was the SDK consolidation. If you’ve been putting off building for Android XR because the toolchain felt fragmented — ARCore here, Jetpack SceneCore there, XR Jetpack libraries in a third place — Google has collapsed all of that into a single unified SDK. ARCore is now the spatial understanding layer. Jetpack SceneCore handles scene management and rendering. The new XR Jetpack libraries sit on top and give you composable UI components for spatial layouts. You write once, target both headset and glasses form factors, and the platform handles the rendering differences.
That’s the theory, anyway. The developer preview has been live since early May and the Unity and Unreal plugin updates landed the week before I/O, so there’s already real feedback coming in from early testers.
Designing for 70 Degrees
Here’s a constraint that will shape your app design decisions: at 70 degrees FOV, the sweet spot for comfortable reading is roughly the central 35–40 degrees. Text and interactive elements at the edges get distorted and cause eye strain in longer sessions.
What that means practically: don’t design spatial UI that fills the entire field of view. The temptation when you’ve got 70 degrees to work with is to spread things out, but user testing on similar hardware consistently shows people prefer a narrower, more focused content area — something closer to where they’d naturally hold a phone at arm’s length — with ambient context in the periphery rather than dense information.
The Jetpack SceneCore APIs give you SpatialLayout and SpatialPanel composables that abstract a lot of this, and Google’s updated design guidelines include recommended panel widths for both the glasses and headset targets. Worth reading before you start prototyping.
The Developer Catalyst Programme
This is the concrete thing to act on if you’re interested in building for Android XR. Google opened applications to the Developer Catalyst Programme at I/O — a programme that provides early hardware access (Project Aura units), developer support, and co-marketing opportunities for qualifying apps.
The selection criteria aren’t entirely transparent, but Google has emphasised utility apps, productivity tools, and enterprise use cases over games and entertainment for this first wave. If your app has a clear “hands-free professional use” angle — field service, healthcare, remote assistance, navigation, any scenario where a phone is inconvenient but context matters — that’s the lane they’re signalling interest in.
Applications are open now and the first hardware allocations ship in late Q3. Realistically, if you apply in May you’re looking at building on actual hardware by September.
What’s Still Missing
To be honest, Android XR still has gaps that matter. Eye tracking is supported in the headset form factor but not in Project Aura’s glasses — the hardware doesn’t have it. That limits any app that relies on gaze-based interaction or foveated rendering. Voice input is the primary interaction model on glasses, and while Google’s on-device speech recognition is genuinely good now, it’s not a complete substitute for gaze-based pointing in complex spatial UIs.
Multimodal understanding — using the cameras to understand what the user is looking at and respond contextually — is in preview but unreliable enough that I wouldn’t ship a product depending on it today. The capability is there; the consistency isn’t yet.
And the app ecosystem is still thin. Being an early mover matters here, but don’t expect a ready-made audience until the hardware is in enough hands to justify content investment. The Samsung Galaxy XR headset has the installed base right now; the glasses are starting from scratch.
Should You Build for It Now?
If you’re an indie developer weighing the opportunity cost, here’s the honest calculation: Android XR is the largest potential XR market because it’s Android, and Google is clearly investing seriously in it. But Project Aura is a first-generation consumer device and the SDK just stabilised. You’re getting in early, not getting in at the right time.
The developers who’ll be best positioned aren’t necessarily the first to ship — they’re the ones who spend the next few months building institutional knowledge of the platform so they can move fast when the hardware reaches meaningful scale. Apply for the Catalyst Programme, start with the emulator, get familiar with Jetpack SceneCore, and keep an eye on what gets approved for the first hardware wave. That’s the useful move right now.