Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.

MacRumors

macrumors bot
Original poster
Apr 12, 2001
63,469
30,689



The United States Patent and Trademark Office recently published a new patent application originally filed by Apple last July, detailing a system in which the receiver of an iMessage could be notified when pieces of the message are scrambled incoherently by the company's autocorrect system (via AppleInsider). The patent isn't a proactive solution to enhance the sometimes spotty nature of autocorrect, but simply a way to let the person on the other end of the text know what's happening, and give each user tools to better explain what they meant.

Apple describes a new user interface that would highlight any words or phrases in a message that have been siphoned through autocorrect. The system wouldn't be advanced enough to reveal the specifically intentioned words the sender meant, but at least give the receiver a heads up about which parts of the text were corrected.

autocorrect-patent-1.jpg
A design of the sender-side UI


Parts of the patent reveal iterations of the idea that can streamline the clarification process, as well. For example, a description of the sender-side user interface includes a prompt that pops up -- after a user taps on the autocorrected word -- with an option to "Send clarification" to the receiver. The canned message fills out the phrase, "I sent [wrong word], but I meant [correct word]." If they want a complete do-over, the user could also just opt to re-send the entire message.

autocorrect-patent-2.jpg
A design of the receiver-side UI


On the receiver-side user interface, if the sender isn't opting to fix the issue themselves, the other person can "Request clarification" by tapping on the highlighted autocorrect word or phrase. The automated message is similar to the previous sender-side phrase, asking "You sent [wrong word]. What did you mean?"

If implemented in a future version of iOS, the autocorrect highlight patent could be similar to the way iOS currently underscores vague references to dates and times when users send and receive text messages. Apple's new patent could be slightly more helpful for most users than that feature, however, especially given the speed with which iPhone users have grown accustomed to texting on the device, and how frustrating it can be to realize autocorrect interfered with your message.

Like most patents, it's still advised to be wary of how long it'll take Apple to implement the autocorrect notification system into iOS, if it ever will. Still, it's easy to see how useful and streamlined such a feature could be, without completely taking out much of the humorous -- and sometimes awkward -- mishaps for which autocorrect has become famous.

Article Link: Apple Looks to Streamline Clarification of Awkward Autocorrect Messages in New Patent Application
 

jgelin

macrumors 6502a
Jul 30, 2015
904
1,073
St Petersburg, FL
I think this could work very well if they adapt it to be used on the watch, where we are relying on dictation to make our words and to be able to easily pick the message we sent on the watch and then edit it with its correct word would save a lot of time fiddling with creating a new message, and hoping that Siri understands what you mean in the second dictation as well.
 

ArtOfWarfare

macrumors G3
Nov 26, 2007
9,557
6,057
I feel that it would be vastly simpler to just fix autocorrect. I think if they fixed these two things, it would do away with 99% of false corrections by autocorrect:

#1: When I type a word that includes a capital in it, and it isn't the the first letter of the sentence, don't touch it. Ever. It's a name or trademark or something - it isn't ordinary English, leave it alone.

#2: When I type a valid English word, leave it alone. I don't care that it's statistically improbable that it's what I meant or whatever. AFAIK, I have never mistakenly typed one valid English word but meant another.

I remember making this suggestion when I was using my first iPhone, the 3GS, 7 years ago. I was so sure that Apple would swiftly fix it. Here we are, 7 years later with iOS 9, and autocorrect still sucks just as badly as it did then.
 

jgelin

macrumors 6502a
Jul 30, 2015
904
1,073
St Petersburg, FL
#2: When I type a valid English word, leave it alone. I don't care that it's statistically improbable that it's what I meant or whatever. AFAIK, I have never mistakenly typed one valid English word but meant another.
I am sure you have made the mistake between typing top and too before, just like everyone else, both of which are valid English language words....
I am sure/sire that the list goes on/no, and on/no and on/no.
 
  • Like
Reactions: autrefois

2457282

Suspended
Dec 6, 2012
3,327
3,015
I think that giving Autocorrect the ability to learn would be my #1 wish for imessage. I do tend to misspell the same words over and over. And it seems that it always wants to fix it with the same non-sequitur. If it looked at what I actually chose and remembered it for the next time, that alone would be a huge improvement. This patent is still valuable, but giving Autocorrect learning skills would be way better.
 

bushido

Suspended
Mar 26, 2008
8,070
2,755
Germany
i never use auto correct. i feel like by the time it suggests something or i pick the right suggestion i have already written the sentence on my own
 
  • Like
Reactions: KUguardgrl13

ArtOfWarfare

macrumors G3
Nov 26, 2007
9,557
6,057
I am sure you have made the mistake between typing top and too before, just like everyone else, both of which are valid English language words....
I am sure/sire that the list goes on/no, and on/no and on/no.

