Some of the more annoying things about Google keyboard, is when swipe fails to activate.
I think swiping is really pivotal to mobile input. I've been tempted to run some analysis and try find a keyboard layout that minimises errors, gives greater accuracy and speed of input, etc. But it is a big project. I want to keep the 3 row layout/size as well, just rearrange the keys for swiping. ( I have seen some keyboards try to promise effective swiping but they are too obtuse and different for me to feel comfortable with using rather than just rearranging qwerty)
Review of FUTO: It's alright. The swiping has a little bit of inaccuracy but that is just due to noticing it versus Google's data harvesting. The voice input is also something that I use and it seems okay with Futo but it relies on me saying the whole sentence which it will then analyze and put in the grammar. That is pretty good and it does a really good job of it. I am used to voice talking and correcting as I go, so this will be something to get used to. All in all, I like it. And I will try it for a little while.
One of the comments raises the main concern that I have as well, which is the ambiguity, in and on are fairly similar, but there's also other combinations that are way worse. Wide and worse being one of them. We almost want to encode the direction of the letters from each combination, and maximize the angular distance but minimise the magnitude of direction.
I used to swipe, but I moved off it. Two thumbs are twice as fast as one for me, and SwiftKey, for all its faults, is magic in understanding what you meant to tap.
I literally just blindly tap around in the general vicinity of the key I want to press, and SwiftKey outputs the right word.
All I word is a keyboard that does that, without the bullshit. SwiftKey is extremely infuriating because it's 99% close to perfect, but it has some ridiculous things like always replacing "my" with "NY" and there is absolutely no way to make it forget the word "NY", no matter how many times you say "forget this word and never predict it".
How hard can it be to add word deletion from the dictionary?! It really annoys me how close it gets to perfection but shoots itself in the foot by word deletion not working.
FUTO, please, please make a SwiftKey that works. I'll pay you $20 for a lifetime license.
Some of the more annoying things about Google keyboard, is when swipe fails to activate.
I think swiping is really pivotal to mobile input. I've been tempted to run some analysis and try find a keyboard layout that minimises errors, gives greater accuracy and speed of input, etc. But it is a big project. I want to keep the 3 row layout/size as well, just rearrange the keys for swiping. ( I have seen some keyboards try to promise effective swiping but they are too obtuse and different for me to feel comfortable with using rather than just rearranging qwerty)
Review of FUTO: It's alright. The swiping has a little bit of inaccuracy but that is just due to noticing it versus Google's data harvesting. The voice input is also something that I use and it seems okay with Futo but it relies on me saying the whole sentence which it will then analyze and put in the grammar. That is pretty good and it does a really good job of it. I am used to voice talking and correcting as I go, so this will be something to get used to. All in all, I like it. And I will try it for a little while.