News for hackers. Stuff that matters.
Re:WWDC 2011 Prelude by gfodor on Sunday June 05, 2011 @09:46PM (#2623394)
Here's something that's been broken in iOS since v1.0 that I hope they fix: autocorrect. I was going to write a blog post about this but I'll just write a small version here.

Problem 1: Autocorrect is by definition an algorithm that makes mistakes. Hence, it should be an 'opt-in' UX. Currently, it's 'opt-out', ie, I can type a word that's perfectly correct, and the computer can "overrule" me and replace the word I just typed. This is horrendous. If I make a typo, that's my fault and I can only get mad at myself. If the computer makes a typo (ie, replaces my text with text I don't want without me telling it to) then that's inevitably frustrating.

Problem 2: The autocorrect bubble appears on the screen where the cursor is. This makes it so that I cannot develop muscle memory for the mechanism to de-activate autocorrect.

Problem 3: The bubble has the word it's going to replace with as well as an "X" -- the naive user will think that tapping the bubble will activate the word, and tapping the X will remove the bubble. It turns out, that tapping the word itself behaves the same as the "X".

Problem 4: Combine 1 & 2 and you realize that autocorrect as implemented right now necessarily makes it so I constantly have to be looking at both the keyboard and the cursor at the same time as I type. Every letter I type I need to "double check" at the cursor point to confirm iOS is not about to overrule me when I wack the spacebar. Then, if it turns out that I catch the computer doing something wrong, I have to remove my hands from the keyboard, and tell it "no, bad computer." On iPhone, this is barely tolerable because of the small screen. On iPad, it is a nightmare.

It amazes me Apple got this one so wrong since they usually don't miss these details. Here's some alternatives:

Proposal 1: Add a button to the keyboard to cancel the autocorrect and show the word if one is about to be blasted in over my typing. Basically move the "bubble" into the keyboard. This at least will make it so I don't have to watch the cursor like a hawk as I type.

Proposal 2: Proposal 1 + make it opt-in. So the new keyboard key is one-click to activate the word as opposed to deactivating the autocorrect for that word. (I think this is how Android does it?)

Proposal 3: Leave the UI as is but make the bubble opt-in (tap to replace) instead of opt-out.

Of course there are other ways to deal with this and they all involve tradeoffs. But it's clear to me that since I've owned an iPhone now since they first came out and I'm still frustrated by the autocorrect clearly there's a better solution out there.

Re:WWDC 2011 Prelude by philwelch on Sunday June 05, 2011 @10:56PM (#2623514)
Autocorrect works the way it does to optimize for the average case, and if you type very very fast on the keyboard and ignore any typos you make, autocorrect simply fixes them as you go. I've actually found it one of the better thought out parts of the system. Of course it makes mistakes but in my experience it fixes more than it breaks.
Re:WWDC 2011 Prelude by gfodor on Sunday June 05, 2011 @11:37PM (#2623591)
It all comes down to frustration. Having autocorrect "fix" things that aren't broken say 1% of the time, consistently, forever, is a constant frustration that I have no way to remove without either turning it off or changing the way I type (by watching the cursor for the bubble to come up.)

On the other hand, I've noticed simply turning autocorrect off results in less overall frustration, despite less efficiency at first, since the mistakes I make are my own and its my responsibility to improve my typing accuracy so they approach zero.

Re:WWDC 2011 Prelude by britta on Monday June 06, 2011 @04:37AM (#2624104)
Yeah, I get irritated when autocorrect automatically "fixes" unusual words I wanted to type, but it's also nice to have correction available. So I'm really happy with ManualCorrect on my jailbroken iPhone - it makes it just correct when I tap the suggestion, instead of automatically. Not a real solution, but nice for my particular case.
Re:WWDC 2011 Prelude by thought_alarm on Monday June 06, 2011 @01:28AM (#2623799)
I agree that the iPhone autocorrect is utterly frustrating and asinine. It is the worst aspect of the iOS platform. And it's even worse on the iPad, because the text and the autocorrect UI are that much further away from the keyboard.

The problem with disabling autocorrect is that you no longer get the obvious corrections: i -> I, dont -> don't, etc. And even if you leave autocorrect enabled, the iPhone may decide to stop doing those obvious corrections. It's just a complete mess.

Let's not forget that the iPhone also has no way for the user to add their own corrections or create custom text expansions.

Apple needs to separate the basic text replacement from the more advanced (and problematic) predictive auto-correction. The corrections need to be utterly consistent, easily undoable and redoable, and all without leaving the keyboard.

I think for anyone who's used a BlackBerry or, say, TextExpander on the Mac, it's obvious what Apple needs to do to solve the problem. And I really hope they do, because right now iOS devices are not really suitable for typing anything longer than a single sentence.

Re:WWDC 2011 Prelude by philwelch on Monday June 06, 2011 @03:24AM (#2624002)
"Let's not forget that the iPhone also has no way for the user to add their own corrections or create custom text expansions."

That's not true. I've noticed the iPhone autocorrect add words to its dictionary after I use them a few times.

Re:WWDC 2011 Prelude by Jgrubb on Monday June 06, 2011 @07:53AM (#2624380)
Mine, however, just doesn't seem to catch on to the fact that I mean fuck instead of duck, no matter how many times I use the word.
Re:WWDC 2011 Prelude by uxp on Monday June 06, 2011 @12:20PM (#2625234)
After typing "fuck", which gets replaced to "duck" when you continue on, backspace to the end of the word, and iOS4 will hover a new bubble that "asks" if you would like to undo the correction, as well as list any other suggestions that may be relevant for that case.

This is a quick way to train the algorithm into learning your spelling habits.

Re:WWDC 2011 Prelude by iaskwhy on Monday June 06, 2011 @03:47AM (#2624037)
But it is much better now. I noticed when it autocorrects something you can just touch the changed word and it will show a bubble with the previously typed word. What annoys me here is that it doesn't work for all the words, maybe just the last three or something like that... I also hate how it autocorrects correct words into wrong words and I can't change that, it is so annoying.
Re:WWDC 2011 Prelude by jasonlbaptiste on Monday June 06, 2011 @02:17AM (#2623867)
fyi, autocorrect has made its way into lion..ios style. It's fucking miserable.
Re:WWDC 2011 Prelude by ugh on Monday June 06, 2011 @02:21AM (#2623874)
Nah, it’s not. You can actually use the keyboard to dismiss suggestions.
Re:WWDC 2011 Prelude by weaksauce on Sunday June 05, 2011 @10:52PM (#2623504)

    Problem 3: The bubble has the word it's going to replace with as well as an "X" -- the naive user will think that tapping the bubble will activate the word, and tapping the X will remove the bubble. It turns out, that tapping the word itself behaves the same as the "X".
Actually, pressing the x will indeed remove the bubble and not force the word correction. Maybe you are not pressing the x correctly?
Re:WWDC 2011 Prelude by ugh on Sunday June 05, 2011 @11:11PM (#2623547)
Touching the word will also remove the bubble. You don’t have to touch the X. That’s the problem.