Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>There is also <a href="http://www.hockeyapp.net/" rel="nofollow noreferrer">HockeyApp</a>. I am comparing Flurry and HockeyApp based solely on grokking their website propaganda, and my summary is that HockeyApp is more "fix-centric", whereas Flurry is more "sales-centric:" Dev &amp; QA would benefit more from HockeyApp's great crash reporting features, and Product Management would benefit more from Flurry's crazy slice-and-dice analytics. Hopefully that helps guide you based on what you are trying to accomplish.</p> <p><strong>Update</strong>: I had a quick chat with the Crittercism dudes and wanted to add my findings. Their offering seems to fill the gap between fix-centric HockeyApp, and sales-centric Flurry. It uses the same underlying PLCrashReporter library to produce robust crash reports like HockeyApp does, and it seems to have more Flurry-like analytics than HockeyApp. Also, pricing ... Flurry is free (though they seem to monetize through advertising on their WWW interface). HockeyApp has pricing based on plans, starting with a $10/month plan. Crittercism prices based on # of active users of your app and you have to work with their sales folks to eek out an actual number. </p> <p><strong>Also update regarding support</strong>: HockeyApp's support is excellent; I've never waited more than 10 minutes to get a response back to my questions and the responses are succinct and accurate. Flurry, about 24 hr turnaround and a fairly unpersonalized and lifeless response that was mostly accurate. Crittercism has been quite fast to respond to my inquires; they have a "Chat Now!" button that put me through to the CTO, which was great for the technical questions I had.</p> <p>Some key specifics and elaborations:</p> <ul> <li><p>HockeyApp automatically symbolicates users' crashreports on their web interface, and can group crashes by crashing API. Flurry does not; it just shows you a bunch of raw crashes and you get to manually symbolicate them one instruction at a time (using <code>atos</code> -- you can't use <code>symbolicatecrash</code> because Flurry doesn't give you a proper .crash report). Be aware that <a href="http://support.hockeyapp.net/discussions/problems/981-line-numbers-seem-to-be-off-by-1-2-lines" rel="nofollow noreferrer">line numbers in HockeyApp can be off by one or two lines</a>.</p></li> <li><p>The crash reports that Flurry shows you do not include other running processes, whereas HockeyApp's do. In fact, it appears that <a href="https://flurry.zendesk.com/entries/240046-larger-text-field-for-crash-error-stack-trace-reporting" rel="nofollow noreferrer">Flurry crash reports are truncated</a> to 255 characters or so. They are anemic compared to HockeyApp.</p></li> <li><p>For crashes you mark as fixed in HockeyApp's web UI, HockeyApp can inform a user who subsequently experiences such a crash that the issue has been fixed in a new version.</p></li> <li><p>Flurry has very deep analytics prowess that HockeyApp cannot touch: tracking usage stats, customer engagement, average session length, geographic distribution of your app, user retention over time. </p></li> <li><p>Flurry is free; HockeyApp (free up to 10 apps). Both provide email support, but only HockeyApp provides a discussion group. Both can record arbitrary messages (like a JSON response from the server that caused your app to crash) but only HockeyApp indicates that this message can be any length.</p></li> </ul> <p>Alas, these are just a few random tidbits that appealed to my developer-nature and cause me to prefer HockeyApp. I wonder what would happen if I used both in my app! </p> <p>If you have 7 minutes, HockeyApp has <a href="http://www.youtube.com/watch?feature=player_embedded&amp;v=U6Jon0ombSk" rel="nofollow noreferrer">a video walkthrough</a> that I found quite useful. </p>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. VO
      singulars
      1. This table or related slice is empty.
    2. VO
      singulars
      1. This table or related slice is empty.
    3. VO
      singulars
      1. This table or related slice is empty.
    1. This table or related slice is empty.
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload