I have integrated Crittercism in a couple of our apps.
The crash reporting has been very useful in addition to Flurry. It
gives you a stack trace for each crash, as well as other diagnostic
info (what kind of device did the crash occur on, what OS version,
what was the memory use, etc.). It's definitely helped me smoothing
out some bugs. (Crittercism's T real time usage stats are nice
too ;) )
There are some other alternatives as well. You might want to have a
look at hockeyapp (
http://www.hockeyapp.net/). It's a service for over-
the-air distribution of betas (like TestFlight), but also does live
crash reporting.
Cheers,
Adriaan
On Feb 6, 3:03 pm, Oleg Kiorsak <
kior...@gmail.com> wrote:
> Hi all
>
> was wondering if anyone here used this thing:
http://www.crittercism.com/features.html
> or what your thoughts/opinions are?...
>
> I been "leveraging" the Flurry SDK for crash reporting purposes, but that
> requires a bit of add-on work/code,
> whereas this one seems to be more focused/dedicated to just crashing and
> claims to collect lots of relevant info "out of the box"...
> is it worth adding *in addition to Flurry?*
>
> (btw came across it via this article -
http://www.forbes.com/sites/tomiogeron/2012/02/02/does-ios-crash-more...