Shipped
- Introduced a centralized analytics module to standardize event tracking via PostHog
- 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 fallback logging when PostHog isn’t configured
- Updated documentation to reflect the new analytics approach and usage patterns
Why
- Consistent instrumentation is the foundation for evidence-based iteration (activation, retention, habit loop)
- Centralization prevents “analytics drift” where different parts of the app log events differently
- Fallback logging keeps dev/staging environments usable without breaking flows when PostHog keys aren’t present
Notes
- This is an infrastructure release: it doesn’t change user-facing features directly, but it improves visibility into what’s working and what’s not.
Next
- Define a minimal canonical event taxonomy (P0 events only) and enforce naming consistency
- Add a tiny “debug panel” toggle to view recent events locally during QA
- Start tracking the beta funnel: landing → request access → onboarding complete → first workout completed → week-2 return