Live data from Hacker News

Keybee: A Keyboard Designed for Smartphones

keybeekeyboard.com

71–80 of 103 posts

Re: Keybee: A Keyboard Designed for Smartphones

#71
post #26

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)

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.

Re: Keybee: A Keyboard Designed for Smartphones

#72
post #29

Earlier quoted context omitted.

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.

> 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 wo…

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.

Re: Keybee: A Keyboard Designed for Smartphones

#73
post #4

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 u…

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.

Re: Keybee: A Keyboard Designed for Smartphones

#74
post #49

Earlier quoted context omitted.

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.

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.

>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.

Re: Keybee: A Keyboard Designed for Smartphones

#75
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?

Re: Keybee: A Keyboard Designed for Smartphones

#76
post #49

Earlier 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.

Weird thing to say, why would a random port be peak efficiency that can’t be improved?

Re: Keybee: A Keyboard Designed for Smartphones

#77
post #24

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…

> 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?)

Re: Keybee: A Keyboard Designed for Smartphones

#78
post #36

Earlier 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

I've never felt so stressed by someone writing text before.

Re: Keybee: A Keyboard Designed for Smartphones

#79
post #74

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.

>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.

Re: Keybee: A Keyboard Designed for Smartphones

#80

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/

Post reply on HN