Insights · guide
SteamVR vs OpenXR choose with a runtime map
Drafted with Insight · edited by The WE ARE VR team
development

I would choose the runtime map before choosing the XR plugin.
I wrote this because “SteamVR or OpenXR?” often appears too early. For Jozi teams moving between studios, client offices and event venues, that shortcut creates avoidable setup work.
What's the problem?
SteamVR and OpenXR are different kinds of technology. Treat them as two linked decisions.
OpenXR is a common application programming interface, or API. An API is the agreed set of calls your app uses for tracking, controller input and rendered frames. A runtime is the software that manages those requests for the headset.
SteamVR is a runtime included with Steam. Steam is also a distribution ecosystem. SteamVR can run an application built with OpenXR. Meta Horizon Link can provide another OpenXR runtime for Quest headsets connected to a PC.
Several runtimes may be installed, but only one OpenXR runtime is active at once.
The common mistake is choosing from the headset on your desk. You test with a Vive through SteamVR and select a SteamVR-specific path. Later, you learn that the client expects a private executable running through Meta Horizon Link.
The build may still work. Deployment now carries extra questions about Steam installation, runtime selection and controller bindings.
At a Jozi event, those questions arrive while someone waits in a headset. That is poor timing (the queue will conduct its own usability study).
What's the solution?
Make a one-page runtime map before committing the project.
Write three columns: headset, runtime and distribution. Add one row for every place the build must run. Distribution means how the build reaches the PC. That could be Steam, a private installer, a copied folder or a client-managed system.
Imagine a training demo with these targets:
- Valve Index in your studio, using SteamVR.
- Quest over Meta Horizon Link at a Rosebank client office.
- A hired Vive at a Sandton exhibition, using SteamVR.
This map points towards OpenXR as the application interface. You can maintain one main PC build while testing it against SteamVR and Meta’s runtime.
You still need real device checks. Controller profiles, optional OpenXR extensions and performance can differ between runtimes. OpenXR reduces ecosystem-specific code, but it does not remove testing.
Choose a SteamVR-specific API only when every target PC uses SteamVR, or the project needs a feature unavailable through your required OpenXR runtimes. Record that dependency beside the relevant row.
If the public release belongs on Steam, SteamVR remains a sensible runtime. You can still build the application through OpenXR.
The practical default is simple: use OpenXR, test every expected runtime, and document each vendor-specific exception.
What's next?
- List every headset, PC owner and delivery method for one current project. Include the event machine you have not booked yet.
- Confirm the active OpenXR runtime on each available PC. Test launching, tracking, buttons, view resetting and headset removal.
- Run one packaged build across two runtimes. Record differences before adding any vendor-specific code.
Share your runtime map or send us the awkward headset combination you need to support.
The WE ARE VR team