Um, no. I don't have that problem. I don't press my finger in the same spot when I mean different letters, so I don't mix up top or too (because there's an o right before the letter that could be mixed up).

I definitely don't type letters in the wrong order and end up with no when I meant on or vice versa.

I could imagine there are some situations where autocorrect's current behavior is better than its behavior if you make the changes I proposed, but they seem exceedingly rare to me.
 

gaximus

macrumors 68020
Oct 11, 2011
2,240
4,375
Um, no. I don't have that problem. I don't press my finger in the same spot when I mean different letters, so I don't mix up top or too (because there's an o right before the letter that could be mixed up).

I definitely don't type letters in the wrong order and end up with no when I meant on or vice versa.

I could imagine there are some situations where autocorrect's current behavior is better than its behavior if you make the changes I proposed, but they seem exceedingly rare to me.

Wow I've never meet someone who never makes a mistake while typing. You must be an amazing typist or type so slow that its impossible to make a mistake. Some words I type so fast from muscle memory I'll mix up the characters, even in my own name.
 

jgelin

macrumors 6502a
Jul 30, 2015
904
1,073
St Petersburg, FL
Wow I've never meet someone who never makes a mistake while typing. You must be an amazing typist or type so slow that its impossible to make a mistake. Some words I type so fast from muscle memory I'll mix up the characters, even in my own name.
Um, no. I don't have that problem.
Right, can't wait to see him at the World Typing Championship in the no Backspace round this year!
Gonna get the cup this time o_O
 

autrefois

macrumors 65816
For me, and other people I text with, we use * to indicate a word that we realize after the fact was autocorrected and shouldn't have been (or similar mistakes).

Example
Original message: Did you get the car?
Follow-up message: *card

I'm not a big texter, so I'm not sure about other people's experiences. That works well for me, except on the phone and iPad it takes three taps just to type an asterisk.

On the receiver's end, just typing that word or saying "huh?" or "??" or something similar works, doesn't it?

I don't think you need a whole "send/request clarification" system. In my experience at least, if they made the asterisk easier to get to, or introduced some other similar symbol that would work in many/most cases, I think that could really help. They can try to patent developing easy access to it if they want. :D
 
Last edited:

brunosh

macrumors regular
May 14, 2014
190
278
For me, and other people I text with, we use * to indicate a word that we realize after the fact was autocorrected and shouldn't have been (or similar mistakes).

Example
Original message: Did you get the car?
Follow-up message: *card

I'm not a big texter, so I'm not sure about other people's experiences. That works well for me, except on the phone and iPad it takes three taps just to type an asterisk.

On the receiver's end, just typing that word or saying "huh?" or "??" or something similar works, doesn't it?

I don't think you need a whole "send/request clarification" system. In my experience at least, if they made the asterisk easier to get to, or introduced some other similar symbol that would work in many/most cases, I think that could really help. They can try to patent developing easy access to it if they want. :D

Right? It's such a simple thing that worked since the beggining of sms'ing, so I think this is kinda useless.
 
  • Like
Reactions: autrefois

redscull

macrumors 6502a
Jul 1, 2010
849
832
Texas
I feel that it would be vastly simpler to just fix autocorrect. I think if they fixed these two things, it would do away with 99% of false corrections by autocorrect:

#1: When I type a word that includes a capital in it, and it isn't the the first letter of the sentence, don't touch it. Ever. It's a name or trademark or something - it isn't ordinary English, leave it alone.

#2: When I type a valid English word, leave it alone. I don't care that it's statistically improbable that it's what I meant or whatever. AFAIK, I have never mistakenly typed one valid English word but meant another.
Seriously. Those are my same top two recommendations. They seem so ridiculously obvious to anyone and everyone 5 minutes into typing on an iPhone that I'll forever be flabbergasted that it's not how it works. There must be a hard-headed Senior VP somewhere who just flat put his foot down, insisting the functionality remain stupid, despite every underling and QA in Apple telling him it's broken.

My number three: If you replace a word I typed with a Capitalized word, and I backspace it because autocorrect was wrong, don't preserve the damn capitalization. It's so annoying trying to fix both the miscorrection and the miscapitalization. In fact, I don't think capitalized words should even be a valid replacement for my typo'd word unless I spelled it exactly correctly and merely lacked the capitalization. Or my typo was itself capitalized, explicitly indicating that I want it corrected to a capitalized word.
 
Last edited:

redscull

macrumors 6502a
Jul 1, 2010
849
832
Texas
I am sure you have made the mistake between typing top and too before, just like everyone else, both of which are valid English language words....
I am sure/sire that the list goes on/no, and on/no and on/no.
too/top and sure/sire are ok examples, but no/on is clearly not. n and o aren't near each other. No one typos that. And regardless, I would much rather have to fix too/top or sure/sire myself in those rare cases I fat thumb it than the constant battle with autocorrect over all the other words I type out perfectly that it changes to whole other words.
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.