11–20 of 30 posts
The problem with Crashlytics is that you can't get your data out besides through their pretty website. Their search is limited and there's no adhoc querying. There's no API so you can't integrate with any of your other tools. Also, you have to trust Twitter with your app's data.
Crashlytics as part of Twitter's Fabric.io suite is awesome. It's our goto for simple things like monitoring crashes/errors, DAU/WAU/MAU and associated ratios across our apps. It also knocks TestFlight right out of the water for beta testing.
I wanted to do some estimation on what kind of revenue 1M apps could bring but their pricing page consists of "enter your email and we'll contact you shortly". Seems weird they haven't passed the invite only phase at 1M apps served.
This may be a good place to ask: Now that Testflight is gone, what do you recommend for getting crash reports (incl stack trace) in iOS apps? Crashlytics?
Question: How Crashlytics (or Fabric) lives? It's free, but how are they making money to survive?
I'm asking because it's an awesome service, and I want to know if they will be free forever, or in some point (like how did happen with Pivotal Tracker) they will charge with an ugly and useless free option.
Crashlytics as part of Twitter's Fabric.io suite is awesome. It's our goto for simple things like monitoring crashes/errors, DAU/WAU/MAU and associated ratios across our apps. It also knocks TestFlight right out of the water for beta testing.
Thanks ksar! Wait until you see what we've been working on ;-)
The problem with Crashlytics is that you can't get your data out besides through their pretty website. Their search is limited and there's no adhoc querying. There's no API so you can't integrate with any of your other tools. Also, you have to trust Twitter with your app's data.
The problem with Crashlytics is that you can't get your data out besides through their pretty website. Their search is limited and there's no adhoc querying. There's no API so you can't integrate with any of your other tools. Also, you have to trust Twitter with your app's data.
They also need to add proper alerting. Telling me that my app with 1m users has reached "Impact Level 2" for a particular bug because it's affected 50 people is basically useless.