This document discusses developer tools for analyzing virtual reality (VR) experiences. It notes that directing users is harder in VR than traditional media since VR is consumed actively. It outlines a three step process for VR analytics: 1) gather data on user behaviors and characteristics, 2) visualize VR sessions to see what users are doing, and 3) go beyond quantitative data to qualitative insights by seeing sessions from the user's perspective and identifying comfort issues. It introduces a new tool that provides quantitative, visual, and qualitative analytics with a single API call to help developers better understand user experiences.

1. Analytics Backed Developer Tools for VR
Robert Merki
Director of Product

2. Traditional media:
Consumed passively.
Directing users is pretty easy.

3. Virtual Reality:
Consumed actively.
Directing users is hard.

4. VR Analytics
Step 1: Gather Data

5. Where (
user height < 190,
comfort level > 0.95,
vr headset = “HTC Vive”
)
{
Show( Average Session Length );
}
Run Query
Step 1: Gather Data

6. “But what are my users actually doing?”
Going beyond data:

7. Analytics for immersive
content needs to be
visual to tell the whole
story.

8. VR Analytics SceneExplorer
Step 2: Visualize VR Sessions

9. SceneExplorer

10. Third Person First Person

11. Complete visualizations of VR sessions

12. But what are my users thinking?

14. Step 3

15. Step 3

16. NEW THESIS:
One API call, full suite of analysis tools
cognitiveVR.Event(“Comfort Issue”)
.setProperty(”FPS”, 41);
Quantitative

17. NEW THESIS:
One API call, full suite of analysis tools
cognitiveVR.Event(“Comfort Issue”)
.setProperty(”FPS”, 41);
Quantitative
Visual

18. NEW THESIS:
One API call, full suite of analysis tools
cognitiveVR.Event(“Comfort Issue”)
.setProperty(”FPS”, 41);
Quantitative
Visual
Qualitative

20. cognitiveVR.co
Q&A