Automatic lifecycle management for pages on a mobile application

• US 9,792,006 B2
• Filed: 04/18/2014
• Issued: 10/17/2017
• Est. Priority Date: 09/29/2011
• Status: Active Grant

• Current Assignee: Microsoft Technology Licensing LLC (Microsoft Corporation)
• Original Assignee: Microsoft Technology Licensing LLC (Microsoft Corporation)
• Inventors: Singh, Siddharth, Shah, Nirav Y.
• Primary Examiner(s): Angkool, David Phantana
• Application Number:
  US14/256,283
• Publication Number:
  US 20140229849A1
• Time in Patent Office: 1,278 Days
• Field of Search: 715854
• CPC Class Codes: G06F 3/0484 for the control of specific functions or operations, e.g. selecting or manipulating an object, an image or a displayed text element, setting a parameter value or selecting a range
• CPC Class Codes: G06F 9/451 Execution arrangements for user interfaces
• CPC Class Codes: G06F 9/461 Saving or restoring of program or task context

Abstract

User interface state (UI) information (such as UI control values) are stored and revived when the user navigates and returns to an application. When an instance of a page is created, the page registers with a tombstone list and indicates which page state information on the page is to be stored and revived when a user navigates away from the application. When the user provides an input indicating navigation away from the application, the application accesses the tombstone list and stores the UI page state information. UI page state information is stored in a page state dictionary data structure that corresponds to the current instance of the page. Then, when the user navigates back to the application, the application accesses the page state dictionary and restores the values of the UI page state information so that the user interface display is in the same state as when the user navigated away from the application.

Claims

1. A computer-implemented method comprising:

generating an instance of a user interface page, for an application, on a mobile device;

registering an identification of page state information in a data structure, the page state information corresponding to the instance of the user interface page;

receiving an indication of a request to navigate away from the instance of the user interface page for the application;

based on the instance of the user interface page, storing values, for the page state information registered in the data structure, wherein the values are stored in an instance-specific data structure corresponding to the instance of the user interface page;

receiving an indiction of a request to navigate back to the instance of the user interface page of the application;

based on the indiction of the request to navigate back to the instance of the user interface page, accessing the instance-specific data structure corresponding to the instance of the user interface page; and

generating the instance of the user interface page using the values for the page state information stored in the instance-specific data structure.

2. The computer-implemented method of claim 1 and further comprising:

prior to generating the instance of the user interface page, launching the application.

3. The computer-implemented method of claim 1 wherein generating the instance of the user interface page comprises:

requesting registration of predefined page state information for which the values are to be stored, wherein the registration is requested using functionality corresponding to a class of pages from which the instance of the user interface page derives.

4. The computer-implemented method of claim 3 wherein requesting registration of predefined page state information comprises:

requesting registration of predefined controls on the instance of the user interface page.

5. The computer-implemented method of claim 1 wherein the identification of page state information stored in the data structure comprises an identification of items of user interface page state information, each of which has an associated state and value, corresponding to the instance of the user interface page.

6. The computer-implemented method of claim 5 wherein storing values for the page state information registered in the data structure comprises:

accessing the data structure and selecting one of the items identified in the data structure;

obtaining from the instance of the user interface page, the state and value associated with the selected item; and

storing the state and value associated with the selected item in the instance-specific data structure corresponding to the instance of the user interface page.

7. The computer-implemented method of claim 1 and further comprising:

prior to accessing the instance-specific data structure,

determining whether the application was navigated away from or was suspended because the mobile device was locked since a last time the instance of the user interface page was displayed; and

based on the determination, accessing the instance-specific data structure to retrieve the values for the page state information.

8. The computer-implemented method of claim 1, wherein the instance of the user interface page comprises a first user interface page for the application, and the data structure comprises a first data structure, the method further comprising:

prior to receiving a request to navigate away from the application, receiving a request to navigate to a second user interface page for the application, from within the first user interface page; and

storing the values for the page state information registered in the first data structure, for the first user interface page, in response to the request to navigate to the second user interface page.

9. A mobile device, comprising:

a processor; and

memory storing instructions executable by the processor, wherein the instructions configure the mobile device to;

generate with first and second user interface pages for an application, wherein each of the first and second user interface pages comprises storage and revival functionality for storing and reviving user interface page state information corresponding to the respective user interface page;

receive an indication of a request to navigate away from the application;

based on the indication of the request to navigate away from the application, storing user interface page state information from one of the first or second user interface page, that is open in the application;

receive in an indication of a request to navigate back to the application; and

based on the indication of the request to navigate back to the application, restoring the stored user interface page state information to the one of the first or second user interface page.

10. The mobile device of claim 9, wherein the first and second user interface pages derive from a page class associated with a utilities entity that has the storage and revival functionality, the first and second user interface pages inheriting the storage and revival functionality of the page class.

11. The mobile device of claim 10 wherein the application comprises a business related application.

12. The mobile device of claim 11 wherein the application comprises a customer relations management application.

13. The mobile device of claim 9 and further comprising:

a data store storing a list

wherein, for each respective page of the first and second user interface pages, the storage and revival functionality is configured to register all types of page state information that are to be stored and retrieved for the respective page when the respective page is created.

14. The mobile device of claim 13 and further comprising:

a page state dictionary data store configured to store an instance-specific state dictionary,

wherein, for each respective page of the first and second user interface pages, the storage and revival functionality is configured to execute a storage function when the instance of the respective page is navigated away from, wherein the storage function comprises accessing the list and storing current page state values corresponding to each type of page state information for the instance of the respective page.

15. The mobile device of claim 14 wherein, for each respective page of the first and second user interfaces pages, the storage and revival functionality is configured to:

execute a retrieval function by accessing the list and retrieving from the instance-specific state dictionary the current page state values corresponding to each type of page state information for the instance of the respective page and

restore the retrieved current page state values to the instance of the respective page when the application navigates back to the instance of the respective page.

16. The mobile device of claim 15 wherein, for each respective page of the first and second user interface pages, the storage and revival functionality is configured to:

execute the revival function for the instance of the respective page only if the application has been navigated away from since the storage function was performed for the respective page.

17. The mobile device of claim 9 wherein the first and second user interface pages each have controls thereon that have control values that are configured to be set based on an indication of user input, and wherein the user interface page state information comprises the control values.

18. A hardware computer readable storage medium, storing computer readable instructions which, when executed by a computer, cause the computer to perform steps comprising:

generating an instance of a user interface page, for an application, for display on a mobile device;

registering an identification of page state information types in a data structure, the page state information types corresponding to the instance of the user interface page;

receiving an indication of a request to navigate away from the instance of the user interface page for the application;

based on the instance of the user interface page, storing page state values, for the page state information types registered in the data structure, wherein the page state values are stored in an instance-specific data structure corresponding to the instance of the user interface page;

receiving an indication of a request to navigate back to the instance of the user interface page of the application;

based on the indication of a request to navigate back to the instance of the user interface page, accessing the instance-specific data structure corresponding to the instance of the user interface page;

retrieving the page state values stored in the instance-specific data structure;

restoring the retrieved page state values to the instance of the user interface page; and

generating the instance of the user interface page using the restored page state values from the instance-specific data structure.

19. The hardware computer readable storage medium of claim 18, the steps further comprising:

determining whether the computer has navigated away from the application; and

obtaining the page state values only if the computer has navigated away from the application.

20. The hardware computer readable medium of claim 19 wherein determining whether the computer has navigated away from the application, comprises:

determining whether the application has received a command from an operating system to deactivate the application.