Practical aspects of crash reporting, analytics and connectivity
summary
Describes crash reporting, analytics and connectivity used on a real PulseOn optical heart-rate product: uses CoffeeCatch for POSIX-level crash capture that writes stack dumps to flash and store-and-relay on next startup, wraps Google Analytics via the Measurement Protocol over HTTPS (no SDK) with local buffering and circular storage for offline uploads, and handles Bluetooth SPP/LE plus SPI/I2C. Live deployment reveals surprising demographics — ~70% male, median age 43 and more iOS than Android — and the approach proves reliable in the field.
AI-written summary · about
chapters (8)
- 0:00Introduction to connected devices
- 1:18Connected device constraints
- 8:38Crash reporting strategies
- 13:06The store-and-relay approach
- 17:35Hybrid code and debugging
- 20:41Monitoring and diagnostics
- 25:50Analytics and user privacy
- 32:02Practical analytics implementation
related talks
22mBuilding a movement data and analytics platform to de-stress customers & save lives
44mEfficient Android app monitoring
29mCrash-reporting taken to next-level
26mObservability of your app in production
30miOS Observability & Performance Metrics
27mBuilding Observability into Your iOS App Platform
01h 19mHow Code Fails in the Real World
17mVitals: Past, present & future