Page Comparison

...

1. How many actually complete set-up?
   
   Utilizing Firebase: Analytics > Conversions Event to track event cadence for the app 'onboarding process' during startup (not including meta data unless opt-in).
   

2. How many turn on location data
   
   Unable to capture telemetry / instrumentation meta data without implementing ‘set user properties’
   
   firebase.analytics().setUserProperties({location_data: TRUE});
   

3. How many subscribe to an HA?
   
   Utilizing Firebase: Analytics > Conversions Event to track event cadence for the ‘subscribe to HA' (not including meta data unless opt-in)
   

4. How many open the app after they install it?  (AIUI the number who open it on day 28 is a standard KPI?)
   
   Utilizing Firebase: Analytics > Retentions to track high level ‘engagement’.
   

5. How many get an alert that they may be infected?
   
   Utilizing Firebase (FCM) Cloud / In-App Messaging: Push notifications would need to be implemented.
   

6. How many location data points does their app log (worry that there may be bugs where we fail to log)
   
   Depending on the device this calculation can be made during the export function (then passed to custom user properties).
   

7. How many infection data points do they have from HAs they are subscribed to.
   
   Unable to track this information from device (PII / GDPR)
   

8. How is performance is effected by network location (NV)
   
   Utilizing Firebase: Quality > Performance we can look at both Network Response Latency (NRL) and Device Performance (Duration Traces). Custom Traces (CPU, Memory, Device Attributes) and Data Aggregation (Network / URL).
   

9. How can we A/B test / Canary Rollout
   
   Utilizing Firebase: Audiences can be defined with a subset of user behaviors that can be flagged for rollout.

Epic / User Story

...