I often press the 'b' key instead of 'space' - could you identify and auto-correct words likebthis or likevthis
I am constantly hitting the 'b' key instead of the 'space' key, so my words often lookbsomething likebthis - could you write some logic that can recognize two or more valid words separated by a 'b' character, and auto-correct it?
Catch when a space is missing between words. Swiftkey should be able to split such combos into two words rather than leaving as one word (and should never add to personal dictionary in such cases)
The space bar is way too small. Most of my typos come from trying to hit the space bar but i wind up hitting the letter v or b
Make it where it can recognize v and billed in between words. I hit those a lot with my right thumb instead of space.
I have big thumbs and I get a b or an n instead of a space when typing fast. Please add an algorithm that increases the likelihood of a space at the end of recognized words.
It would be nice if Swiftkey was able to provide word suggestions which take into account the mis-typing of a space, i.e. "ofvit" might actually be "of it".
I often find myself hitting the "b" and "v" keys instead of the spacebar when I'm typing quickly -- I'm sure I'm not the only one. So I'll get sentences like "The quickvbrown fox jumped overbthe lazybdog." Swiftkeys remarkable deciphering abilities almost always fail to recognize the two real words separated by the extra character -- could you somehow make the algorithm more sensitive to this type of error?
SwiftKey 3 has a new feature called Smart Space, which corrects when you type likethis, or likebthis, or even luketjis
You can get SwiftKey 3 here https://play.google.com/store/apps/details?id=com.touchtype.swiftkey
This may have fixed the problem for two words... but can you please extend this to many more words.
I often findbmyselfbhavingbtypedblikevthis, and then I have to literally delete everything and go back and retype... exremely annoying.
I do this with the y as I tap on the word above to enter... :S
Put chinese on it please then it will be perfect, thanks...
I've done this a million times and It drives me nuts.
Sebastian Di Mateo commented
Nice!! Starting trial period NOW
Craig slingerland commented
SwiftKey 3 solved it. Upgrade
The link isn't working for me.
Even though we've tripled our server capacity, interest in SwiftKey 3 has temporarily placed our servers under a lot of pressure. We'll get it back up at our earliest opportunity.
Thanks very much for your patience!
Add me to this list as well. Stopped recommending swiftkey to people until this is fixed. Extremely frustrating. Ditch the "swiftkey" key as well.
I DO THIS EVERY SINGLE TEXT AND IT'S DRIVING ME INSANE. ITS TEARING MY FAMILY APART, IM LOSING ALL OF MY FRIENDS. MAKE IT STOP PLEASE
No, but seriously, it frustrates me to no end. This is literally the only problem I have with Swift Key. I am *this close* to switching to a different keyboard because it messes up my texts so much.
Wai Fung commented
*spacebar... That was an autocorrect by SwiftKey!
I agree. The letter v is my most common press instead of the space bar. c and b are the next common mistakes pressed instead of the spacebar. I know my iPad splits words that need to be spaced so it's definitely obtainable. Please fix soon. Thisvis the only flaw in my daily usage.
Jason Pyktel commented
I agree I have it sometimes where push wrong letters and creates a word that doesn't even exist and where if write like andgoing together it won't automatically space between them.Therefore creating extra double work having to travel back and fix applying space between word's.
In addition to detecting words separated by the "be key" other letters like n and v and the period key should be included as well
God I need this so badly. It's incomprehensible to me that this isn't already a feature. If I was creating a keyboard that predicted/corrected, this would be one of the FIRST things to add, not a suggested feature. I want to uninstall it every time it happens to me. FIX THIS PLEASE.
Andy L commented
I have the exact opposite problem, I keep hitting the space bar instead of the C, V, or B buttons. What is extra annoying about this is that it tends to mess up the prediction because now the space bar has turned my single word into two wrong words instead of 1 that hopefully would be corrected by the prediction.
I think Celly's idea is the best one to solve this problem.
I am really bothered by this as well, but I don't think that editing the auto correct engine is the way to fix it. The solution is to add couple pixel rows of "dead space" between the zxcvbnm row of the keyboard and the bottom administrative keys. Just separate the keyboard from the bottom row slightly, or just make the bottom row of keys smaller to allow for dead space without increasing the vertical footprint of the keyboard.
Great Idea. Love this