Improved prediction based on context / previous word
At present EFkey doesn’t seem to use the preceding word to help decide what the swiped word is leading too a higher number of errors.
For example if I swipe the sentence "Just because I’m ill doesn’t mean I’ll be ill all the time” in the native keyboard and SwiftKey I get a 100% success rate. However swiping the same sentence in EFkey gets me "Just because I’m I’ll doesn’t mean I’ll be I’ll all the time"
Similarly the native keyboard gets "brush dust off the surface of the desk” whereas EFkey gets "brush dust of the surface of the desk". SwiftKey fails this one though for me.
I wonder if the other keyboards are tracking frequency of word pairs rather than just scoring individual usage.
Discussion
Sign in to comment or vote.
Except the stock keyboard, the others behave similar in these scenarios. Sometimes, they get it right and sometimes wrong. But stock gets these always right.
@Unmutual there were two problems behind this. After a contraction like I'm, the swipe decoder only saw "m" as the previous word, so it had no context at all. And ill/I'll (same with of/off) is literally the same swipe path, so it just picked the more common word every time.
Both are fixed. It'll be in build 425 on TestFlight and in 2.1.3, the next App Store update. Your sentence now comes out as "Just because I'm ill doesn't mean I'll be ill all the time", and "brush dust off the surface" keeps the off. If the guess is wrong, the other word is still in the bar.
One case I left alone on purpose: after "turn" it still goes with "of", because "turn of" (turn of the century) is common enough that forcing "off" would break it for other people.
Great. Thanks!
@efko much better. Good job! 👏👏