[webvr] Why does entering VR need to be on user interaction?
pyalot at gmail.com
Wed Sep 21 16:27:03 UTC 2016
It's not that easy.
Aparts from the obvious development difficulty of making a browser do a VR
SteamVR has some flavor of "VR shell" which shows you some SteamVR tiles
and tiles with your applications. There's also several "VR Desktops" which
work like a VR window manager. GearVR has a VR shell of its own. In
addition, GearVR's browser also has a "tab display mode" inside of its VR
shell. Oculus might add a VR shell to the oculus home themselves. Then
there's the likelihood that in the near future, some or other OS will start
offering native VR shells.
As an application maker, you'll want to avoid expending a lot of effort on
something just for your usecase, that a variety of people are already
trying to solve. But no clear solution to this has crystallized yet. But
when it does crystallize, it'll likely mean you can throw whatever you did
away and start over from scratch.
On Wed, Sep 21, 2016 at 6:09 PM, Stephen White <steve at adam.com.au> wrote:
> On 22 Sep 2016, at 1:02 AM, Brandon Jones <bajones at google.com> wrote:
> > What are some examples of user experiences that are made impossible (or
> at least less feasible) because of the gesture requirement?
> I’m reluctant to enter this debate as I’m worn out from the last one, so
> here’s the one opinion I’ll give and that’s it.
> If I’m wearing a VR headset connected to a web browser, I should always be
> in VR even if the browser needs to draw a room and a monitor in front of me.
> The web page can appear on the monitor, or it can take over the room with
> the gesture granting permission.
> steve at adam.com.au
> web-vr-discuss mailing list
> web-vr-discuss at mozilla.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the web-vr-discuss