googlevr / gvr-android-sdk

Google VR SDK for Android
http://developers.google.com/vr/android/
Other
3.28k stars 1.28k forks source link

Headset Selection UX Issue for users without Daydream #557

Open VR-Nima opened 6 years ago

VR-Nima commented 6 years ago

Users with Daydream-compatible devices always have the ability to switch to the Daydream View headsets through the Gear Icon Menu through the Google VR SDK. If a user selects the headset(whether to try with a friend’s device or just because they’re curious to see what it will do) they will receive an error asking them to download and install Daydream before continuing use, with no way to access the Gear icon to change back to a Google Cardboard headset.

In addition, to get to the screen in the Daydream app that allows you to change headsets, the user is required to enter their credit card information. This poses a problem for us as WITHIN is free and users following the standard flow that Google VR presents inside our app may feel as though content they’ve been using that was free now requires a credit card to continue to use.

The only workaround we’ve found is for the user to download the Google Cardboard app and make the headset change there, but this is not intuitive and isn't documented or communicated to the user in any way through the Google VR SDK.

We’ve thought of a couple of solutions:

  1. Developers are given the ability to change headset profiles programmatically(we do not prefer this, as the onus is on developers to create a custom UX solve in their apps).

  2. Headset profile selection becomes a core part of Android Settings, and users are instructed to go to Settings to change headsets back. In addition, these settings could potentially be hidden until after a Google VR SDK app is downloaded, or become a default setting of all Android devices with Gyroscopes to promote virtual reality usage. In addition, this would allow users to globally change their headset selection without needing to do so from an app.

jdduke commented 6 years ago

Hi @VR-Nima, you're right that this particularly scenario yields suboptimal UX. We'll look into improving this to avoid users getting stuck.