RE: New Year VR Question

Leonard, I think you must do user testing rather than asking opinions through email.

Here’s my take (which I’m not too proud of)

My understanding was that you entered stereographic display and then started your app (a web browser). Is there an additional setting in the web browser beyond stereographic display—can you detect 2 displays?

My memory of cardboard mode is very dim. It may even be a dream. I am trying to get some clarification.

If there are two displays and no WebVR available, then I would have a confirm dialog (yes/no) whether someone wants to enter VR.

If there’s only no or one display, I would set a cookie to the fallback option chosen (I’m assuming your app is heavily VR), and then proceed to do the fallback option.   Later, confirm the number of displays and provide a (yes/no) dialog to go through the fallback options, if the number of displays change.  If the number of displays stays the same, then mere have one confirm dialog confirming the cookie.  If they say no, then proceed to fallback options.   Provide one option to exit the application.

That’s the best I can think of without some serious UX testing and more systematic thinking—Perhaps you can find some UX testing research online?

Answer this question: what do YOU prefer?  If you’re ambivalent or jaded, present several alternate designs to someone fresh and get their feedback.  Provide the options in a mixed app environment (normal phone or device use).   Try to measure how surprised the user is or how natural the interface is for a person to navigate.

If something irks you, try something else.

Lastly, emulate someone else’s Look&Feel.  It’s best to get consistency.

If you’re trying to come up with a standard, especially do user testing of alternatives.

John

Sent from Mail for Windows 10

From: Leonard Daly
Sent: Monday, January 1, 2018 2:49 PM
To: John Carlson
Subject: Re: New Year VR Question

On 1/1/2018 11:11 AM, John Carlson wrote:
I'm recalling some kind of confirmation that you are using cardboard while you are enabling cardboard.

None that I have ever encountered. It is necessary to get into a stereographic display, but cardboard is not required for that. I have done that  with X3DOM and XSeen (THREE.js).

Leonard Daly






On Jan 1, 2018 2:07 PM, "John Carlson" <yottzumm@gmail.com> wrote:
Leonard, before I answer your question, do you have experience with Cardboard setup? As I recall, it's difficult to get a cardboard display without a cardboard device, so you may be able to detect the device.   It's worth seeing the capability of the hardware before making software changes.   If capabilities are exposed to the browser, you may be able to leverage them.

John

On Jan 1, 2018 1:58 PM, "Leonard Daly" <web3d@realism.com> wrote:
Happy New Year Everyone!
I have been real quiet these couple of months working on a variety of projects. Part of that time has been thinking about handling Declarative VR in the browser. In particular what should happen when the web page requests a VR display, but the device is not VR capable. For example in a modified version of the THREE boxes example (see ) a button is put on the bottom of the display allowing the display to go into VR mode (if possible) or indicating that a VR device is not available.
The user may have a phone with only cardboard. Cardboard is not considered a VR device (at least in context of WebVR). It is still possible to get a VR experience. 
If a programming environment such as THREE, that can be detected and other options offered. In a strictly declarative environment, that capability is not available. Should a Declarative VR language 
1. automatically roll-over to a stereographic display
2. provide an ordered list of fallback options 
3. only do exactly what is requested (no VR device ==> no VR display)
Note that (3) is not necessary exclusive of (2).
If (2) is the desired capability, then how is that best represented - as an attribute list ("option1, option2, ..."), a single fallback attribute, an ordered list of children tags?

-- 
Leonard Daly
3D Systems Architect & Cloud Consultant
President, Daly Realism - Creating the Future 


-- 
Leonard Daly
3D Systems Architect & Cloud Consultant
President, Daly Realism - Creating the Future