×
Namespaces

Variants
Actions
(Difference between revisions)

Games usability design guidelines

From Nokia Developer Wiki
Jump to: navigation, search
hamishwillee (Talk | contribs)
m (moved Games usability to Games usability design guidelines: More useful topic title)
hamishwillee (Talk | contribs)
m (Hamishwillee - Bot update - Fix metadata etc)
Line 1: Line 1:
 
[[Category:Mobile Design]][[Category:Usability]][[Category:Games]]
 
[[Category:Mobile Design]][[Category:Usability]][[Category:Games]]
{{ArticleMetaData <!-- v1.1 -->
+
{{ArticleMetaData <!-- v1.2 -->
 
|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]] -->
 
|installfile= <!-- Link to installation file (e.g. [[Media:The Installation File.sis]]) -->
 
|installfile= <!-- Link to installation file (e.g. [[Media:The Installation File.sis]]) -->
Line 11: Line 11:
 
|capabilities= <!-- Capabilities required by the article/code example (e.g. Location, NetworkServices. -->
 
|capabilities= <!-- Capabilities required by the article/code example (e.g. Location, NetworkServices. -->
 
|keywords= <!-- APIs, classes and methods (e.g. QSystemScreenSaver, QList, CBase -->
 
|keywords= <!-- APIs, classes and methods (e.g. QSystemScreenSaver, QList, CBase -->
|id= <!-- Article Id (Knowledge base articles only) -->
 
 
|language= <!-- Language category code for non-English topics - e.g. Lang-Chinese -->
 
|language= <!-- Language category code for non-English topics - e.g. Lang-Chinese -->
 
|translated-by= <!-- [[User:XXXX]] -->
 
|translated-by= <!-- [[User:XXXX]] -->

Revision as of 08:04, 7 May 2012

Article Metadata
Article
Created: User:Rahulsingh1m (25 Jun 2009)
Last edited: hamishwillee (07 May 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

67 page views in the last 30 days.