Samsung’s Galaxy XR is now available to order in the US and South Korea for $1,800, with controllers sold separately for $250. That price and hardware spec sheet — dual 4K AMOLED displays at 90Hz, a Snapdragon XR2+ Gen 3 chip — is what most coverage has led with. The more consequential detail for anyone building spatial work is what it runs: Android XR, Google’s new platform, with a Samsung interface layer on top rather than a Samsung-proprietary OS underneath.
Watch: Google Android XR — Headset & Glasses Unveiled (YouTube)
Why “runs on standards” is the actual headline
Android XR is built around OpenXR, WebXR, Unity, and Unreal Engine support from the outset, rather than requiring a platform-specific toolchain the way a fully native visionOS app does. Unity 6 ships a dedicated Android XR build profile, giving developers a production-ready path that reuses the same XR Interaction Toolkit, OpenXR plugin, and asset ecosystem Unity XR developers already know from other headsets. WebXR is supported directly in Android XR’s browser, meaning immersive content can ship as a web page the same way it increasingly can on visionOS 27’s Safari.
The practical implication: work built against open standards for Android XR has a real chance of running on whatever comes next in this ecosystem too, rather than being locked to Galaxy XR specifically the way a visionOS app is locked to Apple hardware. Google has already confirmed Android XR won’t stay confined to headsets — Xreal’s Project Aura smart glasses are built on the same platform, expected later this year.
The timing is not a coincidence
Meta has confirmed there’s no Quest 4 in 2026 — the next Quest headset isn’t expected until 2027. That leaves a real gap in the consumer XR headset market at exactly the moment Samsung and Google are shipping a genuine alternative, and it’s likely to shift where developer attention goes over the next year, at least at the margins.
What this means if you’re deciding where to build
If cross-hardware reach matters more than deep integration with one vendor’s specific rendering pipeline, Android XR’s standards-first approach is worth serious evaluation alongside visionOS — particularly for anyone already using Unity or already shipping WebXR content, since the retooling cost is lower than starting a native visionOS build from scratch. It’s not a strictly better choice than visionOS’s more integrated, higher-fidelity toolchain — it’s a different bet, on openness over polish, and which one is right depends entirely on whether you’re optimizing for reach or for depth on a single platform.
Related Reading
- Samsung Galaxy XR With Android XR Out Now for $1,800 — UploadVR
- Android XR: Everything You Need to Know — Tom’s Guide
- Unity Powers Launch Titles for Samsung’s Galaxy XR and Accelerates the Android XR Ecosystem
- Giving Your Apps a New Home on Samsung Galaxy XR — Android Developers Blog
- Design for Unity, OpenXR, and WebXR — Android Developers