3 ms·

I can’t say I’m thrilled with using Crashlytics in my own iOS apps, but I’m not aware of any better options when it comes to crash tracking. A handful of crashe

I can’t say I’m thrilled with using Crashlytics in my own iOS apps, but I’m not aware of any better options when it comes to crash tracking. A handful of crashes come in through Apple’s opt in crash report sharing but when compared to the data I’m getting from Crashlytics, it’s clear that a lot of info is missing. If I relied only on manually submitted bug reports and what Apple is telling me, I never would’ve come to know about many of the bugs I’ve fixed. Better testing could’ve caught some of them, but many just won’t surface in any other place except out in the wild. Is increased privacy worth decreased stability? I won’t claim to know the answer to that question, but I suspect it’s more murky than some think, especially when you have paid customers who expect a throughly solid product for their money.

blub 9y ago
It's not privacy vs stability, that's a favourite red herring around here. The problem is your development process is not capable of producing stable enough software. I don't know why that's the case, but you should work on that first. Deming: "Inspection does not improve the quality, nor guarantee quality. Inspection is too late. The quality, good or bad, is already in the product. As Harold F. Dodge said, “You can not inspect quality into a product"". This goes even more for crash-reporting quality into a product.
- kitsunesoba 9y ago
  I see what you’re getting at, but the reality is that there’s only so far massaging and rethinking your process can take you. No matter what you do, some number of bugs are going to find their way through. There’s going to be unforeseen combinations of variables and edge cases you’d never predict. The best one can ever do is reduce the frequency of occurrence to a minimum. Bugs are an inevitability, and I’d rather not be at the mercy of my users when it comes to finding out about them.

blub 9y ago

It's not privacy vs stability, that's a favourite red herring around here. The problem is your development process is not capable of producing stable enough software. I don't know why that's the case, but you should work on that first. Deming: "Inspection does not improve the quality, nor guarantee quality. Inspection is too late. The quality, good or bad, is already in the product. As Harold F. Dodge said, “You can not inspect quality into a product"". This goes even more for crash-reporting quality into a product.

kitsunesoba 9y ago
I see what you’re getting at, but the reality is that there’s only so far massaging and rethinking your process can take you. No matter what you do, some number of bugs are going to find their way through. There’s going to be unforeseen combinations of variables and edge cases you’d never predict. The best one can ever do is reduce the frequency of occurrence to a minimum. Bugs are an inevitability, and I’d rather not be at the mercy of my users when it comes to finding out about them.