Unity has been the default engine for XR development for so long that “learn Unity” and “learn to build for headsets” have practically meant the same thing. Google’s latest Android XR Developer Preview quietly changes that: alongside existing Unity support, the platform now officially supports Unreal Engine and Godot, with an Android XR Engine Hub that brings real-time device testing directly into whichever engine a developer is already using.
Watch: Google Android XR — Headset & Glasses Unveiled (YouTube)
What actually shipped
Developer Preview 4 delivers the APIs and libraries needed to design and build for both immersive and augmented experiences directly from a laptop, without a headset tethered the whole time. The Engine Hub is the part that matters practically: it puts live testing on real hardware inside the engine’s own editor, for Unreal and Godot exactly the same way it’s long worked for Unity. Google is also running a Developer Catalyst Program offering pre-release hardware, support forums, and launch guidance to studios preparing apps for Google Play on Android XR — support previously reserved, in practice, for teams already committed to Unity’s ecosystem.
Why this matters more than a typical SDK update
Godot in particular is free, open source, and has spent the last several years building a passionate following among smaller studios and solo developers who’ve found Unity’s licensing and workflow frustrating. Officially supporting it for XR — not as a community hack, but with the same real-time testing tooling Unity gets — opens headset development to exactly the developers who were most likely to have been priced or workflow-shut out of it before. Unreal’s inclusion matters differently: it brings Android XR into reach for studios already building high-fidelity 3D content in Unreal for games or film, without forcing a second engine into their pipeline just for a headset build.
The competitive backdrop
This lands as Samsung’s Galaxy XR — the first Android XR headset — sells at $1,799, roughly half of Apple’s $3,499 Vision Pro M5, with Gemini-powered spatial AI built in from the ground up rather than bolted on. Cheaper hardware plus a genuinely open choice of engine is a meaningfully different pitch to developers than “buy the expensive headset and learn the one engine it supports” — and it’s the more interesting story here than any single spec bump.
Related Reading
- What’s New in Android XR: Tooling, Engine Support, and Ecosystem Updates — Android Developers Blog
- Android XR — Android Developers
- Android XR 2026: A Technical Analysis of Why Google’s Open Ecosystem Is Poised to Dominate Spatial Computing — Frame Sixty
- Giving Your Apps a New Home on Samsung Galaxy XR — Android Developers Blog