Application processing method and apparatus for jumping between child applications and storage medium

1. An application processing method, applied to a terminal, comprising:

displaying a first child application page of a first child application, the first child application being run by a parent application;

acquiring, by the first child application, a second child application identifier corresponding to a second child application to be jumped to;

adding the second child application identifier to an end of a jump path when the second child application identifier does not exist in the jump path, wherein the jump path records one or more child application identifiers arranged in a sequence based on one or more previous jumps;

moving the second child application identifier to an end of the jump path when the second child application identifier exists in the jump path;

running, by the parent application, the second child application when a jump is made from the first child application to the second child application;

upon detecting a close instruction of the second child application and that a first native plug-in child application identifier exists before a foremost third-party child application identifier in the jump path, returning to a first native plug-in child application corresponding to the first native plug-in child application identifier; and

upon detecting the close instruction and that the first native plug-in child application identifier does not exist before the foremost third-party child application identifier in the jump path, returning to the parent application,

wherein returning to the first native plug-in child application corresponding to the first native plug-in child application identifier comprises:

when more than one first native plug-in child application identifier exists before the foremost third-party child application identifier in the jump path,

acquiring a second native plug-in child application identifier, wherein the second native plug-in child application identifier is adjacent to the first third-party child application identifier and is located before the first third-party child application identifier;

determining a second native plug-in child application page, wherein the second native plug-in child application page is a page corresponding to a second native plug-in child application corresponding to the second native plug-in child application identifier during a jump; and

displaying the second native plug-in child application page.

2. The method according to claim 1 , further comprising:

acquiring a return instruction from a current child application;

determining a current child application identifier in response to the return instruction;

searching the jump path for a third child application identifier immediately preceding the current child application identifier; and

returning to a third child application page corresponding to the third child application identifier.

3. The method according to claim 2 , wherein returning to the third child application page corresponding to the third child application identifier comprises:

when a third child application corresponding to the third child application identifier is run by the parent application in a background state, returning to the third child application page corresponding to the third child application left during a corresponding previous jump; and

when the third child application corresponding to the third child application identifier has finished running, returning to a default child application page corresponding to the third child application identifier.

4. The method according to claim 1 , wherein the second child application comprises a native plug-in child application; and moving the second child application identifier to the end of the jump path when the second child application identifier exists in the jump path comprises:

determining a consecutive native plug-in child application identifier immediately preceding the second child application identifier in the jump path; and

moving the second child application identifier to the end of the jump path, and deleting the consecutive native plug-in child application identifier in the jump path.

5. The method according to claim 1 , further comprising:

when the jump is made from the first child application to the second child application; transferring, by the parent application, page data corresponding to the second child application identifier to the second child application;

generating, according to the page data, a second child application page over the first child application page; and

displaying the second child application page.

6. The method according to claim 5 , wherein transferring the page data corresponding to the second child application identifier to the second child application comprises:

switching to a parent application page used for triggering a child application jump, wherein the parent application page is a page displayed by the parent application;

triggering, by using the parent application page, acquisition of the page data corresponding to the second child application identifier; and

transferring the page data to the second child application.

7. The method according to claim 1 , wherein after acquiring the second child application identifier, the method further comprises:

acquiring a first parent application page identifier corresponding to a switched-to first parent application page; and

when the second child application identifier exists in the jump path,

deleting a second parent application page identifier immediately after the second child application identifier in the jump path;

adding the first parent application page identifier to the end of the jump path; and

moving the second child application identifier to be immediately after the first parent application page identifier.

8. An application processing apparatus, comprising a processor and a memory, the memory storing computer readable instructions, and the instructions causing the processor to perform:

displaying a first child application page of a first child application, the first child application being run by a parent application;

acquiring, by the first child application, a second child application identifier corresponding to a second child application to be jumped to;

adding the second child application identifier to an end of a jump path when the second child application identifier does not exist in the jump path, wherein the jump path records one or more child application identifiers arranged in a sequence based on one or more previous jumps;

moving the second child application identifier to an end of the jump path when the second child application identifier exists in the jump path;

running, by the parent application, the second child application when a jump is made from the first child application to the second child application;

upon detecting a close instruction of the second child application and that a first native plug-in child application identifier exists before a foremost third-party child application identifier in the jump path, returning to a first native plug-in child application corresponding to the first native plug-in child application identifier; and

upon detecting the close instruction and that the first native plug-in child application identifier does not exist before the foremost third-party child application identifier in the jump path, returning to the parent application,

wherein returning to the first native plug-in child application corresponding to the first native plug-in child application identifier comprises:

when more than one first native plug-in child application identifier exists before the foremost third-party child application identifier in the jump path,

