Virtual-reality already works on websites.
Anyone who owns a modern smartphone can have a virtual-reality experience on the web today. And if you are a web developer, there’s nothing stopping you from building a working virtual-reality experience as a weekend hack project.
When I learned this a couple weeks ago, it kind of blew my mind. Modern virtual reality is very new, and web specifications and browser APIs take time to implement. Yet here it is.
But let me take a step back and talk about what “it” is.
What it looks like
For me, web-based virtual-reality conjured up visions of 3D web pages with nav-bars floating above my head, and hyperlinks teleporting me across websites, as if between worlds.
That’s not how it works.
Web Virtual-Reality (or WebVR) allows developers to build contained VR experiences. When WebGL support was added to browsers, it didn’t magically make all websites look like they were rendered in 3 dimensions, but it did allow developers to build and embed specific 3D renderings based on existing technologies (like the 2d canvas). WebVR is similar. Today’s implementations of WebVR are based on the same technologies that power WebGL. That means that any browsers or devices that support WebGL (like modern smartphones) can be used to build and test WebVR today.
This is what a WebVR scene looks like in a supported browser:
Even without those, you can get a blurry (but working) taste of it by pulling up a scene like this on your phone, orienting it landscape, bringing it in front of your eyes, and working to resolve it into a single image, like a magic eye poster.
Most WebVR demos allow you to navigate the environment with some combination of WASD controls, your mouse, or tilting your device to look 360 degrees around you. Check out these cool demos if you want to see what people have made.
How the technology works
A-frame renders 3D scenes onto the Canvas element using WebGL. It’s built on the mature and popular Threejs, a library that makes it easier to build 3D scenes and geometries, primarily for WebGL. Interestingly, A-frame does this by defining a library of custom elements used to build scenes declaratively. It almost looks like a new markup language:
<a-scene> <a-sphere position="0 1.25 -1" radius="1.25" color="#EF2D5E"></a-sphere> <a-box position="-1 0.5 1" rotation="0 45 0" width="1" height="1" depth="1" color="#4CC3D9"></a-box> <a-cylinder position="1 0.75 1" radius="0.5" height="1.5" color="#FFC65D"></a-cylinder> <a-plane rotation="-90 0 0" width="4" height="4" color="#7BC8A4"></a-plane> <a-sky color="#ECECEC"></a-sky> </a-scene>
So, If you’re interested in trying out WebVR, definitely check out A-frame, and maybe join their Slack community. Taking a week to learn about this has been fun and I’m interested to see where it goes in the future.