×
Namespaces

Variants
Actions
(Difference between revisions)

Games usability design guidelines

From Nokia Developer Wiki
Jump to: navigation, search
Rahulsingh1m (Talk | contribs)
hamishwillee (Talk | contribs)
m (Text replace - "Category:Mobile Design" to "")
 
(9 intermediate revisions by 3 users not shown)
Line 1: Line 1:
[[Category:Mobile_Design]][[Category:Usability]]
+
[[Category:Usability]][[Category:Games]]
 +
{{Abstract|This article contains some guidelines for games usability. For more information see [http://www.developer.nokia.com/Resources/Library/Design_and_UX/#!designing-different-applications/game-design.html Game Design] (Design and User Experience Library). }}
 +
{{SeeAlso|[http://www.developer.nokia.com/Resources/Library/Design_and_UX/#!designing-different-applications/game-design.html Game Design] (Design and User Experience Library)}}
 +
{{ArticleMetaData <!-- v1.2 -->
 +
|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 -->
 +
|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= [[User:SannaH]]
 +
|review-timestamp= 20120507
 +
|update-by= <!-- After significant update: [[User:username]]-->
 +
|update-timestamp= <!-- After significant update: YYYYMMDD -->
 +
|creationdate= 20090625
 +
|author= [[User:Rahulsingh1m]]
 +
}}
  
== Here are some important Games usability guidelines ==
+
== 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.
 +
* Use splash screens in case the game takes a lot of time to load at first run.
  
 
== Related links ==
 
== Related links ==
  
* [http://wiki.forum.nokia.com/index.php/Symbian_C%2B%2B_Games_Articles Symbian C++ Games Articles]
+
* [[Symbian C++ Games Articles]]
* [http://wiki.forum.nokia.com/index.php/Java_Games_Articles Java Games Articles]
+
* [[Java Games Articles]]

Latest revision as of 06:42, 9 May 2012

This article contains some guidelines for games usability. For more information see Game Design (Design and User Experience Library).

See Also

Game Design (Design and User Experience Library)
Article Metadata
Article
Created: User:Rahulsingh1m (25 Jun 2009)
Reviewed: SannaH (07 May 2012)
Last edited: hamishwillee (09 May 2012)

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

[edit] Related links

This page was last modified on 9 May 2012, at 06:42.
70 page views in the last 30 days.
×