Balancing Speed and Reliability- The Double-Edged Sword of Third-Party Libraries
summary
An April 2020 Google Maps update causes widespread crashes, leaving millions of users blocked and costing tens of millions of dollars while teams deploy hotfixes that delete cached files and roll out Uber Maps as an emergency fallback. The company hardens library governance, mandates feature flags and delayed initialization, sandboxes Play Services in dynamic feature modules, uses lint bans, jar shading only as last resort, and builds an automated startup recovery called Black Swan recovery engine plus push and DNS‑based mitigations.
AI-written summary · about
chapters (22)
- 0:00Introduction to third-party libraries
- 1:02Google Maps outage impact
- 5:55Third-party code risks and benefits
- 7:40Library governance explained
- 10:08Business priorities for library selection
- 11:31Evaluating third-party libraries
- 14:18Managing library upgrades
- 16:01Library governance examples
- 19:13Mobile app release lifecycle
- 20:39Defense techniques overview
- 21:40Delayed initialization of libraries
- 23:24Handling Play Services risks
- 25:32Google Play Services challenges
- 28:02Transitive dependency conflicts
- 29:08Jar shading drawbacks
- 30:12Abstraction of third-party libraries
- 31:14Linters for crash prevention
- 33:23Automated crash recovery systems
- 34:51Black Swan recovery engine
- 36:57Push-based recovery mechanisms
- 38:41Force upgrades and user attrition
- 40:04Summary and Q&A
related talks
30mLearn from developers: Lyft and Google Maps share their experiences optimizing app performance
14mBuild powerful, reliable apps with Google Play services
29mDon't reinvent the wheel, use libraries: Modern Android Stack
23mSpeed Trap Ahead - Avoiding Costly Security and Privacy Issues in SDK Integration
35mEscaping the Dependency Hell on Android
53mHuawei Mobile Services Vs Google Play Services?
01h 12mInterview and Q&A
03mInterview