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

    • You're absolutely right! No reason in hell these should be on the road!
    • They aren't going to want to. Most would just go with the 17 Pro and save money. Why would they want to spend $300 for basically the same thing? It's not worth it if there are hardly any changes from year to year.
    • 24H2 rolled out to the Release Preview Channel in early June 2024, so this coming a bit later in the Experimental Channel (formerly Dev) doesn't really say much more than earlier H2 releases that came out in October. I am not sure what the thinking is here by putting it in Experimental, one would think that the 26H2 stamp means features are locked down and it's now bug tested until October? I don't even pretend to understand Microsoft's strategy for Windows Insider Program though
    • Nothing Ear (a) and CMF Buds Pro 2 with active noise cancellation drop to lowest price ever by Fiza Ali With Prime Day 2026 scheduled to run from Tuesday 23 to Friday 26 June, Amazon has already begun rolling out early access offers ahead of the main event. Particularly, Nothing Ear (a) and CMF Buds Pro 2 wireless earbuds have dropped to their lowest price ever with limited Prime deal offering 33% and 24% discounts, respectively. Nothing Ear (a) are equipped with 11mm dynamic drivers featuring a PM1 + TPU diaphragm. For noise control, the earbuds offer active noise cancellation (ANC) of up to 45dB across frequencies reaching 5,000Hz. The smart ANC algorithm adapts to surrounding noise levels, while a Transparency Mode allows users to remain aware of their environment when needed. Connectivity is handled via Bluetooth 5.3, with support for AAC, SBC, and LDAC audio codecs. Additional features include IP54-rated earbuds for dust and splash resistance, paired with an IPX2-rated charging case. Furthermore, users also benefit from pinch controls, in-ear detection, Google Fast Pair, Microsoft Swift Pair, dual-device connectivity, and a low-latency mode designed for gaming and video playback. The Nothing X app unlocks a range of customisation options, including a personalised equaliser, bass enhancement, control remapping, ear tip fit testing, firmware updates, dual-device management, a Find My Earbuds feature, and low-latency mode settings. When it comes to the battery, the earbuds house a 46mAh lithium-ion battery, while the charging case contains a 500mAh cell. With ANC disabled, users can expect up to 9.5 hours of playback from the earbuds and up to 42.5 hours in total with the charging case. With ANC enabled, battery life is rated at up to 5.5 hours per charge and up to 24.5 hours combined with the case. Finally, fast charging is also supported that should provide up to 10 hours of playback from a 10-minute charge with ANC turned off. Nothing Ear (a) Wireless Earbuds (Black): $53.20 (Amazon US) - 33% The CMF Buds Pro 2 feature a dual-driver audio system consisting of an 11mm bass driver and a 6mm micro-planar tweeter. The earbuds use PU (polyurethane) and PET (polyethylene terephthalate) titanium-coated diaphragms and are tuned by Nothing to deliver balanced audio performance. They further support active noise cancellation of up to 50dB across a frequency range of up to 5,000Hz, and noise control features include a Smart ANC algorithm, Adaptive ANC, Transparency Mode, and Clear Voice Technology 2.0. For calls, the CMF Buds Pro 2 use a total of six microphones and feature an environmental noise-cancelling algorithm, Clear Voice Technology 3.0, and Wind Noise Reduction 3.0 that should improve voice clarity during conversations. Furthermore, when it comes to the connectivity, it is provided through Bluetooth 5.4. Additional features include an IP55 rating for dust and water resistance, Google Fast Pair, Microsoft Swift Pair, in-ear detection, a low-latency mode, and a Find My Earbuds function. Moreover, through the Nothing X app for Android and iOS, users can access custom EQ settings, a bass enhancement algorithm, customisable controls, Find My Earbuds, low-latency mode, dual-device connectivity, an ear tip fit test, and firmware updates. The earbuds contain a 60mAh rechargeable lithium-ion battery, while the charging case houses a 460mAh battery. A full charge of the earbuds and case via USB-C should take approximately 85 minutes, while the earbuds alone should be fully recharged in the case in around 60 minutes. Battery life is rated at up to 11 hours of playback on a single charge and up to 43 hours with the charging case when ANC is turned off. With ANC enabled, playback time is reduced to up to 6.5 hours on the earbuds and up to 26 hours with the charging case. Talk time is rated at up to 6 hours on the earbuds and 25 hours with the case with ANC disabled, or up to 4.8 hours and 18.6 hours, respectively, with ANC enabled. CMF Buds Pro 2 Wireless Earbuds (Dark Grey): $37.05 (Amazon US) - 24% Good to know This Amazon deal is U.S. specific, and not available in other regions unless specified. We only use first-party seller links (at the time of article publishing); ensure that you purchase from a first-party seller link only. Check out Today's Deals on Amazon | or our recent tech deals. Become a Prime member (for Students or SNAP) via Neowin Get Prime Access - Prime for half price (for qualifying Medicaid, EBT, SNAP) Subscribe to Prime Video, Audible Plus, Music Unlimited or Kindle Unlimited via Neowin As an Amazon Associate, we earn from qualifying purchases.
  • Recent Achievements

    • Collaborator
      ryansurfer98 went up a rank
      Collaborator
    • Week One Done
      Eurosoft10 earned a badge
      Week One Done
    • One Month Later
      Eurosoft10 earned a badge
      One Month Later
    • One Year In
      Skeet Campbell earned a badge
      One Year In
    • One Month Later
      Sharbel earned a badge
      One Month Later
  • Popular Contributors

    1. 1
      +primortal
      542
    2. 2
      +Edouard
      186
    3. 3
      Michael Scrip
      77
    4. 4
      PsYcHoKiLLa
      76
    5. 5
      Steven P.
      71
  • Tell a friend

    Love Neowin? Tell a friend!