“How’s the App Doing?” Bringing Mobile Into Your Reliability Picture
summary
Argues that server-side SLOs miss a huge slice of failures unless apps send user-centric telemetry and shows concrete gaps: requests stuck in client queues, crashes before send, response deserialization delays, and device/network heterogeneity. Recommends instrumenting mobile with OpenTelemetry (example: Embrace), correlating app traces with backend logs, and building SLOs measured in seconds of user wait. Gives concrete surprises: a 15 minutes fix vs 15 days rollout reality, and that users measure latency in seconds not milliseconds.
AI-written summary · about
chapters (11)
- 0:00Mobile reliability intro
- 1:00User experience matters
- 3:10Mobile app failures overview
- 5:21Client-side issues beyond backend visibility
- 8:33Mobile runtime challenges
- 10:40User expectations vs performance
- 11:25Cost of hidden mobile issues
- 12:28Mobile observability setup
- 13:53Why mobile observability is new
- 15:19Integrating mobile telemetry
- 16:25Mobile observability takeaway
related talks
28mMobile Application Performance Done The Right Way
18mThe Last Inch Problem in Mobile Observability
26mUsing OpenTelemetry to Improve Service Level Objectives
45mMobile App Reliability: What It Is and How to Achieve It
35mMobile Observability at scale
19mOops my app performance sucks... what if observability could be a game changer?
18mOpenTelemetry for Mobile Apps: Challenges and Opportunities in Data Mob...
21mMonitoring Your Apps is not About Devops