JS in the Virtual & Augmented Reality Ecosystem
summary
Overview of what actually runs today: WebXR lands in Chrome 79 ships WebXR unflagged, so standard WebXR pages can run without hacks; before that many demos rely on custom browsers (WebARonARKit / WebARonARCore) or Mozilla’s WebXR Viewer to access AR APIs. Production-ready libraries are usable now — three.js, A-Frame, AR.js, model-viewer, TensorFlow.js — enabling markerless and marker-based AR, 3D model preview, and on-device pose/body meshes; prototypes and exports via Torch → Eighth Wall demonstrate web AR running in normal mobile Safari/Chrome.
AI-written summary · about
chapters (11)
- 0:00Start
- 2:03What do we mean by WebXR?
- 3:522. JS & AR Today
- 4:19WebARonARKit/Core
- 5:23WebXR Viewer
- 7:45A-Frame
- 9:17On the web today
- 12:33Torch & 8th Wall
- 13:43Magic Leap on Glitch (announced Tuesday, December 10th, 2020)
- 14:33ImmersiveWeb.dev
- 15:12Browser support
related talks
30mThe future of Virtual and Augmented Reality for the web
30mWebXR : augmented reality lands into our web browsers
23mBuilding Engaging Immersive Experiences
27mState of WebXR: What do You Need to Know Today?
17mThe Immersive Web in 2019
33mWebXR? Native virtual and augmented reality in browsers
32mWriting Virtual and Augmented Reality Apps with Web Technology
26mExploring Augmented Reality on the Web