Commentary

Ed Hansberry
 

Dvorak Users Dislike Qwerty Keyboard Dominance In Phones

Fans of the Dvorak keyboard layout sing praises of how much faster you can type than you can with a traditional Qwerty keyboard, so named because of the order of the first six letters on the upper row. With a PC, it is pretty simple - you just need to plug in a Dvorak keyboard and you are ready to go. With a phone though, you really don't have that option, at least with a physical keyboard.

Fans of the Dvorak keyboard layout sing praises of how much faster you can type than you can with a traditional Qwerty keyboard, so named because of the order of the first six letters on the upper row. With a PC, it is pretty simple - you just need to plug in a Dvorak keyboard and you are ready to go. With a phone though, you really don't have that option, at least with a physical keyboard.The Wall Street Journal has an article on the frustrations that Dvorak fans have when they grab a cell phone to catch up on emails or send out a few text messages. As the article notes, the Qwerty keyboard wasn't designed for speed. In fact, it was designed to limit speed. In the early days of typewriters, the first keyboard layouts let people achieve speeds that were faster than the mechanical arms could smash the ink onto a page. The keys would hit each other and become stuck. So the letters were rearranged so that speeds would be slow enough that the typewriter wouldn't be prone to jamming.

Today that is irrelevant. I challenge you to find a working typewriter in your office that isn't covered in a thick layer of dust. Computers certainly don't care about the speed of the typist. There is nothing to jam and printers today kick out entire pages at a time with only a few moving parts. So why hasn't the Dvorak keyboard layout gained in acceptance? I suspect we are all taught Qwerty in high school or college and once most people can achieve 40-50 words per minute, that is good enough. No point in relearning something you have used for years, or decades, just to get a faster speed, even if that may be 100% faster.


More Mobility Insights

White Papers

More >>

Reports

More >>

Webcasts

More >>

Because there is such a small minority using the Dvorak layout, you can forget ever seeing a phone with a physical keyboard using that layout. However, many phones also have virtual keyboards. The iPhone comes solely with a virtual keyboard. All Windows Mobile devices with touch screens have virtual keyboards. With that, you should be able to install whatever keyboard you want assuming someone has written it. You can run such a keyboard on the iPhone, but only if it is jailbroken. I don't know why Apple would block such an app from the App Store, but you won't find one there.

I feel for Dvorak users. I used a program called FITALY for years on a Windows Mobile phone. It was designed for stylus input and after about 3 months, I could hit 40-45 words per minute with minimal effort. I've seen people hit north of 80 words per minute using just a stylus, so I can understand the Dvorak user's desire for speed. I still have FITALY installed, but now I find myself using the physical keyboard more, which is just fine for two-thumbed operation.

Virtual or physical, phone manufacturers should allow for a Dvorak layout, even if the letters on a real keyboard don't match up. It is just software that the user could easily switch in the settings somewhere to enable it. At the very least, if someone else writes a program, don't block it. (I'm pointing at you Apple.) Give users the chance to personalize their device and make it as efficient as possible. Even if that means that they want to use some obscure odd keyboard layout.


Related Reading




Currently we allow the following HTML tags in comments:

Single tags

These tags can be used alone and don't need an ending tag.

<br> Defines a single line break

<hr> Defines a horizontal line

Matching tags

These require an ending tag - e.g. <i>italic text</i>

<a> Defines an anchor

<b> Defines bold text

<big> Defines big text

<blockquote> Defines a long quotation

<caption> Defines a table caption

<cite> Defines a citation

<code> Defines computer code text

<em> Defines emphasized text

<fieldset> Defines a border around elements in a form

<h1> This is heading 1

<h2> This is heading 2

<h3> This is heading 3

<h4> This is heading 4

<h5> This is heading 5

<h6> This is heading 6

<i> Defines italic text

<p> Defines a paragraph

<pre> Defines preformatted text

<q> Defines a short quotation

<samp> Defines sample computer code text

<small> Defines small text

<span> Defines a section in a document

<s> Defines strikethrough text

<strike> Defines strikethrough text

<strong> Defines strong text

<sub> Defines subscripted text

<sup> Defines superscripted text

<u> Defines underlined text

InformationWeek encourages readers to engage in spirited, healthy debate, including taking us to task. However, InformationWeek moderates all comments posted to our site, and reserves the right to modify or remove any content that it determines to be derogatory, offensive, inflammatory, vulgar, irrelevant/off-topic, racist or obvious marketing/SPAM. InformationWeek further reserves the right to disable the profile of any commenter participating in said activities.

Disqus Tips To upload an avatar photo, first complete your Disqus profile. | View the list of supported HTML tags you can use to style comments. | Please read our commenting policy.
T-Shirt Giveaway T-Shirt Giveaway: Each week we're selecting one great comment from our readers. The author of the comment will receive an InformaitonWeek Community t-shirt. So get posting!
Subscribe to RSS

Resource Links