Do's and Don'ts for wireless applications

Computerworld - Meryl Enerson, president of East Chatham, N.Y.-based consulting firm Enervision Media Inc., outlined her ideas for what developers need to consider when designing wireless applications last week at the Enterprise Wireless Forum in Boston. Enerson has some strong opinions about what is and is not appropriate when designing applications that will be accessed via the small screens available on most wireless devices. Here is a distilled list of do's and don'ts compiled by Computerworld editor at large Brian Sullivan based on that talk.

Do design for the user and not the technical guru or yourself. Consider that all users may not have the technical expertise that you have. Get to know your audience before making assumptions about what they can and cannot do easily.

Don't overload the user with too much content. Cramming every last piece of information on a tiny wireless screen may seem helpful, but is it what the user really needs? Or wants? Too much information in too small a space can make an application worthless.

Do hire an editor and/or a writer. Use casual language and avoid jargon. Too many product development teams assume that the user "will know what that means." Assume the users will not know and keep messages simple and clear. Especially avoid creating jargon for each new application you develop.

Don't use dead-end screens. At the very least, give the users a way to get back to a home page or a way to back up. The most commonly used feature on most Web sites is the Back button, and given that a wireless user is using one hand and not sitting at a keyboard, make it easy to turn around or get back to home.

Do minimize data entry. Again, users are most likely using one hand so don't ask for things such as full e-mail addresses when there are ways to work around such requests, or give the users shortcuts. Think about the user trying to enter data with one hand in a busy airport while juggling a cup of coffee and a briefcase.

Don't overdo the color or graphics. The simpler a display, the easier it is to read. What looks great and fun on a desktop monitor looks like mud on the small screen. Also, use text along with your graphics, don't rely on pictures alone because the user might not get it. If you can avoid graphics, don't use them.

Do be very careful when you use abbreviations. Just like graphics, users may not understand what you mean when you hit them with a list of abbreviations. Another mistake developers often make is that they make up their own abbreviations. If you are going to use abbreviations, try to get a style manual from a large media organization or dictionary and use only common and universally recognized shortcuts.

Don't rely on user surveys and focus groups. Get out and observe your target audience in the field and ask them what they like and don't like about specific applications. What people tell researchers in a focus group or a survey is often very different from what they tell each other when they are frustrated or pleased with the way an application works.