Corrections should take into account the number of characters
expipiplus1 TESTER ·
What would you like?
In the example screenshots the corrections are all different number of characters than what's typed. It's much more likely that a user misplaced their finger than didn't hit the keyboard at all, so words with the same (or similar) number of characters should be scored much more highly
For example typing chwrscters shouldn't suggest Chr char chew like in the screenshot
Of course if a word is swiped and not tapped this is different
App settings
Languages: en-gb, ja (active: en-gb) Full Access: on LAB: Scrollable suggestions on, Period instead of space on Settings changed on this phone (61): activeLanguage=en-gb activeLanguageItem=custom barMenuHidden=custom barMenuOrder=custom barToolsEnabled=off boldKeyText=off commaKeyEnabled=on customColorsEnabled=on customGlassBackground=off customKeyBg=#6B6B6B customKeyOpacity=0.36 customKeyboardBg=#1C1C1E emojiBarEnabled=off emojiBarMode=symbols emojiKeyEnabled=off emphasizeKeySymbols=on enabledLanguages=[en-gb,ja] extendedAccents=on hapticEnabled=off hapticIntensity=0.59 hapticSharpness=0.56 hintsOnlyWhileTyping=off jaFlickOnly=on jaHalfWidthSpace=on keyAffordanceIconsEnabled=on keyLabelScale=1 keyPressAnimationEnabled=on keyPressAnimationSpeed=fast keyPressAnimationStyle=jump keyPreviewEnabled=on keyShadowEnabled=off keyShadowStyle=soft keySoundEnabled=off keyboardSkin=custom languageExtraKeys=off languageItems=custom languageKeyEnabled=off languagePairs=[] longPressDelay=0.20 longPressHintsMode=all multilanguageEnabled=off nativeExactColors=on nativeReturnKeyColor=on numberRowEnabled=on oneKeyboardSize=off periodKeyEnabled=on predictionEnabled=on returnToLettersAfterSymbol=off scrollableSuggestionsEnabled=on singleActiveLanguage=on smartDashes=off stockSymbolLayout=off straightApostrophes=on straightQuotes=on suggestionBarHidden=off suggestionFramingEnabled=off swipeToTypeEnabled=on swipeTrailCustomColor=off swipeTrailStyle=rainbow urlLayoutEnabled=off widerLetterKeys=off
Discussion
Sign in to comment or vote.
Very interesting analysis!
@expipiplus1 the length scoring was fine, the problem was that a backspace inside the word (or going back into it after a space) threw away where you touched for every letter, so the engine only had the letters to go on and matched the start of the word. Fixed for build 462 and in 2.2.1 on the App Store: the touches now survive the backspace, and chwrscters gets corrected to characters.
@expipiplus1 ?
Looks like an improvement thanks!