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

    • But the reality is it will work for people's needs, and they don't care about the technology that makes it. Clearly not everyone's needs, but that low end space where personal laptops were only used to type emails, watch content and browse websites, but they didn't want to do that on a small screen device. Heck, writing that out I can now see the connection and reason it'll do so well. Apple is about experience. If the experience is bad, they don't release it. Low end Windows laptop manufacturers up until this point have not taken that into consideration ever before, so slow laggy usage with brittle slimey plastic shells were common. I hope that the low end space at least creates better physical products that last a bit longer, and if Microsoft get their act together, they could also have a solid OS on such low end hardware that would actually make the experience work for what the hardware was intended for. The fact that the CPU is a "cellphone", sorry mobile phone processor is irrelevant. It's about the experience, and so far, that sounds quite solid.
    • Hello, Bonjour is Apple's implementation of a multicast-DNS service, which allows devices running Apple's software and/or hardware to find each other on your local network.  I believe the Windows version was last updated around 2010. If you do not need it, you can stop and disable the Bonjour service in the Services Control Manager (filename: SERVICES.MSC).  Once you have done that, the operating system will no longer attempt to load the service. Regards, Aryeh Goretsky  
    • This AMD RX 9070 16GB GPU that performs close to Nvidia 5070 is under $600 by Sayan Sen With the memory shortage that's prevalent nowadays, discounts are super-hard to get. As such we post good deals whenever they pop up. Recently, we covered a few great discounts on SSDs wherein you can get a 4TB TeamGroup NVMe PCIe Gen4 drive for just $400 thanks to a special coupon. If you want a faster product but don't need all that capacity, you can also opt for Samsung's 990 PRO 2TB that is on sale for its lowest price in over three months. Let's say though that you are on the hunt for a 1440p gaming card. In that case AMD's RX 9070 non-XT can help, and with its 16GB VRAM, you can also run AI models locally without worrying about bottlenecking (check out our recent 9070 GRE reviews for gaming and productivity to get an idea). The PowerColor Reaper variant of the RX 9070 is currently on sale for just $580 which is a very good price in the current state of affairs (purchase link under the specs table down below). The Reaper cooler on this 9070 uses a triple‑fan design with ring‑blade fans, paired with premium dual ball bearings to extend lifespan and reduce friction. "Intelligent" fan control allows the fans to remain idle at lower temperatures, only spinning up when the GPU is under load. A nickel‑plated copper base makes direct contact with both the GPU and memory modules, helping to spread heat evenly. PowerColor also applies Honeywell PTM7950 phase‑change thermal interface material (TIM), which fills microscopic gaps between the die and heatsink for more efficient thermal transfer. The fan shroud is shorter in height as the firm has made it such that it can be used in certain SFF (small form factor) cases. The technical specifications of the Reaper RX 9070 are given in the table below: Specification Value Stream Processors 3584 Units Video Memory 16GB GDDR6 Memory Speed 20.0 Gbps Memory Interface 256-bit Engine Clock Game Clock: up to 2070 MHz Boost Clock: up to 2520 MHz Bus Standard PCI Express 5.0 x16 Display Connectors 1 x HDMI 2.1b, 3 x DisplayPort 2.1a Maximum Resolution DisplayPort: 7680 × 4320 HDMI: 7680 × 4320 Board Dimensions 289mm × 111mm × 41mm 304mm × 127mm × 42mm (with bracket) Slot 2 Minimum System Power Requirement 600W Power Connectors Two 8-pin PCI Express Get the PowerColor Reaper RX 9070 at the links below (you get only a 90-day warranty on Woot): PowerColor Reaper Radeon RX 9070 16GB Graphics Card (RX9070 16G-A): $579.99 (Sold and Shipped by Amazon US) (Was: $700) PowerColor Reaper Radeon RX 9070 16GB Graphics Card (RX9070 16G-A): $559.99 (Sold and Shipped by Woot US) 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.
    • Are they marketed as an entry into astronomy or astrophotography? I do astrophotography. With big rigs, lots of computers, cables and headaches. I love it. And by learning this ridiculously complex hobby, I’ve learned about the objects I’m shooting. Astronomy followed from photography.
    • Microsoft confirms Recycle Bin bug across all versions of Windows by Usama Jawad A couple of days ago, we reported that the latest Patch Tuesday update has seemingly resulted in a lot of issues for many users, including OneDrive and Dropbox access problems, BitLocker recovery lockouts, and BSODs. Although Microsoft is yet to acknowledge these bugs, it has confirmed another, relatively smaller issue across all supported versions of Windows. In an update on its Windows Release Health Dashboard, Microsoft has confirmed that after installing June's Patch Tuesday update (KB5094126), you'll experience unexpected behavior when leveraging Recycle Bin. Basically, when you attempt to delete an item from the Recycle Bin, the confirm dialog will show you the internal file name of that content rather than the actual name. For example, the file may be named abc.png, but the confirm dialog will ask if you're sure that you want to permanently delete $Rxxxxx.png from the Recycle Bin. This is pretty much it for the scope of the bug itself; it just displays the wrong name in the confirm dialog. The correct name will be shown in the list view of the Recycle Bin and if you restore the file, it will return with the correct name as well. This issue affects pretty much all supported versions of Windows client and server, including: Client: Windows 11, version 26H1; Windows 11, version 25H2; Windows 11, version 24H2; Windows 11, version 23H2; Windows 10, version 22H2; Windows 10 Enterprise LTSC 2021; Windows 10 Enterprise LTSC 2019; Windows 10 Enterprise LTSB 2016 Server: Windows Server 2025; Windows Server 2022; Windows Server 2019; Windows Server 2016; Windows Server 2012 R2; Windows Server 2012 As things currently stand, Microsoft is working on a concrete solution that will be released in a "future" Windows update. It remains to be seen if the firm will wait till the next Patch Tuesday or roll out an out-of-band (OOB) fix. The good news is that commercial customers can deploy a workaround right now, but they will have to reach out to Microsoft Support for Business for additional details.
  • Recent Achievements

    • Week One Done
      Jordan Smith earned a badge
      Week One Done
    • Reacting Well
      BizSAR earned a badge
      Reacting Well
    • First Post
      AndreaB earned a badge
      First Post
    • Week One Done
      Huge Trailer earned a badge
      Week One Done
    • Week One Done
      Classifyskilleducation earned a badge
      Week One Done
  • Popular Contributors

    1. 1
      +primortal
      582
    2. 2
      +Edouard
      185
    3. 3
      PsYcHoKiLLa
      75
    4. 4
      Michael Scrip
      73
    5. 5
      neufuse
      64
  • Tell a friend

    Love Neowin? Tell a friend!