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. Thanks for all your past and future contributions.

(Difference between revisions)

Mobile Application State Management

From Wiki
Jump to: navigation, search
marcelobarrosalmeida (Talk | contribs)
m (Fixing broken link to Little Springs. Blog links were changed but articles are still there and it is necessary to search using
hamishwillee (Talk | contribs)
m (Text replace - "Category:Mobile Design" to "")
(2 intermediate revisions by one user not shown)
Line 1: Line 1:
'''Original article published at [ Little Spring Design] under [ Attribution 3.0]'''
{{ArticleMetaData <!-- v1.2 -->
|sourcecode= <!-- Link to example source code e.g. [[Media:The Code Example]] -->
|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/ Nokia Qt SDK 1.1]) -->
|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= <!-- 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= 20091031
|author= [[User:Aadhar14b]]
}}'''Original article published at [ Little Spring Design] under [ Attribution 3.0]'''
Line 24: Line 45:
--Submitted by - Aadhar14b[[Category:Mobile Design]][[Category:Usability]]
--Submitted by - Aadhar14b[[Category:Usability]]

Latest revision as of 03:42, 9 May 2012

Article Metadata
Created: User:Aadhar14b (31 Oct 2009)
Last edited: hamishwillee (09 May 2012)
Original article published at Little Spring Design under Attribution 3.0


[edit] Introduction

The mobile application state includes what screen is being displayed, what data the user has entered, and any user settings.

[edit] Design Guidelines

  • Save all user input except passwords.
  • To enable saving of password provide an option.
  • Discard task-related input only after the task is complete.
  • Save application state, including which screen is being displayed.
  • When re-entering the application, return the user to that state is appropriate. It might not be appropriate if the user was viewing transient data or if the application has not been used for a few days.

[edit] Example

gmaps on S60 when you refire a saved search, it re-runs it in the last location. Regardless of not having gps. Assume last info is correct unless there is a reason not to.

[edit] When Used

Application state management should be considered for any application.

[edit] Rationale

  • The user, and hence the application, is readily interruptible. The application can be interrupted at any time, by real life people, an incoming call, or a coverage hole.
  • Thus an exited application does not indicate the user's intent to end a task.

--Submitted by - Aadhar14b

This page was last modified on 9 May 2012, at 03:42.
56 page views in the last 30 days.