A smoothly working mobile app means happy users. App crashes affect a lot of factors: quality, conversions, feedbacks, and can occur for various reasons: updating separate module or SDK from the side of the services supplier, e.g., Firebase; server errors or server software update; changing dependences and device software update, etc. A post-development testing helps refine the app, detect critical crashes and errors on main devices. However, even high-quality testing does not guarantee the absence of crashes, as they may occur due to a big number of unique devices (over 20,000 in the world) or, for instance, after a new version of iOS has been released. Our goal is promptly prevent and fix them. If not controlled and analyzed, app crashes may lead to the risks that entail a reduced number of conversions, bad feedbacks on the app market and big number of removals.
Main reasons for app crashes:
- Device software update;
- Updating separate modules or SDK used by the app;
- Server software update;
- Uniqueness of each device and its configuration.
Firebase provides a tool for building real-time crash reports – Crashlytics, which helps fix bugs and errors depending on their impact on users. Crashlytics is easily integrated into iOS and Android apps.
Crashlytics helps identify how a particular crash affects users as well as what parts and lines of the code it is caused by. Reports have a contextual view and feature filters by software, version and device. Detailed information about the event that led to a crash will make it easy to detect its causes, deal with them and eliminate the problem. Besides, Firebase crashlytics tracks the crash frequency and warns about the errors that start to occur more frequently.
Crashlytics main features:
- Detailed crash reports;
- CrashInsights: tips that help detect and eliminate typical problems;
- Analytics integration: facilitates analytics and provides information about users who have had crashes;
- Real-time notifications about new and critical crashes.