Doing an OTA update on day one in fifteen minutes is a big factor. Nerds/tech crowd can get through Android updates but for the average user it's an utter clusterf* of a nightmare.
More work goes into figuring out IF your Android device will be updated than goes into the entire iOS update process...
(Yes, I'm saying "don't buy non-Nexus devices." Not like that's a hard one to grasp, though.)
"But I had to wait four days" is really just...really? And that gets you frothy?
But even a glance at what version of Android is being used: http://developer.android.com/about/dashboards/index.html shows that over 2/3 of all Android Users are still on 2.x or before, and it's very likely that many of them will never have an opportunity to upgrade.
That gets me frothy. iPhones get 3 to 3.5 years of updates, and Android devices averaged on whole are getting what, 1.5 to 2 years? Maybe less, considering how many aren't being updated?
The answer of "only buy a flagship" is bunk. If Google supported that answer, they should cut out the cruft. But Android is more than flagships.
So I installed cyanogenmod 9.1 and I fell in love with my phone again. It's not perfect though but I don't think I'll ever want to buy a non-stock Android phone again...
So being a rather passionate Android guy I do recognize that there are very annoying problems with some Android devices. And installing cyanogenmod is way above the skill level of the average phone user (even though it's rather easy).
Sometimes I wonder if iPhone people experience the same kind of disappointments ... and when they do it makes me feel a little warm inside. I know it's not nice but I guess we all need to justify our own purchasing decisions to ourselves every now and then :)
Sometimes.
The iOS4 update on iPhone 3G was absolutely terrible, the phone became pretty much unusable. The 4.1 update made it less unusable, but the phone was never restored to its former snappiness (unless down-dated to iOS 3.1)
There's also the issue of updates being (at least somewhat) intentionally nerfed for older devices. Sometimes it's explainable by hardware or performance issues, even if a stretch, but other times it feels like complete arbitrary bullshit:
* for iOS3, 3G owners couldn't "view or create 'Invitees' on a Calendar event" while 3GS users could
* for iOS4 3G owners not only didn't get multitasking (acceptable considering the performance issues) but they didn't get the fast-switching UI and attached tools (orientation lock) or larger fonts in messaging applications (...) either
* for iOS4.2 3GS users didn't get the expanded set of text tones
* for iOS5, 3GS users didn't get location-based reminders (geofencing)
* for iOS6, neither 3GS nor 4 owners get turn-by-turn navigation or panorama mode; 3GS owners don't get offline reading lists
Oh, and to be honest as well, I don't hear many complaints from the iPhone crowd.
My own anecdotal Nexus experience (I own the Google updated GSM version): no crashes (although there was a brief syncing outage last night), updates are smooth and fast, and the whole "it just works" thing applies.
8 hours? What?
It probably goes without saying that iOS isn't for him.
But you're right about the error messages, when thing go wrong there are very few apps that will tell you about it.
I don't see a problem with just jumping back to the homescreen, most people will reopen the app right away anyway.
There's a lot of work to do in that field, and that's catching-up work more than improvements. It's much like discussing the Nexus One. Let's talk about it again in a year or two.
I would love something as dead simpel as an Iphone, but IOS is far too limited for my likes (especially lack of sideloading, intents and services).
On top of that, the UI design quirks are infuriating, and this is from a guy who's spent the better part of a decade mostly using a BlackBerry. (Trying iOS here, shortly. We'll see which sucks the least of the three...)
Android still hasn't lived up to its promise, and the software fit and finish is pretty lousy. Had I paid for this phone, it would certainly have gone back during the return window.