My view on Firebase Crashlytics
Rating: 10 out of 10
IncentivizedUse Cases and Deployment Scope
I am using firebase Firebase Crashlytics to get the actual report of the crashes with the exact line of code. Before Firebase Crashlytics it was very difficult to find the issues. Now, the performance of the project has increased because of the help of firebase Firebase Crashlytics. Firebase Crashlytics also provides all crashes, which we can not afford on our end because of the unavailability of real devices.
Pros
- Can get the device detail an actual state like RAM, Storage, Display Size, etc.
- Can get the class name and line number where crash occur.
- Its work in realtime so we can reduce the time of issue finding and resolution.
Cons
- Navigation between the issue listing and details is something difficult to understand for the new user.
- Pannel takes time in loading may be because of analytics data but it can be reduce.
- Not provide accurate line number in case of proguarded apps.
Likelihood to Recommend
If your application is in the initial stage it's very important to use Firebase Crashlytics to get the issues of real devices. Because at the time of development we can test on some devices only so it's very important to watch the behavior of other devices for the app and we can achieve it by Firebase Crashlytics.