Legacy Maemo 5 Documentation/Human Interface Guidelines/Reality Checks

(wikify slightly)
 
(5 intermediate revisions not shown)
Line 1: Line 1:
-
=Reality Checks=
+
{{Legacy documentation}}
-
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].
+
 
 +
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==
==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.
+
 
 +
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==
==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
+
 
 +
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.

Latest revision as of 13:42, 18 October 2010

Image:Ambox_content.png
This article is legacy documentation, and is superseded by Forum Nokia documentation.
The Forum Nokia documentation is available as the Hildon 2.2 UI style guide, Fremantle master layout guide and the Hildon 2.2 widget UI specification

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 Checklists Section.

[edit] Hardware Keys

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.

[edit] Different Devices

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.