Mobile App Crashes in Production: Lessons Learned from a Tester’s Viewpoint
summary
Claims concrete failure modes and fixes: QR code scanning failures, wearable-device data mismatches, and OS/hardware fragmentation cause real crashes; network edge cases like 2G/3G and a force-upgrade rollout that loops users prove it. Recommendations list specific practices: low-memory and CPU spoofing, upgrade testing across versions, better permission and library handling, and analytics-backed prioritization. Tools named and evaluated include Sentry session replay and Firebase Crashlytics for pinpointing files and devices, and notes limits with React Native/Flutter stacks.
AI-written summary · about
chapters (17)
- 0:00Mobile app crashes intro
- 1:08Why crashes matter
- 2:35Crash types and impact
- 4:01Device/OS risks
- 5:25Common crash causes
- 6:30Network failures
- 7:54Resource management
- 8:55Crash prevention
- 10:40Testing strategies
- 12:29Performance & reporting
- 13:32Key metrics
- 14:54Crash analysis tools
- 17:43Crash-free rates impact
- 18:27Q&A: Web to mobile
- 19:31Q&A: Upgrade testing
- 20:53Q&A: Worst failure
- 21:57Q&A: Beta testing
related talks
46mUsing Analytics to Improve Quality
21mSucceed by Failing – A Game Dev’s Journey Into a Mobile Dev Ops Tool Chain
26mDevelop Rock-Solid Apps with Firebase
14mRoundtable: Ensuring Game Stability: How To Find, Monitor, & Fix Issues With Firebase Crashlytics
37mMobile Testing: Pinpointing Invisible Problems
45mUncovering breaking changes behind UI on mobile applications
17mHow can Firebase improve the user experience of your app?
51mQ&A Session