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 over the next few weeks. Thanks for all your past and future contributions.
Mobile Application State Management
m (Fix external links in internal format)
m (Fixing broken link to Little Springs. Blog links were changed but articles are still there and it is necessary to search using site:littlespringsdesign.com)
|Line 1:||Line 1:|
'''Original article published at [http://
'''Original article published at [http://.littlespringsdesign.com// Little Spring Design] under [http://creativecommons.org/licenses/by/3.0/ Attribution 3.0]'''
Revision as of 12:54, 11 June 2011
The mobile application state includes what screen is being displayed, what data the user has entered, and any user settings.
- 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.
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.
Application state management should be considered for any application.
- 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