Namespaces

Variants
Actions

Please note that as of October 24, 2014, the Nokia Developer Wiki will no longer be accepting user contributions, including new entries, edits and comments, as we begin transitioning to our new home, in the Windows Phone Development Wiki. We plan to move over the majority of the existing entries over the next few weeks. Thanks for all your past and future contributions.

(Difference between revisions)

Games usability design guidelines

From Wiki
Jump to: navigation, search
hamishwillee (Talk | contribs)
m (Bot change of links to internal format.)
hamishwillee (Talk | contribs)
m (Hamishwillee - Bot update - Fix ReviewerApproval and ArticleMetaData etc)
Line 1: Line 1:
{{ReviewerApproved}}
+
{{ArticleMetaData <!-- v1.1 -->
[[Category:Mobile_Design]][[Category:Usability]]
+
|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]]) -->
 +
|devices= <!-- Devices tested against - e.g. ''devices=Nokia 6131 NFC, Nokia C7-00'') -->
 +
|sdk= <!-- SDK(s) built and tested against (e.g. [http://linktosdkdownload/ Qt SDK 1.1.4]) -->
 +
|platform= <!-- Compatible platforms - e.g. Symbian^1 and later, Qt 4.6 and later -->
 +
|devicecompatability= <!-- Compatible devices e.g.: All* (must have internal GPS) -->
 +
|dependencies= <!-- Any other/external dependencies e.g.: Google Maps Api v1.0 -->
 +
|signing= <!-- Signing requirements - empty or one of: Self-Signed, DevCert, Manufacturer -->
 +
|capabilities= <!-- Capabilities required by the article/code example (e.g. Location, NetworkServices. -->
 +
|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 -->
 +
|translated-by= <!-- [[User:XXXX]] -->
 +
|translated-from-title= <!-- Title only -->
 +
|translated-from-id= <!-- Id of translated revision -->
 +
|review-by= <!-- After re-review: [[User:username]] -->
 +
|review-timestamp= <!-- After re-review: YYYYMMDD -->
 +
|update-by= <!-- After significant update: [[User:username]]-->
 +
|update-timestamp= <!-- After significant update: YYYYMMDD -->
 +
|creationdate= 20090625
 +
|author= [[User:Rahulsingh1m]]
 +
}}
 +
 
 +
[[Category:Mobile Design]][[Category:Usability]]
  
 
== Here are some important Games usability guidelines ==
 
== Here are some important Games usability guidelines ==

Revision as of 03:18, 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

113 page views in the last 30 days.

Was this page helpful?

Your feedback about this content is important. Let us know what you think.

 

Thank you!

We appreciate your feedback.

×