Editing Legacy Maemo 5 Documentation/Human Interface Guidelines/Usability Principles

Warning: You are not logged in. Your IP address will be recorded in this page's edit history.

The edit can be undone. Please check the comparison below to verify that this is what you want to do, and then save the changes below to finish undoing the edit.

Learn more about Contributing to the wiki.

=Copyright=
Partial Copyright © 2002-2008 Calum Benson, Adam Elman, Seth Nickell, colin z robertson

=Usability Principles=
This section outlines some basic principles that are core to the development of touch interfaces and mobile applications. Concepts introduced later in this document build upon the principles in this section. Although the [http://library.gnome.org/devel/hig-book/stable/principles.html.en Principles Section of GNOME HIG] is not directly related to mobile applications, it is a very useful reference, and the reader should be familiar with it as well.

==Diversity==
Mobile devices have a wide variety of available hardware. For example, some devices have special buttons to raise the volume, to call a menu, to navigate through the menus, etc. Other devices might not have any of these buttons. Because of this diversity, avoid using icons or actions that are intimately related to a specific device or brand. For example, don't use a mouse icon with a button highlighted to suggest a user "click". Also, avoid messages that mention specific hardware features, such as "Use the menu button to..." (unless referring to a graphical button). The developer only controls the software's user interface and cannot depend on any particular hardware features.

==Size Matters==
===Screen size===
A mobile device is neither a desktop nor a laptop computer. Screen size is an obvious and important difference. Interacting with an application on the small screen of a mobile device is a very different experience than working with a standard computer screen.

Remember that mobile device screens are not only small, but they vary widely in size and dimensions. Do not assume that your user's device will have the same size screen as the one you are using. Some devices may have a landscape display while others will have a portrait display. Some may even be able to change the display orientation. Mobile applications must be able to adapt to all these displays. Fixed-sized application widgets should be avoided. For example, instead of defining a fixed size for a button, let Hildon adapt that button to the label and screen layout.

===Widget size===
Hildon is designed for touch interfaces. If you wish your application to be finger-friendly, be aware of the size of the widgets with which the user will interact. Small touch areas, such as small buttons, are difficult and frustrating to use.

==Using Fingers==
Since Hildon was designed to be a finger-centric interface, consideration of the end-user must be used when deciding on the placement of widgets within applications. For example, imagine an application that is divided into two columns: the left column for displaying information and the right column for various control widgets. In this case, a left-handed user may be forced to obscure part of the display area with their fingers when touching the control widgets with their left hand. Because of this, it is good practice to allow the user choose their preferred column positions.

Please note that all contributions to maemo.org wiki may be edited, altered, or removed by other contributors. If you do not want your writing to be edited mercilessly, then do not submit it here.
You are also promising us that you wrote this yourself, or copied it from a public domain or similar free resource (see maemo.org wiki:Copyrights for details). Do not submit copyrighted work without permission!

Summary:

Cancel | Editing help (opens in new window)

Templates used on this page:

Template:Ambox (view source) (semi-protected)
Template:Legacy documentation (view source) (semi-protected)
Template:Main (view source) (protected)

Retrieved from "https://wiki.maemo.org/Legacy_Maemo_5_Documentation/Human_Interface_Guidelines/Usability_Principles"

Personal tools

Navigation

Views

Editing Legacy Maemo 5 Documentation/Human Interface Guidelines/Usability Principles

@@ Line 1: / Line 1: @@
-{{Legacy documentation}}
+=Copyright=
+Partial Copyright © 2002-2008 Calum Benson, Adam Elman, Seth Nickell, colin z robertson
+=Usability Principles=
+This section outlines some basic principles that are core to the development of touch interfaces and mobile applications. Concepts introduced later in this document build upon the principles in this section. Although the [http://library.gnome.org/devel/hig-book/stable/principles.html.en Principles Section of GNOME HIG] is not directly related to mobile applications, it is a very useful reference, and the reader should be familiar with it as well.
-This section gives some basic principles that are core to the development of touch interfaces and mobile applications. Concepts introduced later in this document build upon the principles in this section. The principles present in the [http://library.gnome.org/devel/hig-book/2.26/principles.html.en Principles Section] of GNOME HIG, although not so related to mobile applications, are also very useful reference and you should be familiar with them as well.
 ==Diversity==
+Mobile devices have a wide variety of available hardware. For example, some devices have special buttons to raise the volume, to call a menu, to navigate through the menus, etc. Other devices might not have any of these buttons. Because of this diversity, avoid using icons or actions that are intimately related to a specific device or brand. For example, don't use a mouse icon with a button highlighted to suggest a user "click". Also, avoid messages that mention specific hardware features, such as "Use the menu button to..." (unless referring to a graphical button). The developer only controls the software's user interface and cannot depend on any particular hardware features.
-Mobile devices have a wide variety of available hardware. For example, some devices have special buttons to raise the volume, to call a menu, to navigate through the menus, and so on. Other devices may not have any of these buttons. Because of this diversity, avoid using icons or actions that are intimately related to a specific device or brand. For example, do not use a mouse icon with one of its buttons highlighted to suggest the user to click. Also, avoid messages that mention specific hardware features like "Use the menu button to..." (unless you are referring to a graphical button). The developer only controls the software's user interface and cannot depend on any particular hardware features.
 ==Size Matters==
+===Screen size===
+A mobile device is neither a desktop nor a laptop computer. Screen size is an obvious and important difference. Interacting with an application on the small screen of a mobile device is a very different experience than working with a standard computer screen.
-{{main|Legacy Maemo 5 Documentation/Graphical UI Tutorial/Additions to GTK+#Hildon size types}}
+Remember that mobile device screens are not only small, but they vary widely in size and dimensions. Do not assume that your user's device will have the same size screen as the one you are using. Some devices may have a landscape display while others will have a portrait display. Some may even be able to change the display orientation. Mobile applications must be able to adapt to all these displays. Fixed-sized application widgets should be avoided. For example, instead of defining a fixed size for a button, let Hildon adapt that button to the label and screen layout.
-A mobile device is neither a desktop nor a laptop computer. Screen size is an obvious and important difference. Small size screens make the interaction with an application a very different experience than working with a standard computer screen.
+===Widget size===
+Hildon is designed for touch interfaces. If you wish your application to be finger-friendly, be aware of the size of the widgets with which the user will interact. Small touch areas, such as small buttons, are difficult and frustrating to use.
-Remember that mobile device screens are not only small, but they vary widely in size and dimensions. Do not assume that your user's device will have the same screen size as the one you are using. Some devices have a landscape display while others have a portrait display. Some are even able to change the display orientation. Mobile applications must adapt to all these displays. Avoid fixed-sized application widgets. For example, instead of defining a fixed size for example for a button, let Hildon itself adapt that button to the label and screen layout.
-Hildon is designed for touch interfaces and if you wish your application to be finger-friendly, be aware of the size of the widgets with which the user interacts. Small touch surfaces, such as small buttons, are difficult and frustrating to use.
 ==Using Fingers==
+Since Hildon was designed to be a finger-centric interface, consideration of the end-user must be used when deciding on the placement of widgets within applications. For example, imagine an application that is divided into two columns: the left column for displaying information and the right column for various control widgets. In this case, a left-handed user may be forced to obscure part of the display area with their fingers when touching the control widgets with their left hand. Because of this, it is good practice to allow the user choose their preferred column positions.
-Being designed to be used by fingers, Hildon also requires some changes in what comes to the widget's placement in the application. For example, consider an application divided in two columns, the left one that displays information, and the right one that holds control widgets. If the users are left-handed, they may cover up the display area with their fingers when touching the control widgets. Letting the users choose the position of the mentioned areas is good but a better approach is to place the control widgets in the bottom and the information on top of them, if possible.