⚙️ Technical Change
Title
Add Crash Reporting & Production Observability Before Store Submission
Type
technical-change
Problem
The app is on release/1.0.0-store-submission but has zero crash reporting or analytics. Any failure users hit post-launch will be completely invisible — no stack traces, no breadcrumbs, no way to reproduce or triage issues. This is the single biggest gap between "demo app" and "production app."
Solution
Integrate a lightweight crash reporting SDK (e.g., Sentry or Crashlytics via expect/actual) with KMP-compatible initialization. Capture unhandled exceptions on both platforms, attach offline-sync state context, and wire up a release-health dashboard. Add opt-in analytics for critical flows: event creation, poll voting, and sync reconciliation.
Why Now
Shipping to stores without crash reporting means flying blind on day one — every production issue becomes a frustrated review instead of a traceable ticket.
Context
Suggested by Power User (Dev) during round table
Proposal #8 · Created: 2026-04-15T20:29:47.685Z · By: user-power
⚙️ Technical Change
Title
Add Crash Reporting & Production Observability Before Store Submission
Type
technical-change
Problem
The app is on
release/1.0.0-store-submissionbut has zero crash reporting or analytics. Any failure users hit post-launch will be completely invisible — no stack traces, no breadcrumbs, no way to reproduce or triage issues. This is the single biggest gap between "demo app" and "production app."Solution
Integrate a lightweight crash reporting SDK (e.g., Sentry or Crashlytics via expect/actual) with KMP-compatible initialization. Capture unhandled exceptions on both platforms, attach offline-sync state context, and wire up a release-health dashboard. Add opt-in analytics for critical flows: event creation, poll voting, and sync reconciliation.
Why Now
Shipping to stores without crash reporting means flying blind on day one — every production issue becomes a frustrated review instead of a traceable ticket.
Context
Suggested by Power User (Dev) during round table
Proposal #8 · Created: 2026-04-15T20:29:47.685Z · By: user-power