Comparison between TestFlight Live, QuincyKit and Crashlytics

Question

I am going to launch my app on the AppStore and I would like to keep track of crashes and fix them as soon as possible. If possible, it would be nice to collect also some additi

Answer 1

Crashlytics is second to none for crash reporting.

We were in the same boat as you trying to find the best crash reporting solution. After some thorough investigation and test runs of TestFlight, HockeyApp, and Crashlytics, we originally chose HockeyApp because they allowed us beta distribution along with crash reporting on both iOS and Android (we wanted both in one solution for both platforms). However, HockeyApp's exception backtracing was just not giving us any additional crash details. This is where Crashlytics shines. Their exception backtracing is amazing. Period.

So here's my summary of all 3 SDKs:

Crashlytics

• #1 crash reporting
• #1 exception backtracing, bar none (provides very useful extra crash details)
• Extremely fast and lightweight
• Custom key logging for additional crash context
• Best duplicate crash recognition and culling
• Automatic SDK updates (Their Mac app automatically updates the Crashlytics iOS SDK in your project)
• No beta distribution (I'd love a one stop solution for crash reporting and beta distribution)
• Automatic build server support

TestFlight

• Somewhat heavy, and adds bloat to your app package
• Great beta distribution
• No Android support (at least when we tested back 6+ months ago)

HockeyApp (HockeyKit - Beta distribution, QuincyKit - Crash reporting)

• Lightweight
• Crash reporting UI a bit confusing
• Exception backtracing severely limited (at least when we tested in March of 2011)
• Very good beta distribution

All that said, we chose Crashlytics for crash reporting, and HockeyApp for beta distribution. But you must chose what works best for your needs.