×
Namespaces

Variants
Actions
(Difference between revisions)

Games usability design guidelines

From Nokia Developer Wiki
Jump to: navigation, search
hamishwillee (Talk | contribs)
m (Hamishwillee - Bot update - Fix ReviewerApproval and ArticleMetaData etc)
hamishwillee (Talk | contribs)
m (Hamishwillee - Add Games category)
Line 1: Line 1:
 +
[[Category:Mobile Design]][[Category:Usability]][[Category:Games]]
 
{{ArticleMetaData <!-- v1.1 -->
 
{{ArticleMetaData <!-- v1.1 -->
 
|sourcecode= <!-- Link to example source code e.g. [[Media:The Code Example ZIP.zip]] -->
 
|sourcecode= <!-- Link to example source code e.g. [[Media:The Code Example ZIP.zip]] -->
Line 23: Line 24:
 
}}
 
}}
  
[[Category:Mobile Design]][[Category:Usability]]
+
 
  
 
== Here are some important Games usability guidelines ==
 
== Here are some important Games usability guidelines ==
  
 
* Game should be automatically paused on events like incoming calls, messages, alarms etc.
 
* Game should be automatically paused on events like incoming calls, messages, alarms etc.
 
 
* Game should not continue automatically after the paused state.
 
* Game should not continue automatically after the paused state.
 
 
* If the game starts with a story or a video visual, the user should be provided with a skip button.  
 
* If the game starts with a story or a video visual, the user should be provided with a skip button.  
 
 
* Relevent game data like player life, level etc. should be shown.
 
* Relevent game data like player life, level etc. should be shown.
 
 
* Make the keys consistent with the default applications. For example, keys 2 and 4 should be used for horizontal movement, similarly 2 and 8 should be used for vertical movement.
 
* Make the keys consistent with the default applications. For example, keys 2 and 4 should be used for horizontal movement, similarly 2 and 8 should be used for vertical movement.
 
 
* User should be able to change the control keys.
 
* User should be able to change the control keys.
 
 
* Should provide option to enable/disable sound and backlight.
 
* Should provide option to enable/disable sound and backlight.
 
 
* On restart, user can skip the already cleared levels of the game.
 
* On restart, user can skip the already cleared levels of the game.
 
 
* Should provide the option of restart in the menu.
 
* Should provide the option of restart in the menu.
 
 
* Softkey labels should be consistent. For example, use left key for ok, continue, options and use right key for back, cancel, exit.
 
* Softkey labels should be consistent. For example, use left key for ok, continue, options and use right key for back, cancel, exit.
 
 
* Save the state of the game on exit.
 
* Save the state of the game on exit.
 
 
* Context sensitive help should be provided.
 
* Context sensitive help should be provided.
 
 
* Information on the creator of the game in an about option should be provided.
 
* Information on the creator of the game in an about option should be provided.
 
 
* Use splash screens in case the game takes a lot of time to load at first run.
 
* Use splash screens in case the game takes a lot of time to load at first run.
  

Revision as of 06:46, 13 February 2012

Article Metadata
Article
Created: User:Rahulsingh1m (25 Jun 2009)
Last edited: hamishwillee (13 Feb 2012)


Here are some important Games usability guidelines

  • Game should be automatically paused on events like incoming calls, messages, alarms etc.
  • Game should not continue automatically after the paused state.
  • If the game starts with a story or a video visual, the user should be provided with a skip button.
  • Relevent game data like player life, level etc. should be shown.
  • Make the keys consistent with the default applications. For example, keys 2 and 4 should be used for horizontal movement, similarly 2 and 8 should be used for vertical movement.
  • User should be able to change the control keys.
  • Should provide option to enable/disable sound and backlight.
  • On restart, user can skip the already cleared levels of the game.
  • Should provide the option of restart in the menu.
  • Softkey labels should be consistent. For example, use left key for ok, continue, options and use right key for back, cancel, exit.
  • Save the state of the game on exit.
  • Context sensitive help should be provided.
  • Information on the creator of the game in an about option should be provided.
  • Use splash screens in case the game takes a lot of time to load at first run.

Related links

101 page views in the last 30 days.