Solved

Instrument a component library?

  • 31 March 2023
  • 3 replies
  • 99 views
C
Rank
Userlevel 2
Badge +1

Has anyone used Amplitude to instrument a component library to measure developer's use of the library and components? We’re planning to instrument our Storybook and in theory it seems like it would be great, I’m just curious if anyone has uncovered any traps/pitfalls with this before.

icon

Best answer by Jeremie Gluckman 4 April 2023, 23:41

View original

3 replies

Jeremie Gluckman
Rank
Userlevel 6
Badge +9

Thanks for posting here @CCrowley and excuse the delay. Here are some potential pitfalls to keep in mind: 

  • Respecting user privacy and being transparent about what data you’re collecting
  • Ensuring data quality and filtering out any events that don’t represent real user behavior
  • Selecting the right metrics that provide actionable insights 
  • Not over-instrumenting with irrelevant events or properties; keep your implementation simple

I hope this helps! 

C
Rank
Userlevel 2
Badge +1

Thanks, @Jeremie Gluckman! I think your list can apply to any use of Amplitude Analytics. I was looking more specifically for ways a component library may differ from other applications. But your points are all valid and important to remember.

 

Thank you!

Jeremie Gluckman
Rank
Userlevel 6
Badge +9

Thanks for the feedback @CCrowley. Please let us know if you need anything else!

Reply


Terms & ConditionsCookie settings