Keybee: a new keyboard layout designed specifically for touchscreen devices
keybee.it
keybee.it
Typed on Keybee.
If I am a right hand user, the right part of my keyboard is covered by my hand, and is easier to be used. I've seen this in keyboard which don't have any keys on a 1/4th circle on the bottom right of the screen.
If I am a left hand user, the left part of my keyboard is covered by my hand and is easier to be used. But the left part of the keyboard has less important keys than the right part.
Essentially, a mirror of the keyboard would be more optimal for left hand users. Although the issue is less important than on say QWERTY. Because the amount of space on the outer rings (most strain) is still the same for left and right hand users. And that's Marco's point.
The amount of space your fingers can move back is smaller than the amount of space they can reach up. Going back puts more strain on the fingers. (Anecdotal experience.) (EDIT: and the arm, as well.)
I remember what it was like using PDAs and smartphones with actual physical keys. After a brief period of adjustment to a new device, I was soon typing without any mistakes. It was such a low-friction transfer of my thoughts to digital form, I took it for granted it would always be that easy.
I look forward to trying one of the new Blackberry phones for my next upgrade.
Programmer Dvorak or Colemak are alternatives to QWERTY but they suffer from a lack of widespread adoption. Keyboard shortcuts might still be awkward, you're still going to meet a massive learning curve (less with Colemak though since it deviates only 6 key positions from QWERTY). See this post on SO for an in depth, anecdotal comparison between the 3 [2]. A new keyboard layout is going to suffer from these issues as well. Most of these are chicken-egg problems. But that doesn't mean it isn't better in the long run.
Without having used Keybee some things to keep in mind, apart from not being programmer/sysadmin friendly, are that some users use a smartphone with one hand whilst others use two. Another one seems that the screen is being used more than with QWERTY.
I've sticked to SwiftKey because it can support multiple dictionaries, and I like that there's a lot of themes available. However they got bought by Microsoft recently. I also got Hacker Keyboard installed, so if I'm using CLI (local via Termux or SSH) I can easily use common UNIX keybinds. So I'm certainly interested trying something better, even if there's a learning curve attached and even if its only going to be usable during touchscreen usage.
The keyboard you linked seems akin to what I had on a Nokia N900 / Nokia N950 or a Nokia Communicator. Its keys are small, it adds weight/space or takes time to pull in/out. Plus, you're stuck to a Motorola Z (Motorola doesn't give software updates for long). Take for example the iPad Pro case which includes a keyboard. Its not a bad keyboard given its size but even that layout isn't standard given the key spaces are different (small shift for example!). Both very much not ideal IMO. Another thing one can consider is a Bluetooth keyboard for situations where one ends up having to type a lot, or short, quick bursts such as during keynote taking f.e. student during seminar. I'd say that is a very viable use case. Disadvantage is these use batteries which get eventually depleted and cannot be recharged. Plus the insecurities of Bluetooth being wireless & sniffable.
Also important in these comparisons is how people use their keyboards (touchscreen and physical). Which exact layout version do they use? Do they swipe on their touchscreen? How long have they used layout X or Y? For example, I never really got into swiping even though it has been available for a decade. And finally, there's voice dictation which has taken some ground past years.
[1] https://computer.howstuffworks.com/question458.htm
[2] https://stackoverflow.com/questions/23078626/are-alternative...
That is an urban myth refuted by the author of qwerty, but it just doesn't die.
I was thinking about switching from Android to Sailfish OS for a while now and quickly realized that my personal reason for Android lock-in is a keyboard called SlideType[1]. I really have to figure out how to write keyboards for Sailfish one day.
[1]: https://play.google.com/store/apps/details?id=com.latinsud.a...
They newer Android Blackberries are OK but their keyboard isn't as good as the 9900.
Keybee has suggestions support based on AOSP dictionaries, by default off.
> Keybee was invented, developed and patented by Marco Papalia
That is dishonest, it isn't free if it is encumbered by patents. Also i'm not sure how this works considering the author is from Italy and EU doesn't consider software patentable.
- the word "free" has several meanings in English, i.e. "free" as in "no charge" and "free" as in "freedom" (free access, free software, etc.) - the answer given there does not indicate which one of those is meant.
- patents have most likely been granted in countries that recognise them - this does not prevent from the patent being put into public domain. However, the second sentence in question 17 seems to indicate that the license bears a fee, which also contradicts one of the meanings of "free above.
Either way, the Q&A/FAQ is full of marketing mumble.
while i am in no way defending software patents (which I don't like at all), i find the full-frontal attack attitude that you and many other gnu/zealots exhibit towards random strangers on the internet so infuriating that i am writing this comment here to let you know that people like you are exactly what prevents me (and many others) from getting involved in some free (libre) software projects.
thanks so much for your contribution to the advancement of libre software.
yuck.
Yes, I generally would prefer for people to publish their software as libre, especially if it does not interfere with their way of making money as is the case here, yes, I was somewhat annoyed that I could not actually try this keyboard out, since yes, I am enough of a free software zealot for my personal use that I only have F-Droid installed and yes, I do actually find it unacceptable for a keyboard app on Android to not at least allow its source code to be inspected, as once enabled it can read everything you type from personal conversations down to passwords and Android does fuckall to prevent a keyboard app from just sending all of that to somewhere on the internet, but none of that was expressed in my previous comment.
Free can imply free as in speech (libre) or free as in beer (gratis). Libre does not imply not being patent encumbered either, it refers to the software license.
Also, I suggest you Hanlon's razor [1].
>The sentence itself implies libre, not being patent-encumbered
Nope. It is used as an adverb, for which the dominant meaning is 'without cost'.
And you know this. You are just here spinning. I love libre software, but when you abuse language to make a political point it disgusts me just as much when I hear the words 'pro-life' or 'job-creators'.
If you want to claim you continuously confuse 'free' as as an adverb for patent free gnu stuff you are either an idiot or disingenuous
> "Keybee is simple and clear because all the letters are always available (no hidden keys) and they all have the same size"
Checking my iPhone and my wife's Android phone, as well as an old Windows Phone I have in a drawer, all of the letters of the alphabet are available on the default board, none are hidden, and they are all the same size as each other on each respective keyboard.
At first I thought you might be talking about non-English keyboards, but looking at the Keybee board screenshots it's the same standard 26 English letters.
So, from that particular standpoint, how does Keybee offer a more complete set of English language characters than a device's default keyboard? This feels like either a bad translation or dubious marketing.
Maybe I'm just not smart enough to see the difference from a slide with screenshots and captions that make dubious statements, but I'd appreciate if you would explain anyway.
The keyboard is interesting, it takes a while to get used to the new layout but once you get the hang of it it seems fun.
I've used it for over a year now. My friends beat me when their dictionary is on. But without it, I'm around 30% faster. For writing commands, code or formulas - it's superior, and that's why I like it.
It took me about 3 weeks to get on par with a normal dictionary-less QUERTY. Learning new layouts like this takes really long as it has to go into your muscle memory before you feel comfortable. I guess that's why we're still stuck with QUERTY (which was designed to slow down typing on mechanical typewriters).
It might be worth checking out for the technically-inclined. It's open source and as far as I know - patent free. See https://github.com/Adellica/Thumbkeyboard.
Once you have it in your muscle memory, you can sort of type blindly and use symbols as quick as other letters. It doesn't look like KeyBee can improve my typing.
- https://twitter.com/KeybeeKeyboard/status/947406254871281664