VR in the Browser
VR in the browser?
If you are a developer, find out about developing VR in the browser instead.
Browsers provide a so called “API” that allows a website to access input devices and to provide visuals for output-devices. The current standard for this API is called WebXR Device API.
In December 2019 the WebXR Device API replaced the rudimentary WebVR API and besides improving upon it added support for Augumented Reality (AR), Mixed Reality (MR) and more (hence the ‘X’ as in ‘Any Reality’). Support for this API is added to more and more browsers. As of February 2021 Microsoft Edge, Google Chrome, Opera, Samsung Internet and Oculus Browser support it, and Firefox has experimental support that can be enabled with a flag. To check if your browser is WebXR ready go to https://caniuse.com/webxr.
Just like VR technology, WebXR is being actively developed. This means that there are new features being developed, tested and released. Often these features can be access long before their officially release, like hand-tracking.
To learn more about the WebXR Device API visit https://immersiveweb.dev.
Although “WebVR” is often used to say “VR in the browser” it actually is the name of the initial API, that allowed websites to offer VR experiences. However, since the release of the WebXR Device API, support has been depracted and the association of the name with the original API will vanish over time.
The VR feature for browsers is still very young and under active development and you will notice that some experiences or games don’t work in your browser or on your device. This is mostly due to experiences being developed for WebVR and not being updated. Games that are developed for WebXR should not break, but fundamental changes to the technology are not impossible. At Construct Arcade, we keep track of changes to the APIs and try to keep everything running, take advantage of new possibilities and give you the best experience that the current technology has to offer.