Intent to Experiment: Origin Trial: WebXR Device API
Sam Drazin
Contact emails
baj...@chromium.org, bte...@chromium.org, samd...@chromium.org, ddo...@chromium.org, johnp...@chromium.org
Spec
WebXR Device API: https://immersive-web.github.io/webxr/(explainer)
Summary
We are shipping the core WebXR Device API, which is essentially at parity with WebVR, as an origin trial; there will be no AR capabilities at this time. We would like to get feedback on updates to the core API, as well as the addition of Gamepad capabilities over the M76-77 timeframe.
Background
An Origin Trial for WebVR was originally launched in Chrome 56, and renewed for M59-M61 (and again for M62-64) with changes based on feedback and the long term spec direction. The results of that experiment to date have been reported and we feel it's been a productive experience that has proven popular with developers.
Since then, the spec and API have evolved, with improvements and changes to several core areas of the API (including coordinate spaces/tracking, privacy, and general API shape). In addition, the Gamepad API has been formally added to WebXR.
Link to “Intent to Implement” blink-dev discussion
https://groups.google.com/a/chromium.org/d/topic/blink-dev/XMLgC_SR0dw/discussion
Note: The “Revised WebVR API” (aka WebVR 2.0) referenced in that thread was renamed WebXR Device API several months later.
Goals for experimentation
Get feedback on API updates since previous WebXR origin trial, including:
Overall API shape
Input: general feedback on integration of the Gamepad API
Spatial tracking: clarity and intuitiveness of current spec & API choices
We will send a questionnaire to participating developers, as well as track metrics related to the usage of the API to collect feedback from this origin trial.
Experimental timeline
Enabled :
30 MAY 2019 : Chrome 76 branch to Dev
25 JUL 2019 : Chrome 77 branch to Dev
30 JUL 2019 : Chrome 76 Stable Release*
10 SEP 2019 : Chrome 77 Stable Release*
Disabled :
05 SEP 2019 : Chrome 78 branch to Dev
22 OCT 2019 : Chrome 78 Stable Release*
*Stable dates are estimates: https://chromiumdash.appspot.com/schedule.
Any risks when the experiment finishes?
Unless the API transitions to stable, sites will lose the ability to interact with VR hardware. Given that hardware availability is limited, we are encouraging developers to write responsive content that can account for its absence, but anything that relies on VR features would stop working.
Ongoing technical constraints
None
Will this feature be supported on all five Blink platforms supported by Origin Trials (Windows, Mac, Linux, Chrome OS, and Android)?
Yes, the API and inline sessions will be available on all platforms. Support for head-mounted displays and thus true VR depends on platform support. Currently, Chrome supports Android and Windows. Poses for inline sessions also depends on access to sensors, and support is currently limited to Android.
Link to entry on the feature dashboard
Chris Harrelson
--
You received this message because you are subscribed to the Google Groups "blink-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to blink-dev+...@chromium.org.
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAD_pDDnk-E%2BMagbSXL27vbgHxomhGFaz4K6jGJPrS0hZ9nXnYw%40mail.gmail.com.