Instrument the app for collecting usage analytics

[eecavanna]

The task here is to make it so that NMDC team members can see app usage analytics; specifically, the number of installations and uninstallations, and the number of crashes (and some actionable info about them).

Some options

Apple (for iOS only)

Apple provides some analytics: https://developer.apple.com/app-store-connect/analytics/

Available in App Store Connect, these tools are included with Apple Developer Program membership and require no technical implementation.

App engagement and usage: Measure a variety of user engagement metrics, find out if people continue to use your app, and view the number of installations, sessions, and active devices. This information allows you to evaluate the impact of product changes, such as adjustments to the onboarding experience or the addition of special in-app content. View crash and deletion data by platform, app version, and operating system version to pinpoint potential causes and create a better user experience.

In-app event performance: View information about your in-app events, including event page views, reminder and notification data, and the number of downloads and redownloads that were driven by your in-app events. Each metric can be viewed by territory, source type, device, and more, so you can understand how your in-app events are influencing the growth and success of your apps.

Google Analytics for Firebase (for iOS and Android and maybe also PWA)

Google Analytics for Firebase: https://firebase.google.com/products/analytics

Google Analytics (for iOS, Android, and PWA)

Google Analytics: https://support.google.com/analytics/answer/9304153?hl=en

NMDC already uses Google Analytics for some things (e.g. website, data portal).

Discover how to set up Google Analytics for your website or app by creating a Google Analytics 4 property, adding a data stream, and adding your Google Analytics code.

[eecavanna]

Now that I have access to the other Lab-managed Apple Developer Account, I can see app analytics for existing apps (unrelated to ours), for example/reference. The are in a section of App Store Connect called "App Analytics". I posted some example screenshots on Slack.

[emileyfadrosh]

Following our discussion yesterday about metrics, here are a couple ideas I had about metrics and usage. Thanks @pkalita-lbl @eecavanna

Prior to a full release of Field Notes, it would be useful to understand how beta-testers are using the app for their research. This would include:

1. Whether researchers set up their study prior to the sampling campaign, and if so, whether they enter into the Submission Portal (or app) basic information about the samples they plan to collect. Figuring out a way to capture this pre-sampling usage of both the app and Submission Portal could help with future development.
2. During sampling, having a way to identify how users are capturing their samples and the relevant information. For example, do users mostly take a sample and only add lat/long and sampling date, or do they add more metadata fields? Similarly, do users go back to the app immediately following their sampling or wait to fill in other metadata (or go straight to the Submission Portal)?
3. Tracking usage based on MIxS package used: are there differences in how researchers collect say water samples compared to soil samples?
4. Ability to track information about multiple users contributing to a single study. Are there different researchers responsible for entering data in the app (or Submission Portal) during or after the sampling campaign? Understanding how research teams interact with the app would help us streamline features.
5. Lastly, tracking information for multiple sampling campaigns and repeat users over time could help us understand what's working and what's not (in addition to whatever user research approach will be used for follow up).

[pkalita-lbl]

Thanks @emileyfadrosh. Much to consider here!