### Optimal SMS keyboard layouts

One of the things I find very frustrating about typing SMS messages on my phone is that I often find that the next letter I want to type is actually on the same key that I just pressed. And that slows me down because either I wait for the timeout, or I click the right arrow key to move on.

For example, here's a standard keyboard on cell phones:
`     abc def  1   2   3 ghi jkl mno  4   5   6pqrs tuv wxyz  7   8   9`

Very common English letter pairs such as 'ed' and 'on' appear on the same key meaning that if you need to type one of these you are going to incur the cost of dealing with the 'next letter is on same key' problem. In addition, the most common English letters are more than one click away; the most common English letter 'e' is two clicks, 'o' is three, 'n' is two, etc.

What you really want is a keyboard layout that means that most common letters are as few clicks away as possible, and that the common letter pairs are on different keys so that you can maximize typing speed. And if possible make the layout as close as the current one so that it's easy to learn.

There are some people who propose squeezing QWERTY into the the current keyboard. This ends up with a key that starts with 'q' and another that starts with 'z': two of the least common keys are given pride of place on the keyboard.

Other propose using dictionaries. I think the fastest typing would be on an intelligently laid out keyboard without the need for a dictionary.

I took the 1000 most common words in English as a test set, and performed three keyboard optimizations: one by hand and two using different sets of common letter pairs and tested them against the 1000 most common words. Each set received a score equal to the number of clicks required to type all 1000 words. A single click on a key was worth one click (so typing 'a' is one click, typing 'q' is two, etc. on the standard keyboard), and the cost of handling the 'next letter is on same key' was set at the same time as two clicks.

I used letter and letter pair frequency information from the excellent book Cryptanalysis. And of course I wrote some code to perform the layout of the keyboards optimizing for the least number of clicks per common letter and the least number of same key clicks for letter pairs.

The standard keyboard layout gets a score of 12,447 clicks.

The following machine generated layout can be used to type the same words in 8757 clicks (70.35% of the clicks of the standard keyboard):
`     acb euwj  1   2   3 ipg  hmx olv  4   5   6sfq  tdyz nrk  7   8   9`

This keyboard doesn't look anything like the original keyboard so I then used a shorter list of letter pairs and hand optimized the keyboard to balance clicks and similarity. The result is 8,912 clicks (or 71.6% of the standard keyboard) and a nice layout:
`     adc efb  1   2   3 igj hlk omz  4   5   6srpq tuv nwyx  7   8   9`

Now, if there was only a way to get that on my RAZR I could save 30% of my typing time.

Anonymous said…
Where's the "d"? Your last layout seems to be lacking something important and gave the letter "z" pride of double placement.

{^_-}
Anonymous said…
d in the original place of the b
JoeC said…
It might save you 30% typing time, but how many people are really touch typists on phones? For those who rely on knowing the alphabet to efficiently hunt and peck, you would slow them down by far more than 30%.

By moving letters around how are people going to call 1-900-SEXCHAT? Except for the addition of the Q and Z recently, the "keyboard" has been the same since rotary phones.

Assuming you ignore that problem, why are you not using the 1 key? The only reason not to use the one key is legacy compatibility which you are already throwing out.

In your examples, grouping adc or even acb are bad ideas. Your first grouping should be clearly different from the standard phone keyboard so users instantly recognize the layout they are using. Don't forget Dyslexic users. Or how many users switched to the more efficient DVORAK keyboard.

I also wonder about the placement of the least used letters at the bottom. I find it easier to hit the top and bottom row than the middle.
Anonymous said…
I'm a touch-typist on my phone, and even though it's illegal in australia i quite often send sms's while i'm driving - i hold the phone down near my leg and type away - double-check all the text when i get to a red light or something and then send it.

I'm a fan of predictive text too - it eliminates your problem of having 'ed' etc on the same number. And i've memorised most of the words that come up so that i can change it from "good" to "home" etc without having to look.
Anonymous said…
I recently bought a used Nokia 6820, you know the one which flips open to reveal a full keyboard on both sides of the screen. I didn't buy it for this feature but having now been getting used to it for a few weeks, it makes this sort of problem seem rather stone-age.

I'm really surprised if you don't have T9 / predictive text on the Razr? That too makes the keyboard a secondary problem, although it introduces a nice set of new problems. (Me, I write in three languages regularly, sometimes in the same message ...)
Anonymous said…
You should use your phone for calliing instead of using it to send SMSs: you are not 15 years old, are you?

### Your last name contains invalid characters

My last name is "Graham-Cumming". But here's a typical form response when I enter it: Does the web site have any idea how rude it is to claim that my last name contains invalid characters? Clearly not. What they actually meant is: our web site will not accept that hyphen in your last name. But do they say that? No, of course not. They decide to shove in my face the claim that there's something wrong with my name. There's nothing wrong with my name, just as there's nothing wrong with someone whose first name is Jean-Marie, or someone whose last name is O'Reilly. What is wrong is that way this is being handled. If the system can't cope with non-letters and spaces it needs to say that. How about the following error message: Our system is unable to process last names that contain non-letters, please replace them with spaces. Don't blame me for having a last name that your system doesn't like, whose fault is that? Saying "Your

### All the symmetrical watch faces (and code to generate them)

If you ever look at pictures of clocks and watches in advertising they are set to roughly 10:10 which is meant to be the most attractive (smiling!) position for the hands . They are actually set to 10:09.14 if the hands are truly symmetrical. CC BY 2.0 image by Shinji I wanted to know what all the possible symmetrical watch faces are and so I wrote some code using Processing. Here's the output (there's one watch face missing, 00:00 or 12:00, because it's very boring): The key to writing this is to figure out the relationship between the hour and minute hands when the watch face is symmetrical. In an hour the minute hand moves through 360° and the hour hand moves through 30° (12 hours are shown on the watch face and 360/12 = 30). The core loop inside the program is this:   for (int h = 0; h <= 12; h++) {     float m = (360-30*float(h))*2/13;     int s = round(60*(m-floor(m)));     int col = h%6;     int row = floor(h/6);     draw_clock((r+f)*(2*col+1), (r+f)*(row*2+1),

### The Elevator Button Problem

User interface design is hard. It's hard because people perceive apparently simple things very differently. For example, take a look at this interface to an elevator: From flickr Now imagine the following situation. You are on the third floor of this building and you wish to go to the tenth. The elevator is on the fifth floor and there's an indicator that tells you where it is. Which button do you press? Most people probably say: "press up" since they want to go up. Not long ago I watched someone do the opposite and questioned them about their behavior. They said: "well the elevator is on the fifth floor and I am on the third, so I want it to come down to me". Much can be learnt about the design of user interfaces by considering this, apparently, simple interface. If you think about the elevator button problem you'll find that something so simple has hidden depths. How do people learn about elevator calling? What's the right amount of