Firebase Crashlytics vs. Fullstory

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.

Incentivized

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.

Incentivized

• 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.

• Tracks users' online experiences from start to finish.
• Makes it easy to share a customer's experiences with the rest of my team.
• Allows me to use different methods to find evidence of a customer's experience.
• Shows page insights via segmentation that help me know where to improve my site.
• Tracks error clicks and dead clicks for quick insights into site improvements.
• Integrates with HelpScout for easy access to customer problem-solving.

Incentivized

• 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.

Incentivized

• The ramp-up time to learn the entire product can take a little while. There are just so many absolutely wonderful tools and different ways to look at the same type of information that it can take a new user a few weeks to understand and then more time to master. However, FullStory has a ton of training resources to help with that! A lot of my own teammates have taught themselves FullStory through those training resources.
• The UX of the product is totally wonderful, but there are tiny things that make getting to certain parts of the product slightly more challenging (like clicking into a modal in a modal). Sometimes buttons or links are placed out of my field of view, but those are minor things I notice because I work in UX.

Incentivized

Because its fulfilling our basic and necessary requirements that can be an only and enough reason to renew the subscription.

It's been a phenomenal tool for us; every department that uses it has found something new and unexpected that it can do that they're really excited about. Even if we *only* used it for bug triage, it would be worth our time and money. The fact that we can use it for so many other things as well--gauging how customers interact and use our site, identifying UI problems, etc.--is above and beyond

Incentivized

Because everything seems to be easy to find and it doesn't take long at all to learn how to use the product

Incentivized

We've never had issues with availability

Incentivized

It seems the performance is really good and always loads quickly

Incentivized

They have been overall pretty responsive and proactive. The tool is pretty straightforward to use. Most of the questions we have had to work with them on our how to use new features or adjust our integration to ensure we are gathering all the data from all of our tools.

Incentivized

To successfully implement FullStory, it is important to plan your implementation carefully by defining your goals and user segments. You should also use tags and filters to analyze your user data, train your team to use FullStory effectively, and use FullStory in conjunction with other analytics tools to get a more complete picture of your user's behavior. By following these tips, you can gain valuable insights into your users' behavior and experiences, and use this information to improve your website or application.

Incentivized

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.

Incentivized

Smartlook is software that records users on a website
and mobile app. Finding useful information within thousands of recordings is
made quick and easy with features that help you accomplish this. I have chosen FullStory because it is easier to use and has more advanced features compared to Smartlook.

Incentivized

Full story was easy to scale with the growth of our teams and organisation

Incentivized

• 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.

Incentivized

• Triage for front end bugs - FullStory can sometimes help you spot a bug in action much more quickly than trying to recreate it on your own
• Observing customers use new features and understanding why a new feature may be performing better or worse than expected

Incentivized