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…
Keybee: A Keyboard Designed for Smartphones
41–50 of 103 posts
Re: Keybee: A Keyboard Designed for Smartphones
#42> Keybee Keyboard increases more than double the keysize thanks to its hexagonal structure. No waste of pixels. It may be efficient, but it's using more screen space; I'm not sure that's a win.
Re: Keybee: A Keyboard Designed for Smartphones
#43Re: Keybee: A Keyboard Designed for Smartphones
#44Earlier quoted context omitted.
There were a _lot_ of programs in this space, one of the more interesting was AlphaTap! by Network Improv: http://networkimprov.net/alphatap/light.html c.f., the research project: https://dasher.zone/docs/getting-started/how-to/ For my part, I just write text out using a Wacom stylus on my Note 10+
>Type by zooming infinitely into a prediction model Holy crap that's a trippy GIF
Re: Keybee: A Keyboard Designed for Smartphones
#45This 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.
Re: Keybee: A Keyboard Designed for Smartphones
#46'may be able to'? How is this not knowable? Do I have to wait for effect systems to gain popularity before installations make sense?
Re: Keybee: A Keyboard Designed for Smartphones
#47Re: Keybee: A Keyboard Designed for Smartphones
#48No swyping and no autocorrect make it DOA
Re: Keybee: A Keyboard Designed for Smartphones
#49> Keybee Keyboard increases more than double the keysize thanks to its hexagonal structure. No waste of pixels. It may be efficient, but it's using more screen space; I'm not sure that's a win.
same thought, we've been using smartphones since 2 decades now, and not just we dont have a problem with qwerty, but anything new will be requiring more cycles to get accustomed to
That's to say, I'm writing this comment on my Android phone without looking at the keyboard.
QWERTY is in my muscle memory in such a way that words have become writable as single stroke characters.
I really, really doubt this Keybee thing can be an improvement over that in any way.
Re: Keybee: A Keyboard Designed for Smartphones
#50Earlier quoted context omitted.
same thought, we've been using smartphones since 2 decades now, and not just we dont have a problem with qwerty, but anything new will be requiring more cycles to get accustomed to
I can touch-type with flow typing in GBoard at this point. That's to say, I'm writing this comment on my Android phone without looking at the keyboard. QWERTY is in my muscle memory in such a way that words have become writable as single stroke characters. I really, really doubt this Keybee thing can be an improvement over that in any way.