The good thing about virtual reality is that many of the tools and features we use to build content already exist. Video games have led the way with existing engines, toolsets, and best practices.

Unfortunately, not every single piece of software is perfectly compatible with virtual reality right away. A big piece missing from any developer’s VR toolbelt is a set of powerful analytics for their experiences. Luckily, cognitiveVR is building those tools. Here are three reasons you need VR analytics for your product:

1.) Your users are getting sick.

Virtual Reality Sickness
What happens when users get sick in your VR experience? Moreover, do you know why they’re getting sick? What if you could track when they take their VR headsets off?

There are many recommendations on how to keep your users from experiencing the omnipresent condition known as virtual reality sickness. Akin to seasickness, VR sickness happens because your brain perceives motion from visual cues (i.e. your headset) while the rest of your body does not perceive any motion at all. The human body thinks you’ve been poisoned and prompts you to throw up. Yes, seriously.

Many design choices exist to try and prevent VR sickness:

  • Reduce excessive motion.
  • Reduce forced camera movement.
  • Limit the speed of your character.
  • Eliminate acceleration.

The list goes on and on, but ultimately nobody has exact parameters on what makes people sick. Why? Because getting motion sickness in VR is different for everybody.

What’s worse than making your users sick? Not knowing that you’re making them sick. Sure you could add a review option to your app or visit some Reddit threads to see what your users think, but ultimately that information is not available directly and it’s not objective. Analytics tools such as cognitiveVR’s platform will allow developers just like you to automatically collect data on precise metrics such as user sickness levels, excessive motion levels, low FPS or poor performance, fast spins, and when exactly your users are removing their headsets in (literally) disgust.

2.) You have no idea why your product isn’t doing well.

VR confusion!

Your product doesn’t work very well. You aren’t getting many downloads. Nobody is leaving reviews.

In a typical mobile game, churn is an easy thing to understand. Load up a mobile analytics solution and look at user behaviors. What action prompted users to delete your app? What A/B tests could you run? Are your advertisements prompting new downloads? Which buttons are your users avoiding?

In virtual reality, these problems are much more difficult to understand. Was it motion sickness that turned your users off? What if 95% of your users took their headsets off at some single part of your level? What if something visual in your product’s environment turned people completely off? What if you could A/B test what people are looking at in your virtual reality experience?

You can’t get concrete answers to any of these questions yet. Sure, some have hacked together other analytics offerings and pushed them to their experience, but the truth is that most developers want an easy solution that gives them a ton of power without having to worry about integrations, performance, or setup. That’s where cognitiveVR’s platform comes in.

3.) Your VR experience runs poorly (on some devices).

Virtual reality events mapping
The rise of smartphones brought the era of responsive design that all developers on the web must follow if they want their website to be viewable across many different devices. Virtual reality is no different. With a multitude of competing hardware, virtual reality experiences must be optimized across a wide range of devices.

Every virtual reality experience has to run smoothly to be successful. This ties in very closely to understanding user sickness and understanding market success.

The big problem for developers is that they have limited time to investigate and analyze how their product performs across a multitude of these different headsets and platforms.

cognitiveVR’s analytics platform solves this issue by providing in depth performance data at specific times and areas within your experience. Just imagine you see a large dropoff in user activity (people quit!) at a certain area of your game’s level. Instead of digging around, guessing, asking users, and then hoping your fix doesn’t break things across platforms, just use an analytics solution and find the problem right away.

Track what your users are looking at when performance drops. Watch which areas of your experience run poorly on certain devices. Spend your time fixing problems instead of investigating dozens of different pieces of hardware. These are all things that a VR analytics solution could do for you.

Interested in reducing these headaches? Sign up for our beta.

← Back to the blog.