Crashlytics is a mobile analytics tool which helps users find the exact line of code that their app crashed on, providing granular insight into mobile app performance and user experience. Crashlytics was acquired by Google in 2017 and is now offered as part of the Firebase product.
N/A
Fullstory
Score 9.1 out of 10
N/A
Fullstory’s behavioral data platform helps technology leaders make better, more informed decisions by injecting digital behavioral data into their analytics stack. The technology's behavioral data transforms digital visit into actionable insights.
Truly speaking, it is also a quite good tool for crash reports, but Firebase Crashlytics was better to use when you are using the Firebase Realtime database as your DB, so the integrations become much easier.
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 …
Based on what our developers have told me, Crashlytics is better than anything else out there. I personally have worked with Flurry for event and crash monitoring, and my experience was terrible. I know some project teams have tried some alternatives in the space that I don't …
Compared it with Crittercism on a Xamarin project a while back and on that platform, Crittercism was the best. But on Android, Crashlytics is just a lot better in providing good stack traces and having a useful analytics console. It's pretty much the defacto standard on …
I think other tools are either too heavy or complicated to implement and / or understand. Full story has a super light weight feel to the system and works magically. I implemented Mixpanel once and the entire team struggled with it before replacing it with Full Story after …
Fullstory is really the best at session recording. They are adding new and more features to become more competitive with other web analytics tools (like Pendo, Heap, and GA). But we ultimately keep them because they make it so easy to actually see how people interact with your …
Microsoft Clarity is not on the list. This one is not even close though. 4 years ago there was not much competition unless you paid a fortune for the big survey companies. I see there are many more out there now, and may start looking now that the prices are not as affordable …
Most of the tools we evaluated just didn't have the depth of analysis that we needed. Content Square looked GREAT but it was a much higher price point.
HotJar is built for marketers, whereas FullStory is for product teams, but the tool still stacks up well against HotJar. It has feature parity and is a little more intuitive to use.
We don't use anything else that is close to what Fullstory does. If anything Intercom would be the closest however we use them together to offer the best support possible.
Firebase Crashlytics is a no-brainer if you are already using any of the other Firebase suite of products, as its integration is very easy if you are already using these in your app. If you have cross-platform Android, iOS, and macOS apps, you should also consider Firebase Crashlytics to provide a unified across your platforms. If your app is only on Android or only on Apple, then you may be better off remaining with the default Apple Developer or Google Play Developer Console crash collection experiences.
It was extremely useful in identifying places in our product where things weren't functioning, or where it looked like action was available to the end user but in reality, it was not and therefore caused lots of confusion. It doesn't help as much in other scenarios to see what catches a user's Eye or where they go if they leave our application as well as an actual in-person interview would help with eye-tracking software.
Can be a little confusing to know the exact time something happened, in local time or customer time? That's helpful for engineering to look into log files.
When looking for a specific session, it would be nice if you have a easier list of sessions with a little more info to choose from
It would be nice to be able to save flagged sessions and annotations under my profile to reference later
The metrics are hard to understand at times and inaccurate to the point of being unusable. I stopped pulling them and solely rely on Adobe Analytics for them. So far, I've only used FS to watch sessions and determine behaviors
It is very easy for non-developer staff to use the Firebase Console and gather information for the development team. Developers will find it straightforward to integrate Firebase Crashlytics into new or existing codebases using Google's in-depth developer documentation. I cannot think of an easier cross-platform solution to use, and because of that I wish it supported more platforms!
Yes, that is correct. FullStory has a dedicated support team that is available to assist with any issues or questions. The team is known for being responsive, knowledgeable, and helpful, and they are committed to ensuring that users get the most out of the FullStory platform. They helped us a lot to implement it with our web app
I was not involved in the initial implementation, but I have found it easy to pick up and use without any guidance, so it's very user-friendly, intuitive, and not difficult to get a sense of use, though it may be more difficult to master (I am not a Fullstory master... yet!).
Compared it with Crittercism on a Xamarin project a while back and on that platform, Crittercism was the best. But on Android, Crashlytics is just a lot better in providing good stack traces and having a useful analytics console. It's pretty much the defacto standard on Android...everyone uses Crashlytics. It's even more common to use Crashlytics and the Firebase crash tracking; Firebase does track ANR's a lot better though.
Fullstory is really the best at session recording. They are adding new and more features to become more competitive with other web analytics tools (like Pendo, Heap, and GA). But we ultimately keep them because they make it so easy to actually see how people interact with your site. It is one thing to see a report that says customers fall off a page, it is another thing to actually be able to watch what they do as they fall off.
We reduced our payment error rate by 20% using FullStory.
Our product design team is able to get initial designs approved 95% of the time using FullStory data in order to explain to our stakeholders the reasoning behind decisions. We also do a before-and-after analysis, and we either net out the same with the new designs (just improved visuals) or improve the metric of whatever was designed. More often than not, we improve the metric.
We decreased the time to A/B testing insights by 50%.
We can usually visualize a production issue via FullStory within 10 minutes.