Stories
Slash Boxes
Comments

Dev.SN ♥ developers

posted by LaminatorX on Monday March 31 2014, @05:36AM   Printer-friendly
from the What's-Windows-Phone? dept.

cbiltcliffe writes:

Crittercism has performed testing on mobile platforms, and found that while Apple's release of iOS 7 is the most stable iOS release to date, reducing the crash rate to 1.7%, this still pales compared to Android versions 4.0+, which have a crash rate of only 0.7%.

Not surprisingly, gaming apps with complex graphics and sound crashed more often (4.4%) than other apps, with eCommerce apps getting the best rating of only 0.6%. Some pre-digested coverage from gantdaily.com can save having to dig through pages of research data slides, if you're not looking for the gritty details.

Is this consistent with your experience, or does your particular usage tell a different story?

 
This discussion has been archived. No new comments can be posted.
Display Options Breakthrough Mark All as Read Mark All as Unread
The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
  • (Score: 2) by MrGuy on Monday March 31 2014, @01:32PM

    by MrGuy (1007) on Monday March 31 2014, @01:32PM (#23669)

    My response to everything in the presentation is "OK, that's interesting. So what?"

    Graphic heavy apps like games crash more often than transactional apps, but transactional app crashes are potentially more significant? That's interesting, but so what? Should we make different kinds of apps? Is there something we can learn from about transactional apps? Can you tell me which kinds of calls are more likely crash, so I can avoid them?

    iOS 7 is more stable than iOS 6. OK, so what? Should we make apps that ignore iOS 6? Are there iOS 6 features we should deprecate? Are there ways of recovering from crashes we should implement?

    Some android manufacturers' devices crash less. OK, so what? Should Android app makers manufacturer-lock their apps? Are you trying to get the manufacturers of more crash-prone devices to change something? Are there specific things some manufacturers do better/worse? Are there specific calls that are problematic for some manufacturers, so developers should consider avoiding/working around them?

    There is nothing remotely actionable about any of this information. Nothing anyone can do with it. Nothing it tells us to change. Nothing that we can use.

    This is a classic case of someone not realizing that the fact that you have some data doesn't mean you have something interesting to say.

    Starting Score:    1  point
    Karma-Bonus Modifier   +1  

    Total Score:   2