Skip to main content

Android - Alternative Keyboards Shootout

The Motorola Milestone picture, courtesy of Wikipedia.

Most of the time, I stick to the hardware slide-out keyboard of the Motorola Milestone. Indeed, the presence of the hardware keyboard was one of the main reasons I chose this device over the other in the first place. However, there are occasions, when I just need to quickly reply to a text message or an email, often while on the go having only one hand available to operate the device. I use the stock Android soft-keyboard in these cases, but I remain unhappy with the perceived high number of typos and errors. Many times I start typing on the soft-keyboard and eventually frustrated with the typos I slide out the hardware keyboard, rotate the device to the landscape mode and finish the text on the hardware keyboard. The problem with this solution is, that switching takes time: applications need to react to the screen orientation change and redraw the user interface. Some apps are fast, but for some of them, this change takes one or two seconds and the user experience suffers.

As Swype keyboard was not available for the first generation Droid / Milestone I tried SlideIT which is based on a similar concept, but after a short trial I turned back to the stock: I need to frequently switch back and forth between Czech and English, sometimes even using words from both languages in one message which makes all keyboards relying on a dictionary unsuitable for my use case.

Note: The keyboard pictures above were taken from the Android Market

In the fall 2010, I registered an interesting newcomer to the alternative Android keyboards race the 8pen keyboard (Android Market). I decided to give it spin. During the approximately two week test drive, MessagEase, a soft keyboard which has its roots on the Palm OS platform, was released to the Android Market so I included it in the competition. I installed myTextSpeed, available on the Market to establish a leveled playing field and tried to compare both newcomers 8pen and MessagEase with the incumbents - the hardware keyboard and the stock Android keyboard. You can see the best scores I recorded in myTextSpeed for all the four keyboards in two different races, typing two classic books texts.

  Moby Dick The Odyssey Note
Droid HW keyboard 166 CPM / 30 WPM / 100% accuracy 166 CPM / 34 WPM / 100% accuracy landscape mode, thumb-typing, both hands
Stock Android 2.1 115 CPM / 19 WPM / 100% accuracy 112 CPM / 24 WPM / 100% accuracy portrait mode, thumb-typing, one hand
MessagEase 87 CPM / 15 WPM / 100% accuracy 91 CPM / 19 WPM / 100% accuracy portrait mode, thumb-typing, one hand
8pen 62 CPM / 12 WPM / 100% accuracy 54 CPM / 11 WPM / 100% accuracy portrait mode, thumb-typing, one hand

Note: The 100% accuracy means, that any time I made a typo, I corrected the typo before proceeding further.

The fact that the hardware keyboard comes out as a winner is not a big surprise to me. This confirms the tests I did on the HP OmniGo palmtop many years ago. I was about 2x as fast thumb-typing on its calculator-like qwerty keyboard than using the Graffiti handwriting recognition. What comes as a surprise, is the fact that the stock Android soft-keyboard fared better the alternatives, even though the perception during the regular usage tells otherwise. Between 8pen and MessagEase, the later one fared batter. MessagEase is also faster to learn: after just one day trial, I could already type faster on it than after one week on 8pen. The bad thing about MessagEase though is that it does not work well with the hardware keyboard in the landscape mode. Ideally, I would like to use the built-in keyboard driver in the landscape mode and restrict MessagEase to portrait mode only, which is not currently possible.

Popular posts from this blog

First Month of Active Touring

Putting my money where my mouth is, I took on the adventure of buying a plug-in hybrid. A few years back, I used to drive a car only for weekend getaways, so an SUV seemed to be a logical choice. At only fifteen thousand kilometers driven annually, the fuel economy was not a significant issue, the driving experience was the main thing.

During the past few years with family and small kids, the car usage became more spread out throughout the week. With that said, I noticed we maintain two very distinct driving patterns: many short trips around Prague during the week to get kids to school and sports and then longer trips, roughly 100 miles each direction, during the weekends. With short distances and many cold starts due to the city driving on the workdays, the already poor fuel economy of an SUV deteriorated further.

I realized when our car was up for renewal that it was almost as if we needed two different vehicles for two different use cases - an electric vehicle for city driving and …

Version 2.0 Syndrome - Why the Software Architecture Matters

"Guys you will never have a chance to build the version 2.0, you have to get it right from the get-go, or keep suffering from your mistakes for the lifetime of the product." - Jiri Karpeta, my boss at LCS International, used to say. It was back in 1995, and while LCS's bread and butter were Helios, an ERP for the SMB segment, we were busy building Noris - the future LCS's flagship ERP for larger enterprises. Of course, given the above philosophy, LCS was quite heavily invested in CASE tools to support our software design efforts. That's where I learned the first time that software modeling matters.

But back to the original statement above that you "never get a chance to build the version 2.0". It may sound too harsh, too fatalistic. Well, you may be right, there are always exceptions to the rule. While I don't have exact statistics at hand, my experience shows that the statement is more often correct than not. I have interviewed hundreds of software…

Agile on Overdrive

It may sound old-fashioned and laughable these days when techniques like UML are so unsexy, but I can still remember the days back at IBM T.J. Watson in the early 2000's when we were working on a prototype of a new VoiceXML browser to inform IBM's standardization efforts in the space. (The language was supposed to be VoiceXML 3.0, and we abbreviated the research project to "V-3" - pronounced "fau drai" in reference to the German V-2 rocket.) We took VoiceXML 2.0 as a foundation but added full DOM and DOM Events support together with XForms as the data model representation.

It was shortly after IBM's acquisition of Rational Software, so we took advantage of that deal and got our hands dirty with Rational Rose. While one of our colleagues kept pushing us to start coding and iterate towards the result in the agile fashion, given the incomplete specs and many open questions stemming from the combination of so many complex technologies in one piece, we prevai…