WebVR development continues to happen at a fever pace. And while much of the work has been around refining aspects of the API that define how content is rendered into headsets and managing input devices, one of the most exciting recent developments is the added ability to navigate between WebVR experiences.
The story of the Web is really the story of the hyperlink. Without the hyperlink, the Web would not exist. The elemental piece that allows for web pages to link from one to another. Enabling users to move from one interest to the next in a organic and exploratory fashion. It’s how you end up eyeballs deep in some arcane subject that you never knew you were interested in — often way too late into the evening, when you should be sound asleep. It’s why we enjoy the Web.
This is exciting stuff! WebVR content will no longer have to exist as their own siloed experiences and expand into larger interconnected experiences.
In this article, we’ll dig into how this navigation behavior works and see a basic working example.
It’s still super early
Make no mistake; we’re still in the very early stages of what this will look like. The specification accounts for only the mechanical aspects of how you move from one experience to the next. So no markup or blue underlined text or outlines just yet, nor have we finalized how the interaction model will work.
For now, this leaves WebVR content to freely express what a link looks like and how users interact with them. But, more about that later.
Link traversal experience
View demo!
View source code on GitHub
,
Source: Mozvr