Does iOS Crash More Than Android? A Data Dive


Recommended Posts

One good thing about Android is whenever an app crash you have an option to report it to the developer.

its send the details of the crash and the developer fix those issues.

I have seen many app which mention that in the change log.

One good thing about Android is whenever an app crash you have an option to report it to the developer.

its send the details of the crash and the developer fix those issues.

I have seen many app which mention that in the change log.

Also, updates/fixes get approved and posted faster with android. Updates can take days or a week to get approved by Apple for iOS since it has to go through the approval process. With Android, and update/fix can be released within hours.

Because I know what I'm talking about. I know what a crash is and how it manifests. A crash is not just "Oh crap. It's all gone wrong. Throw an error or reboot". IOS handles crashes a LOT better than android, and hides them from the user.

So you are saying that it's better to have the application you are using randomly vanish and the "desktop" appear than to see "This app may have frozen, wait or force close?" or "This app stopped working unexpectedly, force close"?

Maybe it's better for less computer literate people who think that is normal app behaviour, but I personally disagree that seeing no error message whatsoever is better than seeing an error message.

Please stop stating "iOS handles crashes a LOT better" as if it is a fact, when it is obviously personal preference. Thank you :)

What do you mean iOS crashes? Android doesn't "crash" either. It's always apps that crash.

The bottom line is that iOS is not "just working" while Android keeps crashing which is the BS mantra constantly being thrown out.

Besides the lack of a report dialog in iOS, wouldn't both OSes act the same way with regards to crashes?

In any case, anyone can deliberately do something silly like write data beyond the size of a list and trigger an app crash on an OS, and there are only a limited number of ways an OS can deal with that.

Quite petty to compare OSes based on "crashiness" if you ask me.

Because I know what I'm talking about. I know what a crash is and how it manifests. A crash is not just "Oh crap. It's all gone wrong. Throw an error or reboot". IOS handles crashes a LOT better than android, and hides them from the user.

The OS could be a bit more informative if an app repeatedly crashes a few times in a row. Regular users won't understand why, for instance, an app keeps returning to the home screen one second after starting it, and it doesn't help if they repeat launching the app over and over.

  • 2 months later...

I had an iPod touch.. I had to restore it so much it kept crashing.. In the end I scrapped it (hey it was only 2nd gen) and I got a Samsung galaxy ace, it works perfectly, it updates well, never had a problem

P.s the ipt probably due the the fact I was tinkering with the os but on the stock os, it crashed definitely more than once s month

As always.. we see proof that all that talk about how iOS is better is BS. Naturally these claims have always come from less than informed users and not backed up by facts.. as I have always said, from the very first iPhone until the last, iOS apps crashed more than Android ones.

One of the reasons is that developing apps for iOS/Obj-C forces you to keep track of your pointers and handle memory management and if a developer doesn't pay attention their app will eventually address a bad pointer or will try to garbage collect something that doesn't exist and the app will crash (though Apple uses their BS tactics by not showing any dialog boxes but simply kills the app when it crashes). Android apps on the other hand suffered from a different problem (Android handles garbage collection differently so this was not a huge issue), and this problem was the fact that some developers didn't use threads to offload main thread for UI and it caused apps to lock, showing the infamous (force close or wait dialog boxes). Since later versions of Android this practice has been addressed with many good things and Google introduced stuff like AsyncTask which allow you to easily run long-running processes on a separate thread while transfering results back to main UI thread with onPostExecute.

I'm glad someone came out and actually showed the numbers that destroy this Apple myth.

You can't really blame any particular OS for crashing when 95% of the time, the crash is being caused by a poorly written app, not the OS itself. I doubt very much that many of these "measured" crashes were just OS based, for either brand.

This was my first thought. plus how many more can be put down to user 'error' and not the phone?

99% of all those iOS crashes are caused by an app called Farmville.

For those with iPads and iPhones, just go to App store and download that app and run it.

I will change my name if you manage to run it even once at all. (v2.7 by the way.)

Ha ha ha listen to you all. So your personal experiences are good enough to make an assumption on a whole market. Shut up. I have both, IOS crashes sometimes and Android crashes sometimes. It's just all down to luck and how good the programmer is with the particular app. I would say I've had a harder time with IOS but would never say that Android is better although Android does seem to cope better when I'm throwing a lot of complex things at it.

One of the reasons is that developing apps for iOS/Obj-C forces you to keep track of your pointers and handle memory management and if a developer doesn't pay attention their app will eventually address a bad pointer or will try to garbage collect something that doesn't exist and the app will crash

And if your app is targeting iOS 4+, not using CoreFoundation, and is being compiled by the new LLVM compiler with Automatic Reference Counting enabled, this is (in most cases) a thing of the past.

When I say "iOS handles crashed better", what I mean is that it HIDES the fact that there is any kind of issue from the user. "Better" was a poor choice of word.

VERY poor. Just terminating the app without showing the user ANY kind of feedback as to why is the WORST imaginable way to handle an error!

VERY poor. Just terminating the app without showing the user ANY kind of feedback as to why is the WORST imaginable way to handle an error!

There are certainly some ways Apple could make it more apparent that an app has crashed, but I find a "This app has crashed" or bug reporter modal dialog to be more annoying than just saying nothing. I'm usually aware that the app has crashed. A dialog just adds an extra step in between me and getting the app launched again.

