Linked by Thom Holwerda on Fri 3rd Feb 2012 23:43 UTC
PDAs, Cellphones, Wireless There's an article making the rounds right now about how applications on iOS crash more often than applications on Android. I'm not going to detail the entire methodology - the article itself does so - but it does raise an interesting talking point about how both mobile operating systems handle application crashes and updates.
Thread beginning with comment 505970
To read all comments associated with this story, please click here.
My Phone
by hackus on Sun 5th Feb 2012 15:59 UTC
Member since:

Well, in my personal camp, where I use my own phone, crashes have happened in the past from bad apps, doing bad things.

Now, the term "crashes' is a bad term because it is imprecise.
Crashes that happen that require the phone to be rebooted are not acceptable.

An App crash is annoying, but acceptable.

I have friends who I see rebooting their iPhone's because the entire phone becomes unresponsive, which I must admit very rarely happens on my HTC EVO. Rarely though do they complain about App crashes. But it seems to me iOS requires rebooting the entire iPhone way too often.

Now, if you give the consumer the ability to contribute changes or make corrections to your phone's software, obviously that is going to speed corrections, and increase reliability.

Android does this. Apple assumes the customer doesn't need that ability, which means technically you should see more crashes, and slower correction times for issues because the customer can't do it themselves, they have to wait for Apple.

I can also see Android being a platform which yields more reliable up time for the phone, due to the apps use of Java.

Which as people have pointed out is a very effective sandbox, able to limit memory and system resources that prevent the app from whacking the phone.

Since this is a virtual machine environment, those sorts of things are quite easy to do.

I am not familiar with iOS enough to know whether or not they have a similar ability.


Reply Score: 3