In Android, there is a high probability of your app crashing even after you have manually and automatically tested it. This can be due to factors such as incompatibility with different API levels, screen sizes, phone memory, hardware sensor availability, and vendors’ customization to suit their individual devices. Crashlytics will help you diagnose these problems.
Crashes make your users sad and angry. They might even want to uninstall the app if this happens often. Then give your app a bad review, give negative feedback on the play store, and then go install your competitor’s app! In this already crowded and competitive app market, making your users happy is vital for your app success.
It’s quite impossible for your app not to have crashes, but keeping your crashes down to a minimum is very important. During development and testing, you might not have encountered a particular crash, but in production when your users are actively using it, you’ll begin to see crashes. Using a robust and powerful crash reporting solution is essential to collect information about your app crashes and to give you an insight into how you can fix the problem to keep your users happy.
In this tutorial, I’ll show you how to use Crashlytics, a free and powerful yet lightweight crash reporting solution, which is part of the Fabric set of developer tools by Twitter. We’ll create a simple app that crashes when a button is clicked, so that we can get insight into the crash with Crashlytics.
Continue to read the full tutorial at Tuts+