Editing Legacy Maemo 5 Documentation/Human Interface Guidelines/Reality Checks

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.

=Reality Checks=
This chapter provides guidance for improving usability within applications, even beyond standard testing procedures. (Other very useful information can be found in the [http://library.gnome.org/devel/hig-book/2.26/reality-checks.html.en Checklists Section] of the GNOME HIG.)

==Hardware Keys==
Determine which hardware keys or buttons on the mobile device that is being tested might be assigned to various functions within the application. This is a good way discover whether or not certain functionality might only need hardware control rather than onscreen menus or options. For instance, most mobile devices have a hardware for volume. In this case, users are fairly comfortable with using a standardized hardware key and most likely don't need the function repeated onscreen.

==Different Devices==
Given the inherent differences in the selection of mobile devices on the market, it is common that certain features within an application might not always translate between devices -- some features may not work altogether. Therefore, it extremely important either test applications in as many devices as possible or allow device users to provide feedback about issues they may be experiencing.

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)

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

Personal tools

Navigation

Views

Editing Legacy Maemo 5 Documentation/Human Interface Guidelines/Reality Checks

@@ Line 1: / Line 1: @@
-{{Legacy documentation}}
+=Reality Checks=
+This chapter provides guidance for improving usability within applications, even beyond standard testing procedures. (Other very useful information can be found in the [http://library.gnome.org/devel/hig-book/2.26/reality-checks.html.en Checklists Section] of the GNOME HIG.)
-The sections in this chapter give advices on how to make your application even more usable when it can already be tested. For more information on useful checks, see GNOME HIG [http://library.gnome.org/devel/hig-book/2.26/reality-checks.html.en Checklists Section].
 ==Hardware Keys==
+Determine which hardware keys or buttons on the mobile device that is being tested might be assigned to various functions within the application. This is a good way discover whether or not certain functionality might only need hardware control rather than onscreen menus or options. For instance, most mobile devices have a hardware for volume. In this case, users are fairly comfortable with using a standardized hardware key and most likely don't need the function repeated onscreen.
-Check the keys of the mobile device you are testing your application with to see if you can assign to the keys any already existing or new functions. This way you can find out that some actions do not need an actual control on screen because you can assign them to a commonly used hardware key.
 ==Different Devices==
+Given the inherent differences in the selection of mobile devices on the market, it is common that certain features within an application might not always translate between devices -- some features may not work altogether. Therefore, it extremely important either test applications in as many devices as possible or allow device users to provide feedback about issues they may be experiencing.
-Because of the plurality of mobile devices and their differences, some features of your application may not behave as desired in one device or another. Therefore, you must either test the feature with those devices or let those devices' users give you feedback about it.