Hacker News new | ask | show | jobs
by petercooper 4401 days ago
all cite screen size as their main reason.

Just one data point, but it was "keyboard" by far for me. The iOS keyboard is horrible and very difficult to customize so I took a risk and switched at my last update (and FWIW, I'm finding Android streets ahead in terms of functionality). Digging the larger screen size is something that came later for me but would definitely be another reason not to go back for me now.

3 comments

I agree. I really appreciate the richer inter-app sharing on Android but the absolute deal-breaker for me is the keyboard. Android keyboards like TouchPal or Swiftkey are so much more efficient and user friendly than the 2007-vintage iOS keyboard I just get irritated every time I have to use an iPhone for more than five minutes. And that's just for English. For other languages with a lot of accented characters it's not even a contest. I've been living in Vietnam for a few years now and people often mistake me for a native when SMSing because I write properly accented Vietnamese, which is easy with Swiftkey, whereas most locals write a crippled shorthand because typing all the accents on an iPhone is such a chore.

I think Apple's not used to having competition as agile as Google. Maybe their slow-and-steady approach was enough for them to power past Microsoft but much more rapid evolution on the hardware and software front is going to be necessary if they want to beat the entire Android ecosystem. Let's see what they come up with next week.

People leaving for keyboard reasons are generally, and I hate the term, 'power users'. For 90% of the iOS customer base the keyboard works perfectly well, I'm not the biggest lover of it but I think it's reasonably solid for what it is and what it does.
I really liked the Swype keyboard on my Galaxy S, but I got over it. With any of these keyboards, I still naturally delay anything longer than a status text/email/tweet for when I'm back at my computer, or even iPad (part of it's having enough screen to see the email I'm replying to, or the other sections I've written).
I don't think this is necessarily true. Yes, people leaving for keyboard-feature reasons are power users. But there are other keyboard reasons.

For example, iOS7 totally broke the keyboard so that fast touch-typists just can't type on it any more. This doesn't matter on something small like a phone, but on an iPad it is super-frustrating. Apple fixed it somewhat in recent updates but it's still broken in a few basic ways, all having to do with the fact that the person who programmed the new keyboard doesn't know how typing works.

It is confusing enough that a non-power-user probably doesn't have a clear idea why typing sucks now, they just know that letters don't come out with the right capitals any more, sometimes extra spaces show up, and damn that shift key is confusing. etc. It is not so much "Android is better" as it is "iOS is not a nice experience any more".

There are similar things to do with web browsing. Web browsing is supposed to be one of the few things these devices specialize in, but on my iPad Air it is terrible. If I go to a web site with images on it and scroll down, most of the images don't load for a LONG time, leaving me with mainly a blank page. When iOS7 came out the browser crashed all the damn time. Now that is mostly fixed but it still crashes sometimes.

Meanwhile there are all these timing-based gestures that are thrown off by browser performance problems, leading to bad user experiences. For example, I want to scroll down a page, so I press on the screen, drag, and release. Well oops, some piece of JavaScript ran right then or something, causing the browser's timing to get confused (maybe it counts frames and only a couple of frames went by), so instead of a drag it interprets this as a tap, which for some reason causes me to select some garbage on the page that I don't care about. Well now I am in select mode and things get only more confusing from there (especially if more performance hitches are happening). This happens all the time.

When you can't even scroll down a web page reliably, and yet that is one of the main use cases you are selling your product for, you can't claim it is a luxury product. You aren't delivering a luxury experience so you can't charge a premium.

Apple has gotten away with this in the past, in similar situations, though, because of newness and shininess. As Marc Andreesen pointed out recently, for the first few years you could barely even make a call on an iPhone, and when you did it was super-frustrating. But still it caught on. I think this is just because it was so new and exciting and there weren't real competitors yet. Once the bloom is off that rose, in order to be perceived as a premium brand, you have to actually deliver quality. But Apple is not delivering quality with the OS, they are just delivering some kind of skin-deep attempt of an appearance of quality.

I consider iOS7 to be a huge misstep and a giant missed opportunity, much bigger even than Siri or Maps. I am not sure if fixing iOS7 would solve all Apple's problems, but it is where I would start.

However, I don't think the thesis of this article -- lack of UI features -- would be my first step. Because I don't agree with the article that iOS 7 is simple. In reality it's a mess, it just tries to appear simple. So the first step is making it really, actually simple, and make it deliver a solid, quality experience. Then you can think about adding UI features, which I would claim people don't care about as much.

This is pretty heavily anecdotal but my parents (late 50s) haven't had any issues with the iOS 7 keyboard. As they say, it Just Works. I think it's heavily dependent on user expectations.
Different strokes, I guess - I dread using my work Android phone's keyboard (or any of the 3rd party ones I've tried) whereas iOS's hit detection/autocorrection mostly feels like an extension of my brain/fingers.
As someone who switched recently, I find both the Samsung Keyboard on the Note 3 and the Google keyboard are light years ahead of the iOS keyboard even before considering the ability to use handwriting recognition in place of typing.
Like I said, though, "different strokes" ;) I've used an Android Phone with Google Keyboard and Swype as my daily driver for months at a time this year and was insanely relieved to use the iOS keyboard again. I found its predictions and the accuracy of the keyboard itself far more accurate, and the screen responsiveness in another league...
The day I find a device with handwriting recognition that works with my chicken scratch I will jump for joy.