91–100 of 103 posts
When I go to enable it I get 'may be able to collect all the data you type, including ... passwords'. 'may be able to'? How is this not knowable? Do I have to wait for effect systems to gain popularity before installations make sense?
Very cool. The biggest questions someone skimming would likely be why the letters are in this order, and how this is consumed (eg ios app?). You may answer those details but they were not front and center to me.
Looking at the English keyboard and the English digraphs, it doesn't seem like the coverage is that well optimized. We are currently capturing 8.65% of the digraph weight, but just getting the top-5 would account for 5% by itself. I also feel like distance travelled is the wrong (or an incomplete) metric. Change in direction seems like a good proxy for mental or physical effort. To take it to an extreme, I'd be very…
I agree that distance is not a great metric. The maximum travel distance on a smartphone screen is already tiny. I'd say the best metric is accuracy or lack of amibiguity, something like average confidence level that any given swipe means a particular word and not another. (This is assuming swipe-based word entry, which I much prefer to anything tap-based.)
If Steve Jobs when he introduced iphone, added this keyboard and said this is how we should write, everybody would do it. Just sayin'...
Earlier quoted context omitted.
Wait this keyboard doesn’t support swipe typing? Hmmmm
Because is a huge effort to make a full swipe algorithm based on a potential custom layout and Keybee keyboard is still a one person project. Marco.
This is gonna be like Dvorak where eventually we all figure out that it’s not significantly faster and you had to re-learn how to type just to figure that out. I submit the idea that for most smartphone users, distance traveled and layout are not the limiting factor for typing speed.
> This is gonna be like Dvorak where eventually we all figure out that it’s not significantly faster and you had to re-learn how to type just to figure that out. Generally nowadays people don't learn Dvorak because it's faster, they learn it because it reduces finger travel and effort. Those factors apply here too.
This is gonna be like Dvorak where eventually we all figure out that it’s not significantly faster and you had to re-learn how to type just to figure that out. I submit the idea that for most smartphone users, distance traveled and layout are not the limiting factor for typing speed.
I find another factor that is not always discussed is comfort and how pleasant it is to use a layout. I know Dvorak is not much faster in the end but it is such a joy to use in comparison to Qwerty. I do wonder if it would be fun or just nice to use this hex-grid layout on a phone.
Earlier quoted context omitted.
>People riding horse buggies probably thought the same when powered vehicles first came about, and look at the world now. You won't know unless you give it a honest try. This is a ridiculous non-analogy. I'm flying a jet airplane, and you're telling me to give Ford Model T a try because you don't understand flight as a concept. Or, in this case, Flow typing. From Keybee's website: >Some syllables and some words can b…
Also gboard is the best keyboard for that. Nothing else implements a prediction model over a number of words as far as I can tell. Or if they do, they fail really badly at it.
I think Android is only catching up to it in the past 2-3 years.
Sadly, Lumias went the way of the dodo, and I don't have a need for that sort of input on something that's not a phone.
Whatever Microsoft put out as a keyboard app for Android is different, they didn't implement the same UX.
Out of the swipe keyboards I tried for Android, GBoard worked the best.