Start a project

← All posts

Android XR at Google I/O: Is It Time to Start Building for Glasses?

· Dracode · android · developer-tools · ai
Colorful code displayed on a smartphone screen with a warm glow

What Google Actually Shipped at I/O 2026

Google I/O 2026 ran as an AI keynote — Gemini 3.5, Gemini Spark, a rebuilt Search, and an agentic tools layer — and then spent its final segment on hardware. The centerpiece was Android XR glasses, with multiple partners confirmed: Xreal’s Project Aura (Android XR fused with Xreal’s optics work), fashion partnerships with Gentle Monster and Warby Parker, and Samsung’s own Android XR device featuring an AR display, enhanced AI, and smartwatch tethering. All of it ships “this fall.”

The honest reading: this is still a developer-facing launch in consumer packaging. Hardware due in months means apps need to exist before then. Google’s Developer Catalyst Program is already accepting applications, offering hardware, funding, and resources to teams building XR experiences.

Developer Preview 4: Further Along Than It Looks

Android XR reached Developer Preview 4 in May 2026. Version numbers in preview programs track meaningful progress: DP1 is exploration, DP4 is APIs stabilizing. The tooling is now concrete.

For Android developers, the SDK maps directly onto familiar patterns:

  • Jetpack Compose for XR handles spatial UI for headsets and wired glasses — panels in 3D space, spatial composition, environmental anchoring
  • Jetpack Compose Glimmer is the glasses-specific toolkit, designed for glanceable, high-contrast overlays on display glasses
  • Jetpack SceneCore covers 3D entity management — spatial positioning, 3D model loading (glTF/GLB formats), environment APIs
  • ARCore for Jetpack XR adds real-world perception: anchor detection, semantic segmentation, surface understanding

Android Studio already ships XR-specific virtual devices for all four form factors: XR headsets, wired XR glasses, audio glasses, and display glasses. You can build and test against emulated hardware today.

The compatibility model is also generous. Google structures apps into three tiers: existing Android apps that run as 2D panels with no modification, large-screen adaptive apps that work across device types automatically, and XR-differentiated apps that use the spatial APIs. That middle tier means most mature Android apps are already “compatible” on paper, which lowers the cost of at least testing the experience before committing to a deeper port.

The Two Form Factors Are Not the Same App

The device taxonomy matters more than it appears in Google’s announcements. Android XR covers four hardware categories, but the two relevant to glasses are genuinely different development targets.

Audio glasses have no display. From a UX standpoint, they are closer to earbuds with a local model and an always-on microphone than to anything in the AR space. The interaction model is entirely voice-driven. Google’s design guidance emphasizes concise audio responses, proactive notifications, and state-triggered outputs — the same principles as a well-designed voice assistant. The app listens, processes context, and responds audibly. Writing UI for it means writing dialogue flows, not layouts.

Display glasses add an AR overlay. The Glimmer design system exists specifically for this form factor: glanceable visuals, contextual appearance that surfaces information only when relevant, “subtle integration” that augments without obstructing what the user sees. Content has to work at low contrast over an unpredictable real-world background, inside a one-to-three second attention window, without requiring manual interaction.

A team building for Android XR glasses should answer one question first: audio or display? The design work forks completely at that decision. An audio-first app with a display fallback is achievable. Building both simultaneously without a clear primary target is the usual way to produce a mediocre version of each.

What Meta Ray-Bans Changed (and What They Didn’t)

Meta has done something concrete for the glasses category: Meta Ray-Bans with Meta AI have sold well enough to prove that audio-only AI glasses find a consumer market. That validation removed the biggest early-market risk — whether people would actually buy and wear these things in daily life.

What Meta Ray-Bans don’t offer is a developer platform, ARCore-level environmental sensing, a Figma kit, or IDE integration. Android XR is targeting a different capability ceiling: glasses that can perceive and annotate the world, not just hear and respond to you. Whether that capability produces compelling apps, and whether consumers will pay a premium for it over the simpler audio model, is the open question.

Google Glass failed at exactly this point. The platform launched before the apps existed, the apps that did exist felt engineered rather than useful, and the form factor’s social friction outweighed the marginal utility. Android XR has two advantages Google Glass didn’t: Meta Ray-Bans have already normalized wearing AI hardware on your face, and the SDK is substantially more mature before consumer hardware ships. The risk in 2026 is not the hardware — it’s whether the ecosystem generates useful apps inside the launch window.

What We’re Watching

The Developer Catalyst Program application is worth evaluating for any team with a concrete product concept that fits the audio or display glasses use case. Physical hardware access before consumer release is a meaningful advantage for teams that want to ship at launch rather than six months after.

At Dracode, we build mobile-first products for founders and scale-ups. Android XR is the most developer-legible new hardware platform we have seen since the Apple Watch SDK launched in 2015. The toolchain is familiar, the emulator exists, and the hardware date is firm. We are not advising clients to pivot to glasses as a primary platform — but the teams that ship compelling Android XR apps at launch are building in Developer Preview 4 right now.

The question worth asking is whether the use case you are building warrants three months of focused parallel development. If you are working through that decision, get in touch.

Sources

  1. Android XR developer overview — Google Android Developers, May 2026
  2. AI Glasses design guidance for Android XR — Google Android Developers, May 2026
  3. Project Aura glasses are a big step towards a perfect XR experience — MobileSyrup, May 22 2026
  4. Google I/O 2026 Hardware: 4 Reveals From Gentle Monster Glasses to Googlebook — The Gadgeteer, May 21 2026
  5. Google’s Smart Glasses Plan To One-Up Meta’s Ray-Bans With These 4 New Features — BGR, May 21 2026