Elevating Android App Resilience: Incident Management Strategies
summary
Built an alerting infra for Microsoft To Do (10M downloads, 4.7 rating) that detects crashes, ANRs and a custom sync score metric and triggers automated triage, routing and patch workflows. Uses Google Play Console for crash/ANR feeds, CI/CD plus JUnit/Selenium for gated releases, SOAR and EDR for client threats, and internal Copilot integration for AI-assisted RCA. Stress tests with ~1,000 contacts validate scale; the alerting caught sync-score regressions and restored data consistency.
AI-written summary · about
chapters (16)
- 0:00Introduction
- 1:08App resilience importance
- 2:54Incident severity classification
- 4:19Incident response protocols
- 6:47Post-incident reviews
- 7:30Proactive monitoring techniques
- 8:58Automation in incident management
- 10:22Automated workflows
- 12:10Sync score monitoring example
- 13:55Continuous improvement culture
- 15:21Q&A: Crash handling
- 19:21Q&A: Hotfix deployment
- 21:53Q&A: AI for monitoring
- 22:37Q&A: Remote logging
- 23:41Q&A: Third-party library security
- 24:44Stress testing importance
related talks
44mEfficient Android app monitoring
18mBeyond the Noise: Effective Management of Non-Fatal Issues
17mVitals: Past, present & future
18mProduct Reliability in
32mMeasuring and enforcing app health at scale
35mRelease Android apps globally with no headache and minimum stress
53mCheck your app's vitals
24mFuture-proofing your Android release process