"For the FITALY layout, we have obtained an average travel of 1.8, to be compared to an average travel of 3.2 for the QWERTY layout. (For prose, involving few numbers and symbols, the results are even better.)"
"Please use this idea! If you are a software developer, I urge you to consider adding this functionality to your product. My hope is that ten years from now, we won't have to laboriously tap out messages letter by letter, but instead will be able to zip them out quickly and efficiently with something like HexInput." -Sept2006
I loved the stylus on my Note 10 Lite so much that when the phone was irreparably damaged I replaced it with another identical Note 10 Lite. I'm now on an S24 Ultra and won't consider a new phone without a built-in stylus.
I dread having to replace my Note 10+ (kind of wish I'd future-proofed a bit by waiting for the 5G model) --- it has a wonderful synergy w/ my Kindle Scribe, Samsung Galaxy Book 3 Pro 360 and the Wacom One attached to my MacBook, since they all use the same Wacom EMR styluses.
We did a lot of experimentation with keyboards in Android - finding better ways to type and click is pure HCI dream work
The key challenge is:
- At first, people don't care about speed - they just want to type well and accurately - for most people, that means standardised layout across all their devices, and they won't consider phones that push them into other models.
- Only after they've mastered that standard layout do they start to care about speed, but by then they've gotten good enough at the basic system that swapping to anything else is too much of a regression
So I really do love the existence of third party keyboards that cater to the set of people that are willing to deal with that setback
I wanted to install it to give it a try, but in the playstore I saw the application roughly translated is "susceptible to share my approximative location with other enterprises or organization".
I must ask, what could the reason(s) for a keyboard have access to a location ?
I’ve always thought about copying other useful apps that are clearly trying to collect data or make you pay for stupid IAP, and then publishing and maintaining it through donations. The apps would all be free in the various offical stores.
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 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
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.
QWERTY 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.
>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.
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.
Japanese have a flick-style keyboard, very similar to T9. Instead of pressing a key multiple times, you press one key then flick up/down/left/right to choose a letter on that key.
I find there's a lot more intention behind your actions and I make far less typos when I'm flicking in Japanese vs typing on a touchscreen QWERTY. Being a second language, typos are even more common because its not at recognizable at a glance you made them, so the flicking been a huge improvement.
I always wonder if English should have something like this. I guess "MessageEase" is the most similar thing...
I'm Marco the Keybee Keyboard creator. Thank you really really a lot for your comments. Now Keybee keyboard is totally free and open source so all your ideas and suggestions migth be available one day.
Btw I just wanted to make typing more natural and comfortable, I really struggle with qwerty on touches. (ps: written with keybee keyboard of course).
Not on a phone right now, but you have to type in sample text above and press check. Bad UI choice of showing bars before text has been entered and separating bars from the input field by additional text.
The thing I dislike about smartphone keyboards is the amount of screen real estate they use. This keyboard seems to take more screen real estate rather than less.
I used minumm keyboard a long time ago and it was actually good, 1-2 cm of keyboard height, sadly I think it's been discontinued long ago, but you can see a couple of screenshots here
Yeah, the example is pretty bad. This layout also seems to be hard so squash vertically without increasing the error rate a lot compared to a normal one. The error rate on smaller sizes is something a lot of novel touchscreen keyboards should probably have focused on instead.
If one could swipe through the center without inserting a space, it would be incredible instead of perhaps only great... There was a PalmOS 5 keyboard like this named myKbd(1) based on some IBM research(2) which was quite fast to use. the atomik layout was quite quick to use.
I think the key to smartphone keyboards is something like Nintype, two-finger swiping. It's incredibly fast and doesn't require you to learn a completely new keyboard layout to succeed.
It's also a lot more comfortable for one-hand typing since you can do multiple swipes per word.
Funny that looking at their "number of touches" and "distance covered" checker, I've tried a few words and thinking in my head how it'd be in Nintype and it would score far better than Keybee.
Unfortunately I haven't seen anyone since Nintype (and the older Keymonk) to give it an attempt.
Great idea, keyboards on phones are pretty bad, though a bit ironic to have a taller keyboard with the message about not eating pixels
Also it's missing alternative symbols that you could get by holding a key, so for example, inserting a single number or a quote isn't convenient. And it's missing all the other ergonomic gesture advantages of hold+move gestures
The video is also misleading, there are no gaps between keys in regular keyboards, that's just visual effect that doesn't affect anything. And the qwerty jamming reason is a myth (though not 100% certain)
And why no iOS, the hex keyboard Typewise exists there, why did this project got blocked?
Even Swiftkey dropped from iOs. Main reason for me to dismiss Keybee Keyboard from iOs is that for some forms (like password) you are forced to use the apple keyboard. That's a no-go for me.
I'm a user of ClearFlow, a layout with similar design goals (and it's available on GBoard by default). Interestingly, ClearFlow is an ortholinear layout, but I'm not sure if that's due to a limitation of GBoard or the intention of its author.
Thank you. Started learning it last night and already up to a workable speed. I was getting frustrated with all the corrections I had to do when gliding on qwerty.
Well, it’s interesting, but who is heavily working with text, which requires a lot of typing, and only has a smartphone? Phones are mostly for consuming. For creating, it’s usually easier and more comfortable to use a device with a keyboard (PC or laptop)
2) In my (wealthy, Boston area) suburb most high school students do all their work - including writing multi-page papers - entirely on their phone. They think laptops are for old people.
Ok, but you still can't get actual work done on a smartphone with any efficiency.
> In my (wealthy, Boston area) suburb most high school students do all their work - including writing multi-page papers - entirely on their phone. They think laptops are for old people.
Kids are stupid. We were stupid when we were their age too. They will learn eventually that to get serious work done, you need an actual computer.
I know multiple successful business owners who don't have laptops and run everything off their phone, or at most an iPad. I personally need a laptop to be useful, but it's a mistake to think that just because that's true for you, it extends to everyone else.
People are used to it, yes, but I’m still not sure about the efficiency. Even screen size makes a real difference when you want to see more data on one screen or switch between windows quickly to compare sources
New parents. Newborns require an amount of holding and attention that smartphones are a great companion for. Unfortunately new parents don't get to hit pause on the rest of life while taking care of their newborn, so text entry into phones becomes quite important for the rest of life to keep progressing while also taking care of a new born.
"May be able" refers to collect, which is entirely up to the app. It does have access to password as you write them with it. It doesn't know what you're writing and it MAY collect. But it's not clear if it does collect.
But does it have network access, or access to other apps (perhaps via shared storage)? There's no reason for it to have any of that, and there exist systems for tracking whether an app can do those things.
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.
Well, to create the layouts I had to consider a lot of combinations. Some are really good like "ing" but they could compromize others. That's why I decided to made it fully customizable for the user. You can change any letters if you want!
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 satisfied with a keyboard that had me move my thumb in a circle as on the original iPod, provided it just read my mind and inputted the right text. That's extreme distance but little effort.
+---------+---------------+-----------+-------------------------------------+
| Digraph | Frequency (%) | Adjacent? | Pair on Keyboard |
+---------+---------------+-----------+-------------------------------------+
| TH | 1.52 | Yes | T is right of H |
| HE | 1.28 | No | Separated by O and [Space] |
| IN | 0.94 | Yes | I is top-left of N |
| ER | 0.94 | Yes | E is below R |
| AN | 0.82 | No | A is bottom-center; N is top-right |
| RE | 0.68 | Yes | R is above E |
| ND | 0.63 | No | N is top-right; D is bottom-right |
| AT | 0.59 | No | Separated by [Space] and S |
| ON | 0.57 | No | Separated by H and T |
| NT | 0.56 | Yes | N is top-right of T |
| HA | 0.56 | No | Separated by [Space] |
| ES | 0.56 | No | Separated by [Space] |
| ST | 0.55 | Yes | S is below T |
| EN | 0.55 | No | N/E are on opposite sides |
| ED | 0.53 | No | E is center-left; D is bottom-right |
| TO | 0.52 | No | Separated by H |
| IT | 0.50 | Yes | I is above T |
| OU | 0.50 | Yes | O is below U |
| EA | 0.47 | Yes | E is top-left of A |
| HI | 0.46 | Yes | H is below-left of I |
| IS | 0.46 | No | Separated by T |
| OR | 0.43 | Yes | O is below R |
| TI | 0.34 | Yes | T is below I |
| AS | 0.33 | Yes | A is below-left of S |
| TE | 0.27 | No | Separated by H and [Space] |
| ET | 0.19 | No | Separated by H and [Space] |
| NG | 0.18 | Yes | N is above G |
| OF | 0.16 | Yes | O is below F |
| AL | 0.09 | Yes | A is right of L |
| DE | 0.09 | No | E/D are distant |
+---------+---------------+-----------+-------------------------------------+
> distance travelled is the wrong (or an incomplete) metric.
Indeed, most of these keyboard algorithms use only plausible useful metrics and only plausible real text (like, how many designs account for the fact that you make typos and need to correct them, is backspace location accounted for? What about symbols?)
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.)
For me, as a two thumb typer, I feel like if you had kept the letters generally on the same side (left/right) as Qwerty, even if nowhere near the same location, I could adapt to it much more quickly.
I go to spell something as simple as my name on this and none of the keys are anywhere near where 40 years of muscle memory expect.
Frankly, I just want to hit the letters with the same thumb.
I understand not wanting to copy, to be a purely original creation, but you could certainly help adoption by making it a little less painful.
Oh dear. I'm afraid I'm not going to the take the requisite dozens of hours to be sure by learning this keyboard and making a truly "fair" comparison, but I'd bet I'm faster swiping with the current keyboard than I would be on this one. Swiping is why I can use words like "comparison" or "requisite" on a phone without giving it much thought anymore. I'm still faster on a real keyboard, especially as I rarely get those "tried to write 'hello', got 'grump'" sorts of errors with a keyboard, but it's a lot closer than it was when mobile devices first came out out and Palm's Graffiti input was considered a major breakthrough. (Laughable by modern standards.)
somehow , i get the sneaking suspicion, that while not perfect, qwerty actually works on mobile phones because it’s focused on not conflicting keys when typing (so tapping with thumbs work /better/ because of this).
for example, "The quick brown fox jumps over the lazy dog.” — < means left hand, > means right hand. you can see in a common phrase like this, you alternate sides more often. when you’re thumb-tapping, i think this is useful.
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.
I think they actually learn it because of the fun of mastery and the satisfaction of typing at high speed when you’re good at it, I doubt there’s much practical value.
Much better to use completion/expansion facilities than to learn a non-standard layout. Trying to use any device when you're used to Dvorak is such indescribable suffering.
Rather than experiencing that in exchange for a tiny amount of saved effort, stick with QWERTY and press TAB/etc to skip most of the typing.
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.
This is honestly the best argument for this, use it if you find it fun! Obviously it won’t be mainstream as some seem to think, but that doesn’t mean it can’t be cool.
Compare 1996's "FITALY":
"For the FITALY layout, we have obtained an average travel of 1.8, to be compared to an average travel of 3.2 for the QWERTY layout. (For prose, involving few numbers and symbols, the results are even better.)"
https://www.textware.com/fitaly/fitaly.htm
https://the-gadgeteer.com/1998/08/22/fitaly_review/
And closer to OP, "HexInput":
"Please use this idea! If you are a software developer, I urge you to consider adding this functionality to your product. My hope is that ten years from now, we won't have to laboriously tap out messages letter by letter, but instead will be able to zip them out quickly and efficiently with something like HexInput." -Sept2006
https://www.strout.net/info/ideas/hexinput.html
1996, 2006, 2026... Your turn?
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+
I loved the stylus on my Note 10 Lite so much that when the phone was irreparably damaged I replaced it with another identical Note 10 Lite. I'm now on an S24 Ultra and won't consider a new phone without a built-in stylus.
I dread having to replace my Note 10+ (kind of wish I'd future-proofed a bit by waiting for the 5G model) --- it has a wonderful synergy w/ my Kindle Scribe, Samsung Galaxy Book 3 Pro 360 and the Wacom One attached to my MacBook, since they all use the same Wacom EMR styluses.
Yes! I also use the EMR stylus with my Boox E-Ink tablet.
TY for the flashback: I'd learned Dasher! Jesus-phone had washed that away.
I kind of miss my Compaq iPaq, Danger Hiptop, Handspring Visor ... OK, one of those is not like the others, but it was ideal UX for the time.
>Type by zooming infinitely into a prediction model
Holy crap that's a trippy GIF
I've never felt so stressed by someone writing text before.
At the very least it captures well how it feels to talk when sufficiently high...
This is what immediately popped into my mind. I remember using this back in the early 2000s.
We did a lot of experimentation with keyboards in Android - finding better ways to type and click is pure HCI dream work
The key challenge is:
- At first, people don't care about speed - they just want to type well and accurately - for most people, that means standardised layout across all their devices, and they won't consider phones that push them into other models.
- Only after they've mastered that standard layout do they start to care about speed, but by then they've gotten good enough at the basic system that swapping to anything else is too much of a regression
So I really do love the existence of third party keyboards that cater to the set of people that are willing to deal with that setback
I wanted to install it to give it a try, but in the playstore I saw the application roughly translated is "susceptible to share my approximative location with other enterprises or organization".
I must ask, what could the reason(s) for a keyboard have access to a location ?
I’ve always thought about copying other useful apps that are clearly trying to collect data or make you pay for stupid IAP, and then publishing and maintaining it through donations. The apps would all be free in the various offical stores.
The delta between thinking about it and doing it is why there’s so many solid one-and-done apps that don’t exist.
I strongly encourage people to do it, especially if they’re not going to try to cash in.
There's https://simplemobiletools.com, who are doing their job to close that delta (not affiliated with them)
Those were sold to a predatory company. https://github.com/SimpleMobileTools/General-Discussion/issu...
Fork is https://github.com/FossifyOrg
Incredible, we cannot drop the guard even for a second. Thank you for the heads up!
Yet another tool that the users should have wanted to pay for before someone else did.
Keybee Keyboard uses a third party api called one-signal for push notifications, so they need the device location.
> 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
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.
I 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
I also would like to implement all those texting algorithms but I need the help of the open source community at this moment. Cheers!.
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.
QWERTY 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.
>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.
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.
Swipe 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.
Weird thing to say, why would a random port be peak efficiency that can’t be improved?
Japanese have a flick-style keyboard, very similar to T9. Instead of pressing a key multiple times, you press one key then flick up/down/left/right to choose a letter on that key.
https://www.youtube.com/shorts/BhD6r8NKlmY
I find there's a lot more intention behind your actions and I make far less typos when I'm flicking in Japanese vs typing on a touchscreen QWERTY. Being a second language, typos are even more common because its not at recognizable at a glance you made them, so the flicking been a huge improvement.
I always wonder if English should have something like this. I guess "MessageEase" is the most similar thing...
I'm Marco the Keybee Keyboard creator. Thank you really really a lot for your comments. Now Keybee keyboard is totally free and open source so all your ideas and suggestions migth be available one day. Btw I just wanted to make typing more natural and comfortable, I really struggle with qwerty on touches. (ps: written with keybee keyboard of course).
Percentage bars do not seem to work (FF Mobile), or your conclusion must be that the distance is exactly equal
Not on a phone right now, but you have to type in sample text above and press check. Bad UI choice of showing bars before text has been entered and separating bars from the input field by additional text.
Same on android chrome, bars are the same height and there're no numbers next to the units.
You need to fill in some example text in the text box above, and it will then compare.
The thing I dislike about smartphone keyboards is the amount of screen real estate they use. This keyboard seems to take more screen real estate rather than less.
I used minumm keyboard a long time ago and it was actually good, 1-2 cm of keyboard height, sadly I think it's been discontinued long ago, but you can see a couple of screenshots here
http://minuum.com/
Yeah, the example is pretty bad. This layout also seems to be hard so squash vertically without increasing the error rate a lot compared to a normal one. The error rate on smaller sizes is something a lot of novel touchscreen keyboards should probably have focused on instead.
If one could swipe through the center without inserting a space, it would be incredible instead of perhaps only great... There was a PalmOS 5 keyboard like this named myKbd(1) based on some IBM research(2) which was quite fast to use. the atomik layout was quite quick to use.
(1): https://palmdb.net/app/mykbd
(2): https://doi.org/10.1207/S15327051HCI172&3_4 https://blakewatson.com/uploads/2023/07/Performance_Optimiza...
I think the key to smartphone keyboards is something like Nintype, two-finger swiping. It's incredibly fast and doesn't require you to learn a completely new keyboard layout to succeed.
It's also a lot more comfortable for one-hand typing since you can do multiple swipes per word.
Funny that looking at their "number of touches" and "distance covered" checker, I've tried a few words and thinking in my head how it'd be in Nintype and it would score far better than Keybee.
Unfortunately I haven't seen anyone since Nintype (and the older Keymonk) to give it an attempt.
Heliboard does two finger swipe! Not as well as nintype but very passable! https://f-droid.org/packages/helium314.keyboard/
I wonder what got them kicked from iOS. Alt keyboards in the app store definitely do exist...
I dismissed Keybee keyboard because iOs was not friendly to third party keyboards.
Great idea, keyboards on phones are pretty bad, though a bit ironic to have a taller keyboard with the message about not eating pixels
Also it's missing alternative symbols that you could get by holding a key, so for example, inserting a single number or a quote isn't convenient. And it's missing all the other ergonomic gesture advantages of hold+move gestures
The video is also misleading, there are no gaps between keys in regular keyboards, that's just visual effect that doesn't affect anything. And the qwerty jamming reason is a myth (though not 100% certain)
And why no iOS, the hex keyboard Typewise exists there, why did this project got blocked?
Even Swiftkey dropped from iOs. Main reason for me to dismiss Keybee Keyboard from iOs is that for some forms (like password) you are forced to use the apple keyboard. That's a no-go for me.
I'm a user of ClearFlow, a layout with similar design goals (and it's available on GBoard by default). Interestingly, ClearFlow is an ortholinear layout, but I'm not sure if that's due to a limitation of GBoard or the intention of its author.
Thank you. Started learning it last night and already up to a workable speed. I was getting frustrated with all the corrections I had to do when gliding on qwerty.
Just enabled—I've been idly wondering if there were any good alternative mobile keyboard layouts for ages, and this one checks all my boxes. Thanks!
Well, it’s interesting, but who is heavily working with text, which requires a lot of typing, and only has a smartphone? Phones are mostly for consuming. For creating, it’s usually easier and more comfortable to use a device with a keyboard (PC or laptop)
1) Like 80% of the world is smartphone-only
2) In my (wealthy, Boston area) suburb most high school students do all their work - including writing multi-page papers - entirely on their phone. They think laptops are for old people.
I found 2) amazing. Then I realized I'm an old person...
It means future job security.
> Like 80% of the world is smartphone-only
Ok, but you still can't get actual work done on a smartphone with any efficiency.
> In my (wealthy, Boston area) suburb most high school students do all their work - including writing multi-page papers - entirely on their phone. They think laptops are for old people.
Kids are stupid. We were stupid when we were their age too. They will learn eventually that to get serious work done, you need an actual computer.
I know multiple successful business owners who don't have laptops and run everything off their phone, or at most an iPad. I personally need a laptop to be useful, but it's a mistake to think that just because that's true for you, it extends to everyone else.
People are used to it, yes, but I’m still not sure about the efficiency. Even screen size makes a real difference when you want to see more data on one screen or switch between windows quickly to compare sources
Are they typing or dictating? Voice is an underrated input method
> who is heavily working with text, which requires a lot of typing, and only has a smartphone?
People reading HN on the subway, who have some insightful comment to add, but are slowed down by unergonomic input methods?
New parents. Newborns require an amount of holding and attention that smartphones are a great companion for. Unfortunately new parents don't get to hit pause on the rest of life while taking care of their newborn, so text entry into phones becomes quite important for the rest of life to keep progressing while also taking care of a new born.
Looks like a copy of https://play.google.com/store/apps/details?id=ch.icoaching.t.... I don't know which one can't first.
I tried typewise. Decided it wasn't really worth it.
Typewise came later and their approach is very different than Keybee Keyboard. They only shares the hey keyshape but on a qwerty layout.
Will you get this up on f-droid in addition to the play store?
This reminds me of what I did for Rad Type: https://www.tyleo.com/projects/rad-type
I didn’t fully optimize for touch but it’s based on the same idea that you want more buttons equidistant from where your thumb centers.
No swyping and no autocorrect make it DOA
The site specifically says it is swipe-friendly, and the GitHub site makes clear that it supports autocorrect.
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?
That's a mandatory message for any input method. Keybee keyboard is not collecting anything and the code is all available on github.
"May be able" refers to collect, which is entirely up to the app. It does have access to password as you write them with it. It doesn't know what you're writing and it MAY collect. But it's not clear if it does collect.
But does it have network access, or access to other apps (perhaps via shared storage)? There's no reason for it to have any of that, and there exist systems for tracking whether an app can do those things.
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.
Well, to create the layouts I had to consider a lot of combinations. Some are really good like "ing" but they could compromize others. That's why I decided to made it fully customizable for the user. You can change any letters if you want!
Nice, but physical keyboards are making a comeback.
https://news.ycombinator.com/item?id=47114412
Why the use of “but” here? One does not get in the way of the other
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 satisfied with a keyboard that had me move my thumb in a circle as on the original iPod, provided it just read my mind and inputted the right text. That's extreme distance but little effort.
https://pi.math.cornell.edu/%7Emec/2003-2004/cryptography/su...
See also: https://en.wikipedia.org/wiki/Typewise
> distance travelled is the wrong (or an incomplete) metric.
Indeed, most of these keyboard algorithms use only plausible useful metrics and only plausible real text (like, how many designs account for the fact that you make typos and need to correct them, is backspace location accounted for? What about symbols?)
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.)
Acceleration is a good metric indeed. And distance was the easiest metric to work on to get some useful data to create the layout. Marco.
For me, as a two thumb typer, I feel like if you had kept the letters generally on the same side (left/right) as Qwerty, even if nowhere near the same location, I could adapt to it much more quickly.
I go to spell something as simple as my name on this and none of the keys are anywhere near where 40 years of muscle memory expect.
Frankly, I just want to hit the letters with the same thumb.
I understand not wanting to copy, to be a purely original creation, but you could certainly help adoption by making it a little less painful.
It's interesting but I wish I could still Swype on it
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.
Yeah I mean that makes perfect sense, just means it’s probably not for me. Best of luck to them though
sort of. swiping triggers every letter you cross
Exactly! That's the main innovation. What you can build on top (like a text algorithm) is adding speed and efficiency.
Oh dear. I'm afraid I'm not going to the take the requisite dozens of hours to be sure by learning this keyboard and making a truly "fair" comparison, but I'd bet I'm faster swiping with the current keyboard than I would be on this one. Swiping is why I can use words like "comparison" or "requisite" on a phone without giving it much thought anymore. I'm still faster on a real keyboard, especially as I rarely get those "tried to write 'hello', got 'grump'" sorts of errors with a keyboard, but it's a lot closer than it was when mobile devices first came out out and Palm's Graffiti input was considered a major breakthrough. (Laughable by modern standards.)
That’s a bit different
"Like a Blackberry," I read the headline and thought. Then I looked and thought, "I'm old."
somehow , i get the sneaking suspicion, that while not perfect, qwerty actually works on mobile phones because it’s focused on not conflicting keys when typing (so tapping with thumbs work /better/ because of this).
for example, "The quick brown fox jumps over the lazy dog.” — < means left hand, > means right hand. you can see in a common phrase like this, you alternate sides more often. when you’re thumb-tapping, i think this is useful.
<t >h <e <q >ui <c >k <br >o <w >n <f >o <x >jump <s >o <ver t >h <e >l <az >y <d >o <g
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.
I think they actually learn it because of the fun of mastery and the satisfaction of typing at high speed when you’re good at it, I doubt there’s much practical value.
Much better to use completion/expansion facilities than to learn a non-standard layout. Trying to use any device when you're used to Dvorak is such indescribable suffering.
Rather than experiencing that in exchange for a tiny amount of saved effort, stick with QWERTY and press TAB/etc to skip most of the typing.
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.
This is honestly the best argument for this, use it if you find it fun! Obviously it won’t be mainstream as some seem to think, but that doesn’t mean it can’t be cool.
If Steve Jobs when he introduced iphone, added this keyboard and said this is how we should write, everybody would do it.
Just sayin'...
Very good point. Steve would be proud of Keybee Keyboard!
Oh that made me remember the you're holding it wrong debacle with antenna reception.
You mean in the way that it was massively overblown in the media but ultimately wasn’t a big deal?
No, they wouldn’t have.
[dead]