InformationWeek

March 27, 2000

Good Wireless Applications Are Short But Sweet
By Alan Radding

uilding a wireless application is like writing a telegram: The fewer words, the better. In a telegram, you keep words to a minimum because each word costs money. In developing a wireless app, you minimize user input because composing any message is unwieldy.

Unless you've standardized on a particular phone, you will need to write vanilla Wireless Markup Language to run on any WML microbrowser. Because of the limited memory of the devices and the low-bandwidth connection, limit Wireless Application Protocol deck sizes to around 3,000 bytes. Some phones can handle graphics, but their effectiveness on the small screen is questionable. Here are other guidelines to keep in mind:

Provide only the information or functionality the user needs at that moment. Wireless applications are more suited for single, rather than multiple, tasks.

Keep it short; you don't need to write correct prose. Just string together meaningful words or phrases, as is done with highway signs.

Minimize text input. Offer pick lists of likely words and numbered menu items.

Simplify navigation. Make it clear where to go next and how to get back.

Use flat menu structures. Users will become lost if they go beyond two levels deep.

Present numbers in tables.

Use simulators to test your design and navigation.

Return to: Developers Brace For Wireless Boom

Back to This Week's Issue
Send Us Your Feedback
Top of the Page