acquiring a second native plug-in child application identifier, wherein the second native plug-in child application identifier is adjacent to the first third-party child application identifier and is located before the first third-party child application identifier;

determining a second native plug-in child application page, wherein the second native plug-in child application page is a page corresponding to a second native plug-in child application corresponding to the second native plug-in child application identifier during a jump; and

displaying the second native plug-in child application page.

9. The apparatus according to claim 8 , wherein the computer readable instructions further cause the processor to perform:

acquiring a return instruction from a current child application;

determining a current child application identifier in response to the return instruction;

searching the jump path for a third child application identifier immediately preceding the current child application identifier; and

returning to a third child application page corresponding to the third child application identifier.

10. The apparatus according to claim 9 , wherein returning to the third child application page corresponding to the third child application identifier comprises:

when a third child application corresponding to the third child application identifier is run by the parent application in a background state, returning to the third child application page corresponding to the third child application left during a corresponding previous jump; and

when the third child application corresponding to the third child application identifier has finished running, returning to a default child application page corresponding to the third child application identifier.

11. The apparatus according to claim 8 , wherein the second child application comprises a native plug-in child application; and moving the second child application identifier to the end of the jump path when the second child application identifier exists in the jump path comprises:

determining a consecutive native plug-in child application identifier immediately preceding the second child application identifier in the jump path; and

moving the second child application identifier to the end of the jump path, and deleting the consecutive native plug-in child application identifier in the jump path.

12. The apparatus according to claim 8 , wherein the computer readable instructions further cause the processor to perform:

when the jump is made from the first child application to the second child application; transferring, by the parent application, page data corresponding to the second child application identifier to the second child application;

generating, according to the page data, a second child application page over the first child application page; and

displaying the second child application page.

13. The apparatus according to claim 12 , wherein transferring the page data corresponding to the second child application identifier to the second child application comprises:

switching to a parent application page used for triggering a child application jump, wherein the parent application page is a page displayed by the parent application;

triggering, by using the parent application page, acquisition of the page data corresponding to the second child application identifier; and

transferring the page data to the second child application.

14. The apparatus according to claim 8 , wherein after acquiring the second child application identifier, the computer readable instructions further cause the processor to perform:

acquiring a first parent application page identifier corresponding to a switched-to first parent application page; and

when the second child application identifier exists in the jump path,

deleting a second parent application page identifier immediately after the second child application identifier in the jump path;

adding the first parent application page identifier to the end of the jump path; and

moving the second child application identifier to be immediately after the first parent application page identifier.

15. A non-transitory computer readable storage medium storing computer readable instructions, when being executed by a processor, the computer readable instructions causing the processor to perform:

displaying a first child application page of a first child application, the first child application being run by a parent application;

acquiring, by the first child application, a second child application identifier corresponding to a second child application to be jumped to;

adding the second child application identifier to an end of a jump path when the second child application identifier does not exist in the jump path, wherein the jump path records one or more child application identifiers arranged in a sequence based on one or more previous jumps;

moving the second child application identifier to an end of the jump path when the second child application identifier exists in the jump path;

running, by the parent application, the second child application when a jump is made from the first child application to the second child application;

upon detecting a close instruction of the second child application and that a first native plug-in child application identifier exists before a foremost third-party child application identifier in the jump path, returning to a first native plug-in child application corresponding to the first native plug-in child application identifier; and

upon detecting the close instruction and that the first native plug-in child application identifier does not exist before the foremost third-party child application identifier in the jump path, returning to the parent application,

wherein returning to the first native plug-in child application corresponding to the first native plug-in child application identifier comprises:

when more than one first native plug-in child application identifier exists before the foremost third-party child application identifier in the jump path,

acquiring a second native plug-in child application identifier, wherein the second native plug-in child application identifier is adjacent to the first third-party child application identifier and is located before the first third-party child application identifier;

determining a second native plug-in child application page, wherein the second native plug-in child application page is a page corresponding to a second native plug-in child application corresponding to the second native plug-in child application identifier during a jump; and

displaying the second native plug-in child application page.

16. The storage medium according to claim 15 , wherein the computer readable instructions further cause the processor to perform:

acquiring a return instruction from a current child application;

determining a current child application identifier in response to the return instruction;

searching the jump path for a third child application identifier immediately preceding the current child application identifier; and

returning to a third child application page corresponding to the third child application identifier.

17. The storage medium according to claim 16 , wherein returning to the third child application page corresponding to the third child application identifier comprises:

when a third child application corresponding to the third child application identifier is run by the parent application in a background state, returning to the third child application page corresponding to the third child application left during a corresponding previous jump; and

when the third child application corresponding to the third child application identifier has finished running, returning to a default child application page corresponding to the third child application identifier.