hmm. Don't think I've experienced more than a couple crashes on my Desire HD but I thought iOS didn't crash at all for some reason.

are you being serious?? Why would ever think that, did you think iOS was immune to crashes or something?

I've had several iphones, ipads and ipods as well as several android phones and tablets, without a doubt android apps crash 100x more times for me than anything on ios, I just had an android app crash on me a few minutes ago on my galaxy S2 phone "GasBuddy" and last night the google play store crashed while I was browsing, facebook and ebay crash about every other day at least once, haven't had many crashes on ios, I think the cardshark app may have crashed once on my ipad.

are you being serious?? Why would ever think that, did you think iOS was immune to crashes or something?

No.. but that was the rhetoric of all Apple fanboys. iOS is infallible and perfection of the mobile OS and Android is a turd that crashes non-stop. Well now we see what's what.

No.. but that was the rhetoric of all Apple fanboys. iOS is infallible and perfection of the mobile OS and Android is a turd that crashes non-stop. Well now we see what's what.

Rhetoric from a few iOS users and then wrapped in hyperbole and shot right back to ALL iOS users. Way to get back at em' bro! That will teach them.

This topic is now closed to further replies.
  • Posts

    • Interesting image choice... reminds me of the human centipede poster
    • Get $50 of aloSIM Mobile Data Traveler eSim credit for just $24.97 by Steven Parker Today's highlighted deal comes via our Apps + Software section of the Neowin Deals store, where you can save 50% off aloSIM Mobile Data Traveler Lifetime eSim Credit: Pay $24.97 for $50. Stay connected affordably in 120+ countries/regions with your own lifetime eSIM! An eSIM is a digital SIM card. It's basically just mobile data. Once it's activated on your device, it can connect you to data networks in other countries – giving you an internet connection with NO roaming charges. With aloSIM, you can load prepaid eSIM data packages onto your phone, tablet, or computer. Your lifetime eSIM never expires, so it's yours forever and there are never any monthly charges. You'll get $50 in eSIM data credit, which is almost always enough to cover all your data roaming needs for a full year. But if you run out of data, you can always top up your lifetime eSIM and stay connected internationally. Pay $24.97 for a lifetime eSIM with $50 in travel data credit Use your eSIM to join data networks in 120+ countries Install your lifetime eSIM on a compatible device to roam on local data networks Your lifetime eSIM never expires, and can be topped up with more data anytime Many data packages cost as little as $4.50 and last 7 days. Depending on the package you choose, the length of time varies. Good to know Length of access: lifetime For NEW customers only Instant digital redemption Once you add your $50 credit to your aloSim account you have up to 12-months to use it — after that your credit will expire When you pay for a data plan you also get a free phone number (via Hushed) for the same duration of your plan that was purchased - IE 7 day eSim plan gives you a free 7-day phone number Purchased coupon must be redeemed and used within 12 months This deal is not stackable (one offer per aloSIM account) A $4.50 data package will last 7 days The data DOES expire, and you WILL NOT have any leftover data for your next trip unless it takes place within the validity period. While the eSIM never expires, the actual data package is only valid for the length of time stated at purchase (i.e. seven days after activation, 30 days after activation, etc.) So if you buy a seven-day package and only use a tiny bit, that package is still going to expire after seven days. Access options: mobile (check compatibility) Max number of device(s): 1 Updates included Here's the deal: This aloSIM Mobile Data Traveler eSim $50 Credit normally costs ... $50, but it can be yours for just $24.97 for a limited time, a saving of $25 (50% off). For specifications, and license info please click the link below. Get this aloSIM Mobile Data Traveler eSim for just $24.97 (was $50) Although priced in U.S. dollars, this deal is available for digital purchase worldwide. Support queries If you have queries or need support for any of the Neowin Deals, please use the contact form here. Neowin Deals are managed and sold by StackCommerce who represent Neowin on an affiliate basis. Why we post these deals We post these because we earn commission on each sale so as not to rely solely on advertising, which many of our readers block. It all helps toward paying staff reporters, servers and hosting costs. So for those that keep moaning and complaining, be thankful we're still online for you to even do that. Other ways to support Neowin Whitelist Neowin by not blocking our ads Create a free member account to see fewer ads Make a donation to support our day to day running costs Subscribe to Neowin - for $14 a year, or $28 a year for an ad-free experience Disclosure: Neowin benefits from revenue of each sale made through our branded deals site powered by StackCommerce.
    • WordArt was cool. We now have color fonts as a substitute although Word only supports COLRv0 and COLRv1 (Fraud OS 11 only). The OpenType SVG color font format needs to be supported by Office. Adobe's apps support it
  • Recent Achievements

    • First Post
      DrWankel earned a badge
      First Post
    • Reacting Well
      DrWankel earned a badge
      Reacting Well
    • Week One Done
      Supreme Spray LV earned a badge
      Week One Done
    • One Month Later
      Genuinetonerink- Dubai earned a badge
      One Month Later
    • Week One Done
      Genuinetonerink- Dubai earned a badge
      Week One Done
  • Popular Contributors

    1. 1
      +primortal
      497
    2. 2
      +Edouard
      158
    3. 3
      PsYcHoKiLLa
      90
    4. 4
      Steven P.
      74
    5. 5
      Michael Scrip
      72
  • Tell a friend

    Love Neowin? Tell a friend!