DS - Spike - Investigate a global system for component analytics

[TimRoe]

Description

As part of building the design system components and observing their implementation, it was noted that it seems necessary for apps to create component wrappers for many components if only for simply passing through analytic events more easily. This is a recurring implementation hurdle to being able to seamlessly directly leverage components straight from the library. As such, this spike has been created to consider if there's an alternative method by essentially creating an analytics service that can be instantiated globally by an app and serve to handle analytics events for all design system components. Such a system must be able to handle both global events (e.g. same analytic event on all instances of the component) and ones with local context (e.g. knowing specific screen).

Narin and I discussed via Slack DM (full discussion below) and he suggested it could potentially lean on the global settings spike #256 ideas (or implemented version depending on when this is picked up).

Acceptance Criteria

• Investigate options for creating an analytics service for design system components that could ease consuming apps from needing to routinely create wrappers to our components solely for passing analytic events
• Create a basic proof of concept validating it could be used for both global and localized analytics
• Evaluate if the determined solution seems simple enough to be beneficial for both the design system and consumers long term or the frequent need for app-level wrappers for analytics is optimal, if annoying
  • If it doesn't seem to make sense, document determination and proof of concept for posterity in case the situation changes in the future

Notes & Open Questions

Dev Notes:

• Spike - Explore ability for consumers to set global values for components #256
• DM discussion w/ Narin: