Product Event Tracking Overhaul

Shipped

• Introduced a centralized product-event layer so important actions are measured consistently
• Replaced scattered tracking calls across the app with consistent tracking methods
• Expanded event coverage for:
  • Onboarding actions and state transitions
  • Workout sessions (start/resume/finish, key interactions)
  • Routine management (activation, edits, deletes, preset flows)
• Removed legacy event tracking utilities and added safer fallback behavior when measurement is unavailable
• Updated documentation to reflect the new product-event approach and usage patterns

Why

• Consistent product signals are the foundation for evidence-based iteration: activation, retention, and training habit loops.
• Centralization prevents analytics drift where different parts of the app log events differently
• Safe fallback behavior keeps local testing reliable without breaking product flows

Notes

• This is a foundations release: it does not change user-facing features directly, but it improves visibility into what is working and what is not.

Next

• Define a minimal event taxonomy for the most important product actions
• Add a small local review panel for event quality during QA
• Start tracking the beta funnel: landing -> request access -> onboarding complete -> first workout completed -> week-2 return