5 ms·
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
by anishgupta 7mo ago
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
- alterom 7mo agoI 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.
- skeledrew 7mo agoPeople 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.
- llbbdd 7mo agoQWERTY won't be replaced on phones until there is a full phase change in how people interact with their phones that absolves us of keyboards entirely. Anybody here who thinks otherwise is welcome to make an offer to buy my two decades of notes on the topic.
- alterom 7mo ago>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 be inserted through a simple combination of tap & swipe (we call it twipe) greatly reducing the number of touches for typing a text. For now the twipe is limited to the adjacent keys. Keybee Keyboard is swipe friendly. I am typing an entire word with one "twipe" on GBoard. Each word. I'm done with touchscreen input methods that require me to think about tapping letters. I don't think in individual characters, and I don't type in them either. Let me know if I can make it any clearer.
- viraptor 7mo agoAlso 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.
- alterom 7mo agoSwipe keyboard on Microsoft Lumias was better. 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.
- adzm 7mo agoI really want to see the visualization of words as the swipe typing patterns. I tried doing it on paper and realized I couldn't understand it just by looking but once I started visualizing it and swiping in my head I could start to get a feel for it. The tricky part is figuring out where in the keyboard the stroke begins
- papaly1983 7mo agoI also would like to implement all those texting algorithms but I need the help of the open source community at this moment. Cheers!.
- eviks 7mo agoWeird thing to say, why would a random port be peak efficiency that can’t be improved?