×
Namespaces

Variants
Actions
(Difference between revisions)

Guidelines for Mobile Interface Design

From Nokia Developer Wiki
Jump to: navigation, search
cabezonxdg (Talk | contribs)
(New page: Interface design is a key factor to the success of any application. The guidelines proposed here aim to improve the user experience of mobile applications in general. = Guidelines = == E...)
 
cabezonxdg (Talk | contribs)
(English correction.)
Line 1: Line 1:
Interface design is a key factor to the success of any application. The guidelines proposed here aim to improve the user experience of mobile applications in general.
+
The interface design is a critical factor for the success of any application. The now proposed guidelines seek to improve the user experience and apply to the majority of the applications for mobile devices.
  
 
= Guidelines =
 
= Guidelines =
  
== Enable shortcuts to frequently used features ==
+
== Enable shortcuts for frequently used functions ==
On mobile context time is a critical factor to users. In general they are looking for information 'just in time'. Therefore reducing the number of steps needed by the user to perform regular actions ease its adaptation to the application/device.
+
Time is a critical factor for the users that generally need “Just in time” information in the mobile context. That is why, reducing the amount of steps required for the user to perform frequent operations facilitates his adaptation to the application device.
  
== keep the user informed of their actions ==
+
== Maintain the used informed of its actions ==
Keep the user aware about the application's behavior. It can be done using sounds, dialogs, messages, etc.
+
Always maintain the user informed about what is happening in the application.. It can be done using sounds, dialogs, messages, etc.
  
== Preference for native interface components ==
+
== Follow the device’s interface pattern ==
Using native interface components reduces the learning curve to the application, because the 'look and feel' will be shared among other native applications known by the user. <p>
+
Using the system’s native interface components reduces the learning curve of the user regarding the application once the interface will be similar to others that he is already used to. <p>
Pay attention to the menu positioning on the screen. For example, most of the Nokia devices have the Menu positioned at the left side while the cancel actions are positioned to the right.
+
 
 +
== Positioning of buttons, menus, etc ==
 +
It's a subset of the last section. It is important to pay attention to the menu positioning on the screen. For example, in the Nokia devices in general have the application trigger located on the left side of the screen while on the right is located the trigger used to cancel an action. The same positioning is used for YES/NO actions.
  
 
= References =  
 
= References =  

Revision as of 04:03, 24 May 2009

The interface design is a critical factor for the success of any application. The now proposed guidelines seek to improve the user experience and apply to the majority of the applications for mobile devices.

Contents

Guidelines

Enable shortcuts for frequently used functions

Time is a critical factor for the users that generally need “Just in time” information in the mobile context. That is why, reducing the amount of steps required for the user to perform frequent operations facilitates his adaptation to the application device.

Maintain the used informed of its actions

Always maintain the user informed about what is happening in the application.. It can be done using sounds, dialogs, messages, etc.

Follow the device’s interface pattern

Using the system’s native interface components reduces the learning curve of the user regarding the application once the interface will be similar to others that he is already used to.

Positioning of buttons, menus, etc

It's a subset of the last section. It is important to pay attention to the menu positioning on the screen. For example, in the Nokia devices in general have the application trigger located on the left side of the screen while on the right is located the trigger used to cancel an action. The same positioning is used for YES/NO actions.

References

[1] - G ONG , J., AND TARASEWICH , P. 2004. Guidelines for handheld device interface design. In Proceedings of DSI 2004.

[2] - Programming Mobile Devices: An Introduction for Practitioners by Tommi Mikkonen. Wiley & Sons. ISBN-10: 0470057386

839 page views in the last 30 days.
×