Enables the team to test the implementation status of current sprint features (Sept 16–29). Requires implementation of the items listed on the tracking doc.
Script:
[ ] User loads URL on desktop or mobile device
Starting page presents:
[x] A 360° pano (image or video) in the background
[ ] A 3D model at their feet
[ ] A logo and labels with the brand and instructional information
[ ] The links change color and play sound effects when looked at
[ ] The links are triggered when the user presses a button (if on desktop), or holds their gaze (on mobile device in VR model)
[x] When triggered, the links change the scene
[x] A new pano in the background
[ ] New labels, which animate in
[ ] Hot spots. These expand and display additional information when hovered over, and trigger changes in the scene (eg voice over sequence) when clicked.
[x] The links remain visible on all scenes (like a consistent menu)
[ ] Some scenes use 360° video. For those, the user has controls available to pause/play.
On desktop
[ ] The experience presents in mono mode w/ mouse look by default.
[ ] 2D DOM overlays instruct the user on how to use the scene
[x] "Enter VR" buttons enter VR mode if the user has a compatible browser + SDK + detected headset.
[ ] If the user does not have any of the prereqs to enter VR mode, the "Enter VR" button presents instructions on what is required.
[ ] VR mode works on Firefox Nightly w/ Add-on, or VR-enabled Chromium.
On mobile
[ ] The experience works in mono mode w/ accelerator look by default.
[ ] 2D DOM overlays explain how to user on how to use the scene
[ ] "Enter VR" button enters Stereo mode, hides 2D DOM overlays, and hides toolbars.
Issue by jcarpenter Thursday Sep 17, 2015 at 19:06 GMT Originally opened as https://github.com/aframevr/aframe-core/issues/154
Enables the team to test the implementation status of current sprint features (Sept 16–29). Requires implementation of the items listed on the tracking doc.
Script: