Dealing with Unreliable Networks
summary
Mobile networks are slow and flaky worldwide, so the app adds concrete fixes: retry with exponential backoff reduces transient failures — measured up to a 80% drop in some markets — combined with idempotent GUIDs or server-side dedupe to avoid duplicate posts. Important actions are written to disk before send for resiliency. Performance gains come from POPs/CDN, moving SSL termination, adopting HTTP/2 prioritization and using WebP on Android (30–50% smaller) or progressive/low‑res placeholders to cut initial image render time by ~75%. A network simulator and client-side metrics prove and tune these changes.
AI-written summary · about
chapters (19)
- 0:00Intro
- 0:34Dealing with Unreliable Networks
- 1:34Reliability
- 2:46What if that network call fails?
- 4:10Android
- 6:43Resiliency
- 7:59Performance
- 8:56Points of Presence (POPs)
- 10:04HTTP/2 & SPDY
- 11:30WebP
- 13:34Progressive JPEG
- 14:54Low-res Images
- 15:46Waiting for requests
- 17:14Request Prioritization
- 21:38Network Forecasting
- 22:57Empathy
- 24:43Grey Box Times
- 25:52Network Debugging
- 27:04Network Simulation
related talks
52mPanel 2: Network
01h 14mOptimizing App Performance on Slow Networks
39mMobile Networking Challenges - Networking @Scale
14m89 characters of base-11?! Mobile networking in rural Ethiopia!
44mHTTP in a Hostile World
11mIs the Internet Reliable Yet?
35mIs your app really connected?
16m"Latency: Why You Should Worry and What You Can Do About It"
