Jump to content

WebXR: Difference between revisions

Undo revision 35285 by Xinreality (talk)
Tag: Undo
No edit summary
Line 15: Line 15:
}}
}}


'''WebXR Device API''' (commonly known as '''WebXR''') is a [[Web API]] developed by the [[World Wide Web Consortium]] (W3C) that provides interfaces for accessing [[virtual reality]] (VR) and [[augmented reality]] (AR) devices on the web. WebXR enables developers to create immersive experiences that work across a wide range of hardware platforms, including head-mounted displays, mobile AR devices, and desktop environments with appropriate peripherals.<ref name="w3c-webxr">World Wide Web Consortium. "WebXR Device API." W3C. https://www.w3.org/TR/webxr/</ref>
'''WebXR Device API''' (commonly known as '''WebXR''') is a [[Web API]] developed by the [[World Wide Web Consortium]] (W3C) that provides interfaces for accessing [[virtual reality]] (VR) and [[augmented reality]] (AR) devices on the web. WebXR enables developers to create immersive experiences that work across a wide range of hardware platforms, including head-mounted displays, mobile AR devices, and desktop environments with appropriate peripherals.<ref name="w3c-webxr"></ref>


The API allows web applications to detect compatible VR/AR devices, query their capabilities, render 3D scenes to the devices at the appropriate frame rate, and respond to input from associated controllers. WebXR represents an evolution from the earlier [[WebVR API]], expanding the scope to include augmented reality and other immersive technologies under the "XR" (Extended Reality) umbrella.<ref name="mdn-webxr">Mozilla Developer Network. "WebXR Device API." MDN Web Docs. https://developer.mozilla.org/en-US/docs/Web/API/WebXR_Device_API</ref>
The API allows web applications to detect compatible VR/AR devices, query their capabilities, render 3D scenes to the devices at the appropriate frame rate, and respond to input from associated controllers. WebXR represents an evolution from the earlier [[WebVR API]], expanding the scope to include augmented reality and other immersive technologies under the "XR" (Extended Reality) umbrella.<ref name="mdn-webxr"></ref>


== History ==
== History ==


=== WebVR: The Predecessor ===
=== WebVR: The Predecessor ===
The development of WebXR began with its predecessor, WebVR. The WebVR API was first conceived in spring 2014 by Vladimir Vukićević from Mozilla. Key contributors to the early API included Brandon Jones from Google, Boris Smus, and other members of the Mozilla team.<ref name="webxr-wiki">Wikipedia. "WebXR." https://en.wikipedia.org/wiki/WebXR</ref>
The development of WebXR began with its predecessor, WebVR. The WebVR API was first conceived in spring 2014 by Vladimir Vukićević from Mozilla. Key contributors to the early API included Brandon Jones from Google, Boris Smus, and other members of the Mozilla team.<ref name="webxr-wiki"></ref>


On March 1, 2016, the Mozilla VR team and the Google Chrome team announced the WebVR 1.0 release. This early version of the API was implemented in Firefox and Chromium-based browsers, providing basic virtual reality functionality to web applications.
On March 1, 2016, the Mozilla VR team and the Google Chrome team announced the WebVR 1.0 release. This early version of the API was implemented in Firefox and Chromium-based browsers, providing basic virtual reality functionality to web applications.


=== Transition to WebXR ===
=== Transition to WebXR ===
As the technology evolved, developers recognized the need for a more scalable and ergonomic API that would break backward compatibility with WebVR. Initially referred to as "WebVR 2.0," the new API was officially renamed WebXR to acknowledge its expanded scope that would include both VR and AR content.<ref name="webxr-explained">Immersive Web Working Group. "WebXR Device API Explained." https://immersive-web.github.io/webxr/explainer.html</ref>
As the technology evolved, developers recognized the need for a more scalable and ergonomic API that would break backward compatibility with WebVR. Initially referred to as "WebVR 2.0," the new API was officially renamed WebXR to acknowledge its expanded scope that would include both VR and AR content.<ref name="webxr-explained"></ref>


The transition benefited from:
The transition benefited from:
Line 35: Line 35:
* Multiple mature native APIs to draw inspiration from
* Multiple mature native APIs to draw inspiration from


On September 24, 2018, the Immersive Web Working Group became official, formalizing the development process for WebXR standards.<ref name="webxr-duhoc">DuHoc. "Webxr: History, Design, Support." https://www.duhoctrungquoc.vn/wiki/en/WebXR</ref> WebXR was designed to completely replace WebVR, with all browsers that initially shipped WebVR committing to adopt WebXR once the API design was finalized.
On September 24, 2018, the Immersive Web Working Group became official, formalizing the development process for WebXR standards.<ref name="webxr-duhoc"></ref> WebXR was designed to completely replace WebVR, with all browsers that initially shipped WebVR committing to adopt WebXR once the API design was finalized.


=== Recent Developments ===
=== Recent Developments ===