Slashdot Mirror

And since Android app crash rates are actually lower than iOS

You're wrong, unless you can provide equally large-scale, cross-platform metrics. Compare the iOS 8 (most popular iOS version with about 85% usage share) crash rates (most recently 2.05%) with KitKat 4.4 (60% share) at 2.53% crash rate.

Apparently there are no stable releases of Android.
Fixed That For You.

Fixed that for your Apple-owned SMM sockpuppet handlers, you mean.

Nearly three billion Android devices are currently active, compared to around 500 million of your adored iOS.

That means there's more than enough data available to determine which is the more stable OS.

And unsurprisingly to everyone except Apple shills, Crittercism has found that even though iOS 7.1 is Apple’s most stable release yet, the latest software still has a crash rate of 1.6%.

On the other hand, Android versions KitKat, Ice Cream Sandwich and Jelly Bean all have crash rates of just 0.7%. Even Gingerbread appears to be more stable than any iOS version before 7.1. All in all, you're are significantly less likely to crash on an Android device than on an iPhone, iPad or iPod touch.

http://pages.crittercism.com/m...

It would have been interesting to know what apps they were really logging crashes for(I'm guessing all apps that use Crittercism). Were they including only non-beta internal builds in these numbers? That would have driven the iOS5 WAY up since you normally develop on the latest platform.

Of the apps that send their crash data to Crittercism and were included in this report; iOS apps crash more. The writeup here makes it seem like they were logging crashes of normal apps...

I disagree

You really don't get much more protection with Java then you do with native code on iOS. Exceptions only help you when you know you need to catch them. Null pointer dereferencing is pretty much a non-issue in ObjC/Cocoa because of the way messages are passed(at least no more than java.lang.NullPointerException). When you are multithreaded in Java it's trivial to make the simplest code throw a ArrayIndexOutOfBoundsException or NullPointerException when you hava your logic wrong.

The data we are looking at is from the small subset of apps which use Crittercism rather than TestFlight (why is anyone not using TestFlight?). It's not meant to be representational of the real-world. It would be interesting to know what iOS-based and what Android-based apps use Crittercism.

I disagree

You really don't get much more protection with Java then you do with native code on iOS. Exceptions only help you when you know you need to catch them. Null pointer dereferencing is pretty much a non-issue in ObjC/Cocoa because of the way messages are passed(at least no more than java.lang.NullPointerException). When you are multithreaded in Java it's trivial to make the simplest code throw a ArrayIndexOutOfBoundsException or NullPointerException when you hava your logic wrong.

The data we are looking at is from the small subset of apps which use Crittercism rather than TestFlight (why is anyone not using TestFlight?). It's not meant to be representational of the real-world. It would be interesting to know what iOS-based and what Android-based apps use Crittercism.

iOS crashes more than Android (for those who don't feel like trawling through the (not brilliantly formatted) article.

* for apps which use Crittercism's crash reporting component. That's important since we do not know which apps those are and if they are representative for the whole software catalog for the devices. Only Apple has all the crash reports across all iOS apps (and even then only for people who haven't disabled the sending of crash reports.) Maybe the jailbreak guys could compile some interesting stats, since they've released a tool to upload your crashlogs (Cdevreporter) to them to aid in jail breaking.