8 comments

[ 3.2 ms ] story [ 27.1 ms ] thread
We've been using this instead of TestFlight. The crash reporting aggregation is a huge time saver, and the developer is responsive.
Am I crazy for considering switching from TestFlight to HockeyApp mainly because HockeyApp actually charges for the service?
No, absolutely not. With free products, you are the customer. I don't like this idea either. Also, HockeyApp is far superior to TestFlight. They had In-App-Updates at launch day.
HockeyApp's crash reporting is far more comprehensive and useful than TestFlight's, especially in the server-side symbol/line number associations and grouping of crash reports.

This was a major deciding factor in our switching.

Hey, I am Andreas, one of the developers of HockeyApp.net. The service provides some pretty unique features especially advanced crash report management. Crash Reporting is based on PLCrashReporter (see http://landonf.bikemonkey.org/code/objc/Reliable_Crash_Repor...), works also in the App Store with full server side symbolication grouping all crashes by class, method and line number. Let me know if you have any questions.
We should talk, because I've developed a lot of the stuff you're doing (OTA distribution, analytics, crash and error reporting, bug tracker integration) internally. This was back before both TestFlight and you launched, and we needed a solution so bad that we wrote our own. Would love to talk further if you're interested.

Also, the line about your documentation did not instill me with great confidence:

> HockeyApp provides an open and well-document API which is based on HTTP and JSON.

Can you talk more about your internal solution?