Legacy Maemo 5 Documentation/Human Interface Guidelines/Reality Checks - Revision history

amigadave: wikify slightly

2010-10-18T13:42:37Z

wikify slightly

← Older revision		Revision as of 13:42, 18 October 2010
Line 1:		Line 1:
	{{Legacy documentation}}		{{Legacy documentation}}

-	~~=Reality Checks=~~
	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].		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 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.		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==
		+
	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.		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.

amigadave: {{Legacy documentation}}

2010-02-12T09:28:08Z

← Older revision		Revision as of 09:28, 12 February 2010
Line 1:		Line 1:
		+	{{Legacy documentation}}
		+
	=Reality Checks=		=Reality Checks=
	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].		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].

msoini: Documentation/Maemo 5 Developer Guide/Human Interface Guidelines/Reality Checks moved to Legacy Maemo 5 Documentation/Human Interface Guidelines/Reality Checks: Phase out from Maemo Developer Guide, superceded by Official Nokia Forum documentation

2009-10-14T09:12:42Z

Documentation/Maemo 5 Developer Guide/Human Interface Guidelines/Reality Checks moved to Legacy Maemo 5 Documentation/Human Interface Guidelines/Reality Checks: Phase out from Maemo Developer Guide, superceded by Official Nokia Forum documentation

← Older revision

Revision as of 09:12, 14 October 2009

liox_lang_valid: /* Reality Checks */

2009-09-21T08:14:44Z

Reality Checks

← Older revision		Revision as of 08:14, 21 September 2009
Line 1:		Line 1:
	=Reality Checks=		=Reality Checks=
-	The sections in this chapter 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.

twaelti: /* Different Devices */

2009-09-09T09:26:43Z

Different Devices

← Older revision		Revision as of 09:26, 9 September 2009
Line 6:		Line 6:

	==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	+	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.

193.184.83.231: /* Reality Checks */ Fix typo

2009-09-02T21:19:22Z

Reality Checks: Fix typo

← Older revision		Revision as of 21:19, 2 September 2009
Line 1:		Line 1:
	=Reality Checks=		=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 [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. 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==

danielwilms at 15:44, 17 August 2009

2009-08-17T15:44:58Z

← Older revision		Revision as of 15:44, 17 August 2009
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

bijjal: 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...

2009-07-13T20:03:04Z

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

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 [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.