Comparison between TestFlight Live, QuincyKit and Crashlytics

前端 未结 5 1650
庸人自扰
庸人自扰 2021-01-29 23:32

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

5条回答
  •  不要未来只要你来
    2021-01-30 00:06

    I honestly think Crashlytics is a better solution than Testflight for crash reporting.

    Here's what you get with Crashlytics that you don't get with the others.

    • Duplicate culling (TF does this too, but its not too great at it, Crashlytics is damned near perfect)
    • You can actually mark crashes as closed/resolved, and get them out of your list for a given version.
    • Crashlytics does everything TF's Crash reporting does, but better and then some (logging, stack traces, etc.)
    • Percentage of affected users, and the numbers that go with that. (ie: should i fix the bug that happened to one guy, or the one that's happening to 10k?) Testflight doesn't tell you this.
    • Prioritization based on occurrence. This is probably the most important gain in my opinion.

    These are just a few, but I figure they're probably the most important ones for you.

    We used Testflight's crash reporting for close to 2 years on an extremely popular app (several million D/Ls). Its definitely better than nothing, and very convenient if you're using TF for distribution as well, however you get many more benefits from Crashlytics. We switched to Crashlytics this summer and now we're actually able to manage crashes and make smart decisions about what to fix and when, instead of just sifting through a giant never ending list.

    I see you already accepted an answer, but I'd seriously give it another look even if you opt to continue with Testflight. I've found its hard to really grasp what you're missing until your app has shipped, at which point is even harder to change.

提交回复
热议问题