Application State Management
From MobileDesign
[edit] Applies to:
User Interface: Included,
Excluded
Hardware: Category: Thing,
Category: Another thing
The application state includes what screen is being displayed, what data the user has entered, and any user settings.
[edit] Design
Good state management involves four practices:
- Save all user input except passwords.
- 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.
[edit] Applicable Devices and Platforms
All devices, any application platform or web.
[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.
Also see: Any that apply, Else remove it entirely
