Naw, trying to fix the corrected correction for autocorrect is so annoying. Agreed with the computer scenario but with phone…… maybe if it was a flip phone, you have more con control with that, not a “smart” phone.
I’m going to just take a guess: Most people who have a problem with autocorrect type each letter individually by pressing each letter?
I almost never have an issue with autocorrect because I type in either of two ways:
Swipe typing, which is way faster than normal typing IMO. And on the occasion that there’s a collision with the swipe motion, all I have to do is press the incorrect word on the text, and select the correct one from a tiny list of three most common words with that similar motion. Never fails, very quick.
Typing each letter individually, but here I just start typing the beginning of the word, then I pick the suggestion from the top of the keyboard to complete the word without having to type the whole thing out. Also way faster than normal typing. Often using this method, I don’t even have to start typing the word at all, or just a single letter, or a couple of letters is enough.
In both cases, correcting is very fast. Much faster than corrections using a real, physical keyboard, which you said you would do. So really, logically I have no reason to be annoyed with autocorrect — and I am also actually not annoyed with it. 👍
I’m going to just take a guess: Most people who have a problem with autocorrect type each letter individually by pressing each letter?
Possibly. I’m in that group, for what it’s worth.
Was unaware that was even a thing. As a long-time touch-typist, doing this never even occurred to me. And I know how to use Palm Pilot Graffiti input, so I’m admittedly embarrassed here.
My vocabulary is broader than the auto-complete’s dictionary/prediction, so what I want to say isn’t even a suggestion more than half of the time. I’ve struggled with this since iOS 3, and most recently on Android. It’s never been very useful for me.
Then there is/was this feature that resizes key hitboxes on the fly, based on prediction. I’m unaware if that’s still a thing, but at the time, it absolutely screwed with my thumb-typing muscle-memory in the worst way. Until I learned about this, I was convinced that I was just garbage at hitting the keys, then I started seeing it mis-register keypresses when I looked closely.
From all that I think I see the problem. These systems are compromises for a huge range of different users and communication styles. So it’s going to be pretty mid for a lot of folks until (people like me) move to the middle where the software wants people to be. Were it not for the sake of clear, personalized, and expressive communication, I’d be on board with that.
I’m using whatever the stock keyboard is on Google Android. Since we’re on the topic, I’m open to suggestions. Especially if I’m going to re-train to swiping inputs.
It’s hard to pin down anything specific as an example. If I had to sum it up, its usually where I want to use a long word with a common root for others. There could be eight or so different ways to go for auto-completion, but my choice is seldom in the top three.
the stock keyboard is on Google Android. Since we’re on the topic, I’m open to suggestions.
Is the stock keyboard GBoard nowadays? That’s what I use. It has swipe typing built-in. But if you want more privacy, I’d try FUTO keyboard. It’s pretty darn solid IMO, especially for a FOSS and gratis keyboard.
Naw, trying to fix the corrected correction for autocorrect is so annoying. Agreed with the computer scenario but with phone…… maybe if it was a flip phone, you have more con control with that, not a “smart” phone.
I’m going to just take a guess: Most people who have a problem with autocorrect type each letter individually by pressing each letter?
I almost never have an issue with autocorrect because I type in either of two ways:
In both cases, correcting is very fast. Much faster than corrections using a real, physical keyboard, which you said you would do. So really, logically I have no reason to be annoyed with autocorrect — and I am also actually not annoyed with it. 👍
I hope this might help someone.
Possibly. I’m in that group, for what it’s worth.
Then there is/was this feature that resizes key hitboxes on the fly, based on prediction. I’m unaware if that’s still a thing, but at the time, it absolutely screwed with my thumb-typing muscle-memory in the worst way. Until I learned about this, I was convinced that I was just garbage at hitting the keys, then I started seeing it mis-register keypresses when I looked closely.
From all that I think I see the problem. These systems are compromises for a huge range of different users and communication styles. So it’s going to be pretty mid for a lot of folks until (people like me) move to the middle where the software wants people to be. Were it not for the sake of clear, personalized, and expressive communication, I’d be on board with that.
It’s been pretty great for single-thumb typing ever since it started being common, many years ago.
Could you give me an example of this? Also which keyboard do you use as input? iOS/Android?
I’m using whatever the stock keyboard is on Google Android. Since we’re on the topic, I’m open to suggestions. Especially if I’m going to re-train to swiping inputs.
It’s hard to pin down anything specific as an example. If I had to sum it up, its usually where I want to use a long word with a common root for others. There could be eight or so different ways to go for auto-completion, but my choice is seldom in the top three.
Is the stock keyboard GBoard nowadays? That’s what I use. It has swipe typing built-in. But if you want more privacy, I’d try FUTO keyboard. It’s pretty darn solid IMO, especially for a FOSS and gratis keyboard.