Previous Next |
Design Considerations for Consumer ProductsSome principles for designing consumer-product UIs are independent of the product's domain. This section covers some of these principles. See Information Appliances and Beyond: Interaction Design for Consumer Products [1] for more information. SimplifySimplifying UIs is an objective for all designers. For consumer products, you can make a trade-off of functionality and choice against simplicity. Functionality Versus SimplicityThe more functionality included in a product, the more difficult it is to learn and to use. On the other hand, gratuitous elimination of functionality can lead to a product that is too limited to support consumers' needs. Strive for the functionality threshold—the right collection and number of features to strike a balance between functionality and simplicity. app Developers and MIDP Implementors
Choice Versus SimplicityChoice is useful when it is appropriate, but too much choice can create a complicated, perhaps overwhelming, situation. For example, consider replying to an email. An email app could give you the choice of replying to the sender and including the original mail in the reply, replying to the sender without including the original mail, replying to everyone who received the original mail and including the original mail in the reply, and replying to everyone who received the original mail without including it in the reply. app Developers and MIDP Implementors
Make It PredictableUsability testing has shown that consumers are much happier with systems that are predictable, even at the cost of efficiency. app Developers and MIDP Implementors
For example, assume that an address tutorial app and an email app on a mobile phone have menus that display the available operations, and the address tutorial has a menu element called New Entry for adding a record. The question for the email app is whether its list element for writing a new message should be called Write or New Message. Using New Message is parallel to New Entry in the address tutorial, which makes it an attractive option. It makes the address tutorial and email apps more consistent. Consumers, though, do not think about creating a new message; they think of writing to someone. For them, Write would probably be a better predictor of the command's behavior.
MIDP Implementors
Streamline Important Tasks for Efficiencyapp Developers and MIDP Implementors
When you consider this recommendation remember that predictability is more important than efficiency in a consumer product. One way to minimize navigation is to design apps with shallow hierarchies so that consumers do not find themselves going from screen to screen to screen, and then back, back, back. app Developers
Make It ResponsiveConsumers expect immediate response to their input. When a response is not immediate, they can become annoyed, repeatedly press buttons, or assume the device is broken. They may stop using the device. app Developers and MIDP Implementors
Responsiveness starts with immediate feedback and goes beyond it to intelligent responses. MIDP Implementors
Provide Constant, Unobtrusive FeedbackThe users of consumer products need reassurance that the device is functioning correctly, even when nothing important is going on. MIDP Implementors
For example, most mobile phones have a signal strength indicator, which is active when the phone is on. Its feedback is crucial when making phone calls. The indicator is positioned so that it does not interfere with the display of other information. Screenshot shows the signal strength indicator in the MIDP Reference Implementation. Screenshot Signal Strength Feedback on a Mobile Phoneapp Developers and MIDP Implementors
Screenshot shows the images for a slow, even animation that indicates network activity. Screenshot Animation Indicating ActivityMake Everything InterruptibleConsumers should always be able to cancel, power off, or simply interrupt the device in order to do something else, even when there is a message that requires a response on the screen or they are in the middle of a task. If a person is in the middle of an activity, the consumer should be able to start over at the beginning of that activity without penalty. app Developers and MIDP Implementors
For example, when a PDA shows a modal alert (a message on a screen that the user must dismiss), the consumer should be able to dismiss it not only by tapping a particular button but also by tapping outside the alert. Similarly, if a consumer is writing an email message and wants to go to another app, the device should automatically save the message as a draft without displaying error messages or prompts. Allowing a user to interrupt anything keeps control of the product in the hands of the consumer. People are more comfortable with products they control. Minimize Interruptions From MIDP and MIDletsConsumers should not be interrupted and required to respond unless it is absolutely necessary. Confirmation messages, unnecessary feedback, and error messages that require a response detract from the user experience. app Developers and MIDP Implementors
It can be difficult to decide when a particular piece of information is critical. For example, consider consumers downloading apps onto mobile phones. If network connections are lost, the losses can be considered critical information that lets consumers know that they should reconnect. Another approach, though, is to have the devices automatically try to reconnect and unobtrusively display that status. The second approach keeps interruptions to a minimum. When deciding how to handle this situation, consider the cost to the consumer for the connection, as well as the consumer's time. app Developers and MIDP Implementors, Continued
This approach allows consumers to decipher critical information and maintains their confidence in the device. Check Your Designs with OthersIn any design process, it is valuable to periodically check your designs against the wants and expectations of your audience. You could do this by comparing your design to product-marketing requirements, visiting prospective customers, and evaluating competing products. app Developers and MIDP Implementors
See "Bibliography" on page 243 for sources of information on these techniques. |
Previous Next |