×
Namespaces

Variants
Actions
Revision as of 05:22, 16 November 2011 by hamishwillee (Talk | contribs)

Mobile Application State Management

From Nokia Developer Wiki
Jump to: navigation, search
Article Metadata
Article
Created: User:Aadhar14b (31 Oct 2009)
Last edited: hamishwillee (16 Nov 2011)
Original article published at Little Spring Design under Attribution 3.0


Contents

Introduction

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

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.

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.

When Used

Application state management should be considered for any application.

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

112 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.

×