It really irks me when crashes are made out to be the result of user actions, or some inescapable act of god. Excepting the very rare hardware fault, crashes are caused by a <i>programmer error</i>. PERIOD. That is all that really matters from the user's perspective. There may be some way to work around the bug by tinkering with things, but nothing the user does can ever <i>cause</i> a crash.<p>Also, it wouldn't surprise me if iOS apps crash more than Android apps, because iOS doesn't have virtual memory. When an iOS app runs out of physical memory, it gets killed. This was allegedly a design decision.
My anecdotal evidence co-incides with this, I used to use Android and had barely any crashes (the only ones were generally specifically reproducable bugs), and now I use iOS and I see a lot more.<p>I always attributed it to memory management - manual memory management is simply a lot easier to f' up than garbage collection. Meanwhile Android apps are slower and probably consume more memory. It's all tradeoffs.
I get loads of iOS app crashes. My wife routinely crashes the browser on her iPad. It is interesting though that unlike Android she never thought the apps were crashing, because they just silently exit and return her to the home screen without any message. She always just assumed she accidently exited the app herself. On Android on the other hand you get the ugly 'Force Close' and other unfriendly messages. I always wonder if this contributes to commonly held belief that iOS apps are of higher 'quality' (obviously other things like smoothness and design do too...)
Sorry, but this analysis does not seem useful.<p>In the subset of apps that
1) are tracked by crittercism, and
2) crashed,
here is some data. Great. I'm more interested in the number of apps that did not crash - but those have already been filtered out of the data set. Also important if you want to make a meaningful comparison, what percentage of apps on each platform are tracked by crittercism?<p>Way too many unknowns to draw any meaningful conclusions from this data.
I develops applications for a living on both android and iOS, and as a developer, each one has its quirks.<p>Iphone apps tend to be more robust. The objc language has some interesting features like being able to signal a nil (the objc null). You can chain operations without having to care about fails in the middle, and check the final result for nil. This is the equivalent, saving the distance, to the java null pointer assignments, which is perhaps one of the most common errors.<p>The tricky issue about objetiveC and iphone is memory usage. Memory that is not correctly managed, like free twice, it is going to fail crashing the app (the EXC_BAD_ACCESS error). Getting this right takes a considerable amount of time and effort. Tools to make this easier are the SDK memory monitor, static code analyzers like clang, or the automatic reference counting (ARC) which lets the compile handle <i>release</i> and <i>retain</i> operations for you.
I suspect that 75% of the crashes on iOS are from poor memory management due to naïve app programmers. Android app developers don't need to worry about memory management, because Java takes care of this automatically. I suspect with iOS-5's new automatic reference counting, iOS crashes will decrease.
YMMV, I guess. I believe there's a general rule that the more crappy apps you put on your device, the more often you will see crashes. I almost never see an app crash, the worst offender over the years has been the New York Times app, of all things. I periodically delete it and read the Times in Safari until they ship a new version. My wife OTOH plays a ton of games and sees a fair amount of crashes. I'm guessing games are not as well-tested, but also, more apps will mean more crashes. Crash, BTW, means "freezes up". Easy to recover by pushing the button and the phone and the rest of the apps are still fine. The phone itself has only crashed a couple of times over the last three years, requiring a power off and restart.
I have almost never had an iOS app crash on me. I get crashes in Android apps almost weekly. I honestly don't know where those guys are getting their data, but I really don't believe it.<p>It's true, it's a lot easier for developers on Android to fix bugs and quickly update their apps because of the lack of an approval process, but that also lowers the bar a great deal on the quality of apps (a lot of which never get updated).<p>Edit: I don't know how this goes on iOS, but for Android Market apps, you can see all crash reports straight in the publisher console, without the need for 3rd party services.
I mention this in the article, but I want to re-emphasize how the approval time is a huge factor. We've had Android developers submit fixes the same day they've discovered a bug on our platform, while iOS devs wait in the queue. You could argue this allows buggier apps to be submitted in the first place, but this sample is taken from devs who use our service and obviously care about producing high quality apps.<p>(To be fair the iOS approval process has sped up considerably, even with the number of submissions growing)
I've made apps for Android and iPhone. The iPhone crashes less. I've found in a lot of cases that null pointer exceptions that usually would kill an Android app and handled silently by iPhone because in Objective-C passing a message (calling a function) on a null value is just ignored. I wonder how many other iPhone apps have avoided crashing because of this behavior.
I get <i>an</i> iOS app crashing all the time. The Facebook app closes unexpectedly on me a fair bit, and I've had Safari close two or three times, but apart from that everything I use seems to be very stable...
I've been repeatedly shocked about how many of my friends give me crap for liking Android and then talk about their apps crashing frequently. I can't say I've had a single app crash on my Galaxy Nexus and that includes running nightly CM9s.