Android XR glasses for developers: the story Samsung skipped

On July 22, Samsung walked onto the Galaxy Unpacked stage in London and showed its first Android XR smart glasses — two frames made with Gentle Monster and Warby Parker, a 12-megapixel camera, Gemini built in, audio-only for this first generation with a display model to follow. It's a real product from a real partner in Google's glasses push, and it's going to matter.

Then Samsung declined to say what it costs, when it ships, how much it weighs — or the one thing this blog cares about: what any of it means for the people who'll build the software on it.

That omission isn't an oversight; it's the most honest thing about the reveal. So here's the part Samsung skipped — what building on Android XR glasses actually looks like today, and where it stands next to the platform most glasses developers already know: Meta's.

What's actually shippable (nothing, yet)

Start with the good news, because it's genuinely good: the Android XR SDK is open to everyone. Google opened AI-glasses development to all developers back in Developer Preview 3 (December 2025) — no allowlist. You install Android Studio, pull in the Jetpack XR SDK, and get an AI Glasses emulator that simulates the touchpad and voice input. You can start building a glasses app this afternoon, on hardware you don't own.

Here's the catch, and it's a big one: you can build, but you can't ship. There is no Android XR consumer glasses you can buy today — Samsung's reveal was a name and a tease, not a launch — and there is no public distribution channel for glasses apps. Google's own docs are blunt about it: Play Store distribution currently covers XR headsets and wired glasses only; for the audio/display glasses class, developers should "run and debug apps on the emulator," with "more updates on distribution coming in the future."

So the state of Android XR glasses development in July 2026 is a clean inversion of what you'd expect: the tools are wide open, the door to real users is shut.

The app model is not what you think

If you're picturing an app that runs on the glasses, stop. Android XR glasses use a projected model, and it's the detail every developer arriving from another platform trips on.

Your code doesn't run on the glasses. It runs natively on the paired phone — an ordinary Android app, Kotlin and Compose — and declares a special projected activity whose UI and I/O are beamed out to the glasses over the phone link. The glasses are a display-and-sensor surface; the compute and the app process stay on the phone. Google's own words: a "dedicated activity that runs within your phone's existing app… projected from the host device to the glasses."

Two consequences worth internalizing now:

• It's a phone app first. Camera, microphone, and speaker access come through Jetpack Projected with runtime permission prompts, exactly like a phone app — because that's what it is. Display UI (on the display models) is authored in Jetpack Compose Glimmer.
• iPhone pairing is a consumer fact, not a developer one. Yes, Google says the glasses pair with iPhones. But a third-party projected app is an Android Activity in an Android manifest, and there is no documented iOS host path for it. If you're building, you're building on an Android host.

What Meta already answers that Android XR hasn't

This is where shipping on the other major glasses platform buys you perspective. Put them side by side and the trade is stark.

Meta's Device Access Toolkit gives you the thing Android XR can't yet: an app on a real pair of glasses, on a real person's face. The hardware exists and is in developers' hands. The SDK is native and callable today — camera, audio, the works. The catch is the front door: distribution runs through invite-only release channels, so reaching users is gated and deliberate. Closed, but real.

Android XR is the mirror image. The SDK is more open than Meta's — no invite required to write and emulate — but there's no hardware to buy and no way to publish a glasses app to anyone. Open tools, no exit.

Neither is "better." They're two different bets at two different stages — and, the part that matters, two completely different developer models. Meta's is a native SDK talking to glasses over a Bluetooth transport. Android XR's is a projected activity running on the phone. The same use case — point a camera, run a voice assistant, put a line of text in front of someone's eyes — reached two incompatible ways.

The real story: there are now two of everything

Smart glasses have had developer SDKs for years — Vuzix, Rokid, Brilliant Labs, and a dozen others we track. What changed on July 22 is the arrival of a second consumer platform with a phone giant behind it and a mass-market developer push — one that shares nothing under the hood with the first. Google's "Hey Google" wake path now sits reserved next to Meta's "Hey Meta." A projected phone activity sits opposite a native DAT session. And more vendors are already visible on the roadmap.

That's the story Samsung actually skipped: not the frames or the camera, but the fact that the glasses space just became a multi-platform problem — and each platform hands you a different transport, a different app model, and a different set of things you're not allowed to do. Writing the same feature twice, once against DAT and once against a projected activity, is the tax that arrives with the second platform.

Erasing that tax is exactly what we're building Extentos for: one app, the same capability calls, mapped onto each vendor's transport underneath. We track every one of these platforms — SDK access, app model, distribution, limits — in the Extentos ecosystem reference, which is where the details behind this post live and stay current as the fall launches land.

What to watch next

Two dates. The Android XR audio glasses ship "this fall," and that's when price, weight, and — most importantly — the distribution story stop being blanks. And Meta Connect, September 23–24, where Meta is already teasing new glasses of its own. Between them, the shape of the glasses-developer landscape for the next year gets drawn.

We'll have a developer's read on both, the day they land.