Lessons from Mobile
summary
Facebook reports over a billion users and ~800 million on mobile, and measures show its apps eat ~20% of users’ mobile time. Engineering uses a four-week train (four weeks stabilize, release every four weeks) and an Android beta (1M+ users) to catch device-specific crashes — one photo-compression bug appears only on ~10 devices tied to a CPU and is mitigated by a server-side switch until the next train. Navigation changes run as tab-bar A/B tests 1–5% (millions) and a subtle WebP 20% size reduction cuts global data costs.
AI-written summary · about
chapters (18)
- 0:00Introduction
- 4:00Our History
- 11:24The Tab Bar
- 18:18Challenges
- 22:26Lesson Learned
- 23:16How long to run a test
- 24:28Android Beta
- 25:16Android Frameworks
- 26:21iOS 7 surprises
- 27:59Device testing
- 28:46Serverside switches
- 29:40Android upgrades
- 33:11Network and battery
- 35:36HTML5 vs native
- 38:13Usability testing
- 39:06Power
- 40:25Mic Runners
- 40:40Chat Heads
