Collect anonymous analytics to guide UI improvements

[kfarr]

I'm curious how people are using City Builder. It's been featured as an example project on aframe.io but I'm not clear how many people are actually making cities. Looking at some of them via firebase I see a lot of the cities are gibberish or identical copies of others. (A separate ticket is here for browsing existing cities: https://github.com/kfarr/aframe-city-builder/issues/18).

I'd like to track a "funnel" of how users are actually interacting with city builder. Some questions I'd like to answer:

• How many people ( what %) are using webvr compatible devices? Accessing via mobile?
• How many people actually click "enter vr" button?
• How many people place at least 1 object? Save or Save As a city?

Using this data, I'd like to be able to improve the UI with the primary goal of encouraging as many people as possible to create or modify a city (save or saveAs with unique city contents).

I've used a couple different web analytics suites before and I really like the funnel view provided by amplitude, but others like keen.io or mixpanel would work too.

Amplitude's javascript sdk is very simple, for example: amplitude.getInstance().logEvent('EVENT_NAME_HERE');

Some key events to instrument, prioritized from highest:

• "Enter VR"
• "Place Object", properties 'file', 'position', 'rotation', 'scale', 'id'
• "Save" - property 'name': city name
• "Save As", - property 'name': city name
• "Exit VR"

Some questions:

• Can we identify which VR device is being used (vive, rift, daydream, gearvr, etc?)

[kfarr]

Can maybe offer opt out toggle in ui: amplitude.getInstance().setOptOut(true);

[kfarr]

Other events:

• "Loaded Amplitude", property 'location'
• "Loaded A-Frame Scene" (A-Frame "loaded" function)
• "Loaded City", property 'name' city name
• "Hide Dialog" (not implemented)