Moving Web applications into Virtual Reality
summary
Claim: web UIs can become first-class VR content by rendering DOM/CSS as GPU textures instead of flat iframes. Demonstrations use WebGL shaders for lens distortion and chromatic aberration, a wrapper called HTMLGL v2 that is roughly ten times faster, and stress tests like 25,000 animated GIFs hitting about 45 FPS. Built demos include a 3D carousel, reflected HTML surfaces and a ported calculator; approach works but requires shader-driven rendering for optical corrections and high performance.
AI-written summary · about
chapters (21)
- 0:00VR web app migration intro
- 1:56Why move web apps to VR
- 4:11Flat web apps in VR challenges
- 5:15How VR works technically
- 7:35CSS/HTML in VR environments
- 9:47CSS 3D/iframes limits for VR
- 11:37WebVR API benefits
- 13:46JS optimization lessons
- 16:41GPU rendering power
- 18:29Why WebGL is hard
- 19:44HTML GL for WebGL rendering
- 22:44HTML GL evolution in VR
- 23:46Live demo HTML GL v2
- 25:48Advanced HTML GL effects
- 27:15HTML in 3D worlds
- 28:41HTML GL to textures
- 29:45VR subdomains & enhancement
- 30:59A-Frame for VR scenes
- 32:07React VR & alternatives
- 33:47A-Frame & React VR code
- 34:53Q&A on VR gear & interactions
related talks
44mPorting an Existing Web App to Virtual Reality
45mThe visual web of today and tomorrow - WebGL and WebVR.
49mPorting an Existing Web Application to Virtual Reality
36mJavaScript for Virtual Reality
01h 08mThe quest for the graphical web
36mImmersion in the Browser - Building the VR Web
53mVirtual reality for web developers
42mCreating virtual worlds in the browser
