Hacker News new | ask | show | jobs
by Pfhreak 3468 days ago
I don't understand the intent here. What am I building that's a browser VR experience? That's as foreign to me as saying a browser cooking experience. Those are words, but I just don't understand how they'd operate together in a way that would be enjoyable and easy to use.
6 comments

VR videos, VR videogames, VR [insert other here].

Being able to watch a 360 degree video in the browser. Optionally hit a button and put on a headset and use head tracking to look instead of click+drag.

Playing VR games using something like daydream, oculus, etc... All within the browser.

The idea being it keeps the same cross-platform, cross-device, cross-"viewer" (VR headset, phone screen, computer screen, KB+mouse, touchscreen, etc...) that the web is built on.

You probably won't be making the next AAA title in the browser just yet, but it's more than capable of games, videos, and other VR "experiences".

It's a virtual reality experience that runs in the browser. These experiences can be anything: games, tools, entertainment. Mostly anything that a native VR experience can provide (given the limits of Web APIs).

The benefit to having this content in the Web are:

- Open ecosystem

- No gatekeepers or app stores

- No downloads / installs

- Link traversal (hop from one VR experience to another without having to change "apps")

- Instant publish (throw up a site without a review process)

- Instant sharing (Tweet a link to a VR site)

- More accessible for content creators or web developers (HTML, JS)

- Larger audience: no one is going to download a VR app for your small store, but they would more likely click a link on a web page to open it

- Easier to do cross-platform content

Currently there's dozens if not hundreds of VR experiences, apps, games etc but they all live in silos. You launch an exe or whatever then you're done.

It's as if every website needed a downloadable exe and there were no such things as hyperlinks between websites.

WebVR opens up the possibility of navigating between apps, building sites that curate or embed apps - all the richness that distinguishes the web from silo'ed apps.

VR really suits the idea of 'browsing' so making it part of the web is extremely natural.

When you have a VR headset plugged to your computer, navigating to the urls with WebVR compatible code will add an extra button. Clicking on the button will display a scene inside your VR Headset. This scene can be interactive (using the remote control). It can be a full game, a video, anything...exactly like any experience you can download on Steam.
I think it simply means that the runtime and distribution platform are the typical browser technologies stack, namely JavaScript, HTTP, et al.
Here is a great list of examples: https://mozvr.com/#showcase