I don't have much experience with other Crash reporting systems for iOS besides Crashlytics, but I will say that overall I have been happy with them. The image you linked to leaves out the actual stack trace, but trust me it's there.
The reason I ended up going with them is that they are 1) The library is tiny and isn't bloated with things I don't need 2) It's integration with Jenkins is great. It automatically uploads my dsym with the correct build number and all crashes from that build get tagged with that build number. 4) Support is fast 5) Love supporting a local Boston company
I will say that some of their design is a little over the top, they certainly love skeuomorphism. One thing that kind of annoys me about their site is that the content is a fixed width. This is frustrating because they add "..." to shorten some labels to fit instead of using all the screen real-estate available.
The reason I ended up going with them is that they are 1) The library is tiny and isn't bloated with things I don't need 2) It's integration with Jenkins is great. It automatically uploads my dsym with the correct build number and all crashes from that build get tagged with that build number. 4) Support is fast 5) Love supporting a local Boston company
I will say that some of their design is a little over the top, they certainly love skeuomorphism. One thing that kind of annoys me about their site is that the content is a fixed width. This is frustrating because they add "..." to shorten some labels to fit instead of using all the screen real-estate available.