Choose WebXR when reach and zero install matter more than peak graphics: campaigns, product viewers, event activations and anything opened from a link or QR code. Choose a native app when the experience needs the full power of the device, works offline, runs for long sessions, or must be managed on company headsets, as in training and simulation. Many projects need both: a light web version for reach and a native build for depth.
This guide explains what each option is, where each one runs today, and a short set of questions that settles the choice for most projects.
What is WebXR?
WebXR is the web standard that lets a page in a browser start a virtual or augmented reality session on a headset or phone. It is defined by the WebXR Device API, a W3C Candidate Recommendation Draft maintained by the Immersive Web Working Group. The specification defines three session modes: inline, immersive VR and immersive AR, with AR behaviour described in a companion module.
For the user, WebXR means opening a link and pressing a button. There is no store listing, no download and no update to install. MDN notes that the API is available only in secure contexts, so the site must be served over HTTPS.
What is a native immersive app?
A native app is installed on the device from a store or pushed by an administrator, and talks to the device through its own platform interfaces. On most headsets that interface is OpenXR, which Khronos describes as a royalty-free open standard providing a common set of APIs for XR applications. The current version is OpenXR 1.1, and Khronos lists conformant runtimes from Meta, Valve, PICO, HTC, Microsoft, Google, Magic Leap and Varjo.
Apple Vision Pro is the main exception: apps for it are built for visionOS with Apple’s own frameworks. Engines such as Unity and Unreal Engine sit above these differences, so one project can target several devices, although each target still needs its own testing and tuning.
Where does WebXR run today?
Browser support is the first thing to check, because it decides who can open your experience. The picture below is from MDN’s browser compatibility data and vendor documentation, read in November 2026.
- Chrome on Android and desktop: supported since Chrome 79. Google documents that Chrome on Android uses ARCore to power WebXR AR.
- Meta Quest Browser: supported. Meta describes WebXR as the immersive mode of its web development path, and documents passthrough mixed reality through immersive AR sessions.
- Other Chromium browsers such as Microsoft Edge and Samsung Internet: listed as following Chrome’s support.
- Safari on Apple Vision Pro: Safari 18.0 added immersive VR sessions on visionOS 2, with natural hand input and hand tracking, according to the WebKit team.
- Safari on iPhone, iPad and Mac: no WebXR support in the compatibility data. On iPhone, web AR runs through Apple’s AR Quick Look viewer instead.
- Firefox: no support listed.
MDN labels WebXR as limited availability for this reason: it does not work in some of the most widely used browsers. A WebXR project aimed at the public should therefore include a fallback, usually an ordinary 3D view that works on any screen.
WebXR or native: how do they compare?
The table compares the two options criterion by criterion.
| Criterion | WebXR | Native app |
|---|---|---|
| Getting in | Open a link or scan a QR code | Install from a store or have IT push it to the device |
| Reach | Any supported browser, with a 3D fallback for the rest | Only the devices you build and test for |
| Graphics and performance | Good, limited by browser overhead and download size | The highest the device allows |
| Device features | What the browser exposes, which varies by browser | Everything the platform offers, including the newest sensors |
| Offline use | Limited | Full |
| Updates | Instant, you change the site | A new build, and for public stores a review |
| Distribution control | Your own domain, no store approval | Store rules, or private enterprise distribution |
| Fleet management | The browser can be opened on a managed device, with less control | Can be locked, deployed and monitored through device management |
| Analytics | Standard web analytics | App analytics and deeper device data |
| Typical cost driver | Optimising assets to load fast | Supporting and testing each device |
When is WebXR the right choice?
WebXR fits when the audience is broad and the visit is short.
- Marketing campaigns and product launches where every extra step loses visitors.
- Product viewers and configurators on an e-commerce site.
- Event and exhibition activations opened from a QR code on a stand.
- Virtual tours of a venue, showroom or property that must work on phones, laptops and headsets.
- Pilots and prototypes, where you want feedback before investing in a native build.
When is a native app the right choice?
Native fits when the experience is demanding, repeated or managed.
- Training and simulation, with long sessions, precise interaction and records for each trainee.
- Games and experiences where frame rate and visual quality are the product.
- Sites with weak or no connectivity, such as plants, camps and exhibition halls with crowded networks.
- Company headsets that IT must lock to one app and update centrally.
- Features that depend on hardware the browser does not expose.
Comfort belongs on this list too. When our team rebuilt the mobile game Fananees 4 as a VR experience with MBC Group, the stated challenges were a smooth experience, high-quality visuals and minimising motion sickness triggers. That level of control over performance is the main reason headset games and training are built native.
How do you decide? Five questions
Answer these in order. The first clear answer usually settles it.
- 1. Who is the audience, and what devices do they already have? If it is the public on their own phones, start with the web. If it is employees on issued headsets, start native.
- 2. How long is a session, and how often will people return? Seconds and once points to the web. Twenty minutes and weekly points to native.
- 3. Does it have to work without a good connection? If yes, native.
- 4. Does it need device features the target browsers do not expose? Check the compatibility data for each one. If yes, native.
- 5. Who must be able to update it, and how fast? If marketing needs to change content the same day, the web is easier.
Can one project do both?
Yes, and it is often the best answer. The expensive part of an immersive project is the content: 3D models, environments, animation and interaction design. If those assets are produced in open formats and built in an engine that exports to several targets, the same content can serve a web version for reach and a native version for depth.
Our NextGen Metaverse Store follows that logic at product level. It is a VR store, and shoppers can continue the same journey from a VR headset, a TV, the web or a mobile phone. Planning for several front ends from the start costs less than rebuilding later.
How does Eurisko X approach the choice?
We build in Unity and Unreal Engine for headsets and mobile, and in WebXR with libraries such as Three.js when frictionless browser access matters more than the graphical ceiling. The first deliverable in either case is a prototype on real hardware, so comfort and performance are checked before full production.
Eurisko X is the games and immersive studio of Eurisko, founded in 2009, with more than 200 in-house staff and offices in Adma, Riyadh, Dubai and Larnaca. Eurisko has developed for Oculus Quest headsets since 2019.
Sources
- W3C, WebXR Device API, Candidate Recommendation Draft (November 2026)
- MDN Web Docs, WebXR Device API and browser compatibility data (read November 2026)
- WebKit, features in Safari 18.0, WebXR on visionOS 2 (2024)
- Meta for Developers, WebXR overview and WebXR mixed reality (read November 2026)
- Google for Developers, WebXR and ARCore (read November 2026)
- Khronos Group, OpenXR overview and conformant runtimes (read November 2026)
- Apple Developer, AR Quick Look (read November 2026)