Likelihood to Recommend Crashlytics is almost a defacto standard in the Android world for tracking crashes in the field. I've used it on the last 4 Android projects I've been on. It's not as helpful on iOS' stacktraces but I'm not sure if anything would be better because iOS stack traces are from ObjC code which is not as useful as Java stacktraces.
Read full review For the price and the features available, Localytics is one of the best options. It is more robust in areas that we don't need it to be and overall there could be simpler flows for sending push notifications or performing actions that you need to do every week. Also, the data it sends back on how push notifications perform is basically useless. There needs to be more explanation on the impact notifications have on users. The data would always say that notifications drove less engagement but we would see engagement go up every time we sent a notification.
Read full review 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. Read full review Great web interface which provides a couple of levels of pivoting and filtering of data Straight-forward integration for simpler use cases Access to raw data through S3 for use in your own data pipeline Read full review Cons Sometimes UI of Firebase Crashlytics is quit difficult to understand for new users. There can be a proper discretion for all the features that is offered. There can be api crash report also. Read full review The biggest thing I would like to see with Localytics is the capability for more correlations. The limited amount of correlations available does restrict the type of analyses that could be done with the data. An easier interface to move data into Microsoft Excel would be very useful, rather than creating annoying workarounds. More/better automatically scheduled reporting, as well as an Excel plug-in to access the data rather than being restricted to the Localytics interface. Read full review Likelihood to Renew Because its fulfilling our basic and necessary requirements that can be an only and enough reason to renew the subscription.
Read full review There is a lot of competition. I would renew if there isn't anything more exceptional that would justify the re-coding and implementation load costs
Read full review Support Rating It would take several weeks to hear back from the billing team. It took 3 months to resolve an invoice last year. Their technical support is very responsive. I would typically get a response in under 24 hrs.
Read full review Alternatives Considered As mentioned previously, the only realistic competitor to Crashlytics is
Instabug (backed by Y Combinator in the W16 class). While Crashlytics is focused on actual crashes,
Instabug 's main innovation is in collecting feedback from users for non-crash bugs. While non-crash bugs are a substantial category of bugs,
Instabug 's pricing is quite steep. As soon as you go beyond the most basic features your monthly bill spikes to $124 - $499 per month, whereas Crashlytics is 100% free (for all usage levels and all enterprise features). Based on this, I've never tried
Instabug because the ROI just wasn't there.
Read full review We have not used other products but are going to start exploring making a switch to a new platform.
Read full review Return on Investment Allows us to easily share crash data with clients. Provides confidence to our developers and project teams by having trust in the data that is being reported. Allows us to quickly and efficiently address fatal crashes. Read full review Was our first provider of user-level event data Allows for many users to easily answer their own questions before making requests of the data team Raw data dumps gave the data team the ability to provide more in-depth analyses. Read full review ScreenShots