×
Namespaces

Variants
Actions
(Difference between revisions)

General mobile app design guidelines

From Nokia Developer Wiki
Jump to: navigation, search
hamishwillee (Talk | contribs)
m (Hamishwillee - Tidy wiki text)
hamishwillee (Talk | contribs)
m (Hamishwillee - Bot update - Fix metadata etc)
Line 1: Line 1:
 
[[Category:Mobile Design]][[Category:Usability]]
 
[[Category:Mobile Design]][[Category:Usability]]
{{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:56, 7 May 2012

Article Metadata
Article
Created: User:Rahulsingh1m (26 Jun 2009)
Last edited: hamishwillee (07 May 2012)
  • While switching to background the application should act correctly, e.g. backlight should be turned off, sounds should be paused.
  • Application should pause on high priority system interrupts, like incoming call, messages.
  • User should be able to switch to other applications.
  • Application should be paused in case of low battery, and should give an option to save the application state and close.
  • The audio level of the application should be in sync with the selected profile.
  • User can resume the application smoothly after a paused state.
  • Application should not behave abnormally in case the user provides a wrong input. A proper error message should be displayed to user.
  • Application should not exit by its own in case of low memory condition. At least a notification should be given to the user.
  • Application should handle all screen orientation properly. If it does not support landscape mode, then it should display proper message.
68 page views in the last 30 days.
×