Legacy Maemo 5 Documentation/Human Interface Guidelines/Reality Checks

(New page: =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 [ht...)
Line 1: Line 1:
=Reality Checks=
=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 chapeter give advices on how to make your application even more usable when it can already be tested. Other very useful checks can be found in the GNOME HIG [http://library.gnome.org/devel/hig-book/2.26/reality-checks.html.en Checklists Section].
==Hardware Keys==
==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're testing your application with to see they could be assigned any functions already existing or new functions. This way you might find out that some actions by not need an actual control on screen as they could be assigned to a commonly used hardware key.
==Different Devices==
==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.
+
Given the plurality of mobile devices out there and their differences, you'll maybe find out that some features of your application do not behave as desired in one device or another. Therefore, it extremely important to be able to either test it in those devices or let those devices users give you feedback about it

Revision as of 15:44, 17 August 2009

Reality Checks

The sections in this chapeter give advices on how to make your application even more usable when it can already be tested. Other very useful checks can be found in the GNOME HIG Checklists Section.

Hardware Keys

Check the keys of the mobile device you're testing your application with to see they could be assigned any functions already existing or new functions. This way you might find out that some actions by not need an actual control on screen as they could be assigned to a commonly used hardware key.

Different Devices

Given the plurality of mobile devices out there and their differences, you'll maybe find out that some features of your application do not behave as desired in one device or another. Therefore, it extremely important to be able to either test it in those devices or let those devices users give you feedback about it

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