CN113312570A

CN113312570A - Page jump method, terminal device and storage medium

Info

Publication number: CN113312570A
Application number: CN202010898376.4A
Authority: CN
Inventors: 倪群
Original assignee: Alibaba Group Holding Ltd
Current assignee: Alibaba Group Holding Ltd
Priority date: 2020-08-31
Filing date: 2020-08-31
Publication date: 2021-08-27

Abstract

The embodiment of the application provides a page jump method, terminal equipment and a storage medium. In the embodiment of the application, under the condition of cold start of the application program, the interactive control with the prompt information is displayed on the landing page after the cold start, so that a user is prompted to trigger the interactive control to jump to the history page displayed before the application program is killed, if the user wants to jump to the history page visited before, the user can quickly jump to the history page visited before by triggering the interactive control, the efficiency is high, the problem that the user experiences badly due to interruption caused by killing of the application program in the page visiting process can be solved, and the use experience of the user is improved.

Description

Page jump method, terminal device and storage medium

Technical Field

The present application relates to the field of internet technologies, and in particular, to a page jump method, a terminal device, and a storage medium.

Background

With the development of terminal technology, users can install more and more applications on terminal devices. During use, users often switch from the current application to other applications. When the user switches from the current application program to other application programs, the user can actively kill the current application program, or the current application program can enter a background to run. Wherein, in the case that the application program enters into background running, the application program is easy to be killed by the system.

In any case, after the application program is killed, the application program can be opened again only by cold start, the application program can default to enter the first page after the cold start, and if the user needs to continuously access the previous page, the user needs to retrieve the previous page by accessing the footprint step by step, so that the efficiency is low, and the user experience is poor.

Disclosure of Invention

Aspects of the present disclosure provide a page jump method, a terminal device, and a storage medium, which are used to help a user quickly jump to a previously accessed page after an application program is cold-started.

The embodiment of the application provides a page jump method, which comprises the following steps: responding to the cold start operation of the application program, and displaying a landing page; displaying an interactive control with prompt information on the landing page, wherein the prompt information prompts a user to trigger the interactive control to jump to a history page displayed before the application program is killed; responding to the triggering operation of the user on the interaction control, restoring the historical page according to the page data of the historical page stored before the application program is killed, and jumping to the historical page.

The embodiment of the present application further provides a page jump method, including: responding to the cold start operation of the application program, displaying a landing page, and identifying whether the application program is killed by a system before the cold start operation; and if the application program is killed by the system before the cold start operation, restoring the historical page according to the saved page data of the historical page displayed before the application program is killed, and jumping to the historical page from the landing page.

The embodiment of the present application further provides a page jump method, including: in response to a cold start operation of an application, identifying whether the application was killed by a system prior to the cold start operation; and if the application program is killed by the system before the cold start operation, restoring the history page according to the saved page data of the history page displayed before the application program is killed, and displaying the history page.

An embodiment of the present application further provides a terminal device, including: a memory, a processor and a display screen; the memory is used for storing the program codes of the application programs installed on the terminal equipment; the processor, coupled with the memory, to execute the program code to: responding to the cold start operation of an application program, and displaying a landing page on the display screen; displaying an interactive control with prompt information on the landing page, wherein the prompt information prompts a user to trigger the interactive control to jump to a history page displayed before the application program is killed; responding to the triggering operation of the user on the interaction control, restoring the historical page according to the page data of the historical page stored before the application program is killed, and jumping to the historical page.

An embodiment of the present application further provides a terminal device, including: a memory, a processor and a display screen; the memory is used for storing the program codes of the application programs installed on the terminal equipment; the processor, coupled with the memory, to execute the program code to: displaying a landing page on the display screen in response to a cold start operation of an application program, and identifying whether the application program is killed by a system before the cold start operation; and if the application program is killed by the system before the cold start operation, restoring the historical page according to the saved page data of the historical page displayed before the application program is killed, and jumping to the historical page from the landing page.

An embodiment of the present application further provides a terminal device, including: a memory and a processor; the memory is used for storing the program codes of the application programs installed on the terminal equipment; the processor, coupled with the memory, to execute the program code to: in response to a cold start operation of an application, identifying whether the application was killed by a system prior to the cold start operation; and if the application program is killed by the system before the cold start operation, restoring the history page according to the saved page data of the history page displayed before the application program is killed, and displaying the history page.

Embodiments of the present application further provide a computer-readable storage medium storing a computer program, which, when executed by a processor, causes the processor to implement the steps in the page jump method provided in the embodiments of the present application.

In some embodiments of the application, under the condition of cold start of an application program, an interactive control with prompt information is displayed on a landing page after the cold start, so that a user is prompted to trigger the interactive control to jump to a history page displayed before the application program is killed, if the user wishes to jump to a history page visited before, the user can quickly jump to the history page visited before by triggering the interactive control, the efficiency is high, the problem that the user experiences badly due to interruption caused by killing of the application program in the page visiting process can be solved, and the use experience of the user is improved.

In other embodiments of the present application, in the case of the application cold start, by identifying whether the application is killed by the system before the cold start, if the application is killed by the system before the cold start, it indicates that the user wants to go back to the application again to a great extent and can continue to access the previous page, so that the user can directly jump to the historical page previously accessed by the user, the efficiency of page access is improved, the problem of poor experience caused by interruption of the application due to the application being killed in the page access process can also be solved, and the use experience of the user is improved.

Drawings

The accompanying drawings, which are included to provide a further understanding of the application and are incorporated in and constitute a part of this application, illustrate embodiment(s) of the application and together with the description serve to explain the application and not to limit the application. In the drawings:

fig. 1a is a schematic flowchart of a page jump method according to an exemplary embodiment of the present application;

FIGS. 1 b-1 e are schematic diagrams illustrating a page jump status in a cold start situation of an application according to an exemplary embodiment of the present application;

fig. 1f is a schematic flowchart of another page jump method according to an exemplary embodiment of the present application;

fig. 1g is a schematic structural diagram of a floating layer management system provided in an exemplary embodiment of the present application;

fig. 2a is a schematic flowchart of another page jump method according to an exemplary embodiment of the present application;

2 b-2 c are schematic diagrams of another page jump state in the case of application cold start according to the exemplary embodiment of the present application;

fig. 3 is a schematic flowchart of another page jump method according to an exemplary embodiment of the present application;

fig. 4 is a schematic structural diagram of a terminal device according to an exemplary embodiment of the present application.

Detailed Description

In order to make the objects, technical solutions and advantages of the present application more apparent, the technical solutions of the present application will be described in detail and completely with reference to the following specific embodiments of the present application and the accompanying drawings. It should be apparent that the described embodiments are only some of the embodiments of the present application, and not all of the embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present application.

According to the technical problems of low efficiency, poor experience and the like when a user wants to continuously access a page visited before after the application program is cold started, in some exemplary embodiments of the application program, under the condition of cold start of the application program, an interactive control with prompt information is displayed on a landing page after the cold start, the user is prompted to trigger the interactive control to jump to a history page displayed before the application program is killed, if the user wants to jump to the history page visited before, the user can quickly jump to the history page visited before by triggering the interactive control, the efficiency is high, the problem that the user experiences are poor due to interruption of the application program due to killing in the page visiting process can be solved, and the use experience of the user is improved.

In addition to the technical solutions provided by the above exemplary embodiments, in other exemplary embodiments of the present application, in a case of a cold start of an application, by identifying whether the application was killed by a system before the cold start, if it is identified that the application was killed by the system before, it indicates that a user wants to continue accessing a previous page when the user largely wants to go back to the application again, so that the user can directly jump to a history page previously accessed by the user, the efficiency of page access is improved, a problem of poor experience caused by interruption of the application due to the killing of the application during the page access process by the user can also be solved, and the use experience of the user is improved.

The technical solutions provided by the exemplary embodiments of the present application are described in detail below with reference to the accompanying drawings. Before describing the technical solutions provided in the exemplary embodiments of the present application in detail, the "application" and the "terminal device" in the exemplary embodiments of the present application are explained first. The explanation is applicable to all the embodiments of the present application, and repeated explanation will not be provided in the following embodiments.

In the embodiments of the present application, "application" generally refers to various computer programs developed and running on an operating system for accomplishing a specific task or tasks, and may be, for example, an instant messaging application, an online shopping application, an email application, a game application, a video playing application, a live broadcast application, a map application, a teaching or education application, and the like. It should be noted that the method provided in the embodiment of the present application may be applied to any "application program," and may also be applied to a specific application program, for example, an application program in an online shopping class, or an application program in a video playing class.

In the embodiment of the application, the application program can be installed and run on various terminal devices, and supports a cold start mode. The cold start mode is a start mode that when an application program is started, a background does not have a process of the application program, and an operating system needs to allocate a process to the application program again. Optionally, the "application" in the embodiment of the present application may also support a hot-start mode. The warm boot method is a boot method that is relatively to the cold boot method, and means that when an application program is started, a background already has a process of the application program, and the application program can be directly restored to a last usage state.

The "application" in the embodiment of the present application generally has a plurality of application pages including a top page, and some application pages can jump to each other. Optionally, in the plurality of application pages, an independent page may be included, and a composite page may be included. A compound page refers to a large page that is implemented by multiple independent pages aggregated together. For example, the home page is typically a compound page that includes a plurality of sub-pages, each of which may be implemented as a tab (tab) page.

In addition, in the embodiment of the present application, a first stably displayed application page after the application program is cold-started is referred to as a landing page (i oad i ng page), where the landing page may be a first page of the application program or other pages in the application program, and specifically, the landing page may be different according to a manner of triggering the application program to be cold-started. For example, if the user triggers an application cold start by clicking an icon of "application", the first stably displayed application page after the application cold start is the home page, and the home page is the landing page. For another example, if the user triggers the application cold start in other applications through a link of a certain non-top page (for example, a certain item detail page) in the application, the first stably displayed application page after the application cold start is the non-top page (for example, a certain item detail page) corresponding to the link, and then the non-top page (for example, a certain item detail page) corresponding to the link is the landing page.

In the embodiment of the present application, the implementation form of the "terminal device" carrying the "application program" is not limited, and generally refers to any computer device having certain functions of computing, accessing internet, communicating, man-machine interaction, and the like, for example, but not limited to: smart phones, tablet computers, notebook computers, desktop computers, various wearable devices, and the like. In embodiments of the present application, a terminal device typically includes at least one processor and at least one memory. The number of processing units and memories depends on the configuration and type of terminal equipment. The Memory may include volatile, such as Random Access Memory (RAM), non-volatile, such as Read-Only Memory (ROM), flash Memory, etc., or both. The memory typically stores an Operating System (OS), program codes of one or more application programs, and may also store program data and the like. Besides the processor and the memory, the terminal device also includes a network card chip, an IO bus, an audio/video component and other basic configurations. Optionally, depending on the implementation form of the terminal device, the terminal device may also include some peripheral devices, such as a keyboard, a mouse, an input pen, a printer, and the like. These peripheral devices are well known in the art and will not be described in detail herein.

In addition, in the embodiment of the present application, the operating system of the terminal device is not limited, and the operating system of the terminal device may be different according to the implementation form of the terminal device. Taking the terminal device as an example of a smart Phone, the operating system may be Android (Android), iOS, Symbian, Windows Phone, BlackBerry OS, or the like. In other words, in the case that the terminal device is a smart Phone, the technical solution provided in the exemplary embodiment of the present application is applicable to smart phones of various systems such as Android, iOS, Symbian, Windows Phone, or BlackBerry OS.

Fig. 1a is a schematic flowchart of a page jump method according to an exemplary embodiment of the present disclosure. As shown in fig. 1a, the method comprises:

11a, responding to the cold start operation of the application program, and displaying a landing page;

13a, displaying an interactive control with prompt information on the landing page, wherein the prompt information prompts a user to trigger the interactive control to jump to a history page displayed before the application program is killed;

15a, responding to the triggering operation of the user on the interactive control, restoring the historical page according to the page data of the historical page stored before the application program is killed, and jumping to the historical page.

In this embodiment, the application is installed on the terminal device of the user, and the application is in a running state and can be used by the user before the cold start operation described in step 11a is performed. During use of an application, a user may access various application pages provided by the application. In the present embodiment, it is assumed that the application page last accessed by the user before exiting the application program is page a, and page a may be any page, as shown in fig. 1 b. Taking the application program as an online shopping application as an example, the page a last visited by the user may be a detail page of a certain commodity, a certain shop page, a placing page or an order detail page.

The mode of the user exiting the application program may be that the application program is manually killed, or the application program is allowed to enter a background operation. In the running process of the terminal equipment, in order to ensure smooth running of the equipment and improve the running speed, the operating system may take measures of killing background processes, and at the moment, application programs running in the background may be killed by the system. In the embodiment of the present application, it is assumed that the application program is killed by the system in the case where the application program enters into the background running. In this embodiment, before the application is killed, page jump behavior occurring in the use process may be monitored, and each time the page jump behavior is monitored, page data of a page (e.g., page a) that is newly jumped to is persisted, so that the page a is restored after the application is cold started again. The page data here refers to the complete data of page a, not just the link to page a. In this embodiment, various page jump behaviors existing in the application program may be monitored, and page data of a page (e.g., page a) that is jumped to last may be persistently stored, and detailed implementation may refer to description in the subsequent embodiments, which is not described herein for a while.

On the basis that the application program is killed by the system, when the user uses the application program again, the application program needs to be restarted by means of cold start. The scenarios in which the user needs to reuse the application program are various, and the manner in which the user triggers the cold start application program may also be different according to different scenarios. For example, the user may trigger (e.g., click or double-click) an icon of an application on the terminal device desktop, thereby triggering operation of the cold-start application. Or, the user may obtain a link of a certain page (for example, a product detail page or an activity page) in the application shared by friends or family, and click the link to trigger the operation of the cold-start application. Alternatively, the user may initiate a call to the application in another application, thereby triggering the operation of cold-starting the application.

The terminal device may perform a cold start process of the application in response to a cold start operation of the application. The cold start process of the application program includes but is not limited to: and establishing a process and an initialization stage for the application program, and displaying a landing page of the application program in the cold starting process. It should be noted that, according to different ways in which the user triggers the application program to perform cold start, the landing pages of the application program in the current cold start process are different. For example, if the process of the application cold start is initiated by the user by triggering (e.g., clicking or double-clicking) the icon of the application, the landing page of the application in the process of the cold start is the home page of the application; if the process of the cold start of the application program is initiated by clicking a link of a certain page (such as a commodity detail page or an activity page) in the application program by the user, the landing page of the application program in the cold start process is the page pointed to by the link.

Wherein, in response to the cold start operation of the application program, the displayed landing page is as shown in fig. 1 c. In fig. 1c, the first page of the application is illustrated as an example. In this embodiment, on the basis of displaying the landing page, an interactive control with prompt information may also be displayed on the landing page, as shown in fig. 1 d. Wherein the prompt is for prompting the user to trigger the interactive control to jump to a history page displayed before the application is killed, such as page a mentioned above. In this embodiment, the implementation type of the "prompt information" is not limited, and may be at least one of text, image, voice, and animation, for example; similarly, the implementation form of the "interactive control" is not limited, and the "interactive control" may be in any control form with a human-computer interaction function, for example, a popup window, a floating layer, a button, an icon, or the like. In fig. 1d, the interactive control is a floating-layer control, and the prompt information is text displayed on the floating-layer control, such as "open the page visited last time", for example, but not limited thereto. In this embodiment, the display position of the "prompt information" is not limited, and may be displayed on the "interactive control" or may be displayed in a region around the "interactive control". In addition, in this embodiment, the operation manner of the user triggering the "interactive control" is also not limited, and may be, for example, clicking, double-clicking, long-pressing, hovering, touch-controlling, voice-controlling, or shaking.

For the user, if the user wants to continue to access the history page displayed before the application program is killed, the triggering operation of the interaction control can be initiated according to the prompt message. Of course, if the user does not wish to continue accessing the history page displayed before the application is killed, the triggering operation of the interaction control need not be initiated. For the terminal device, after the interactive control with the prompt information is displayed on the landing page, it may be monitored whether the interactive control is triggered by the user, and when it is monitored that the interactive control is triggered by the user, a history page may be restored according to the page data of the history page saved before the application is killed, and the history page may be skipped from the landing page to the history page, as shown in fig. 1 e. In fig. 1e, the history page is illustrated as page a. In the whole process from the cold start to the completion of the page jump, a user can quickly jump to a previously visited historical page by only triggering the interaction control, the efficiency is high, the problem that the user experiences badly due to the fact that the application program is killed and interrupted in the page access process can be solved, and the improvement of the user experience is facilitated.

In addition, through statistical analysis, the number of users with page access records before the application program is cold started is large, even over a hundred million; even if only the number of users who have page access within a short time (for example, 5min) before the application program is killed is counted, the number is up to several tens of millions, a large part of the users have page conversion requirements, if the system kills the application program under the condition that the user temporarily quits the application program, most of the users are affected adversely, and the page conversion rate of the users is greatly reduced. In the above embodiment of the application, after the application is cold-started, the user can be helped to jump to the page visited before quickly by displaying the interactive control with the prompt information on the landing page, so that the use experience of the user can be improved, the page conversion rate of the user can be improved, and the subsequent user can be driven to be saved.

It should be noted that, in the above embodiments of the present application, the application scenario may not be limited, for example, no matter the application is actively killed by the user or is killed by the system, the method provided by the above embodiments may be adopted, that is, as long as the application is monitored to be started cold, the interactive control with the prompt information may be displayed on the landing page, so as to help the user quickly jump to the page visited before, improve the user experience and the page conversion rate of the user, and drive the subsequent user to leave up. Of course, whether the method provided by the above embodiment is adopted or not can be flexibly selected according to the application scenario. In some embodiments below, an exemplary process for flexibly selecting the method provided by the above embodiments according to an application scenario is described:

in some optional embodiments of the present application, considering that if the application is actively killed by the user, which largely indicates that the user wants to close the application, after the application is cold-started again, the need for the user to jump to a previously visited history page is not strong; conversely, if the user does not actively kill the application when exiting the application, it is largely indicated that the user does not want to actually relate to the application, but wants the application to temporarily enter background running, in which case, if the application is killed by the system, the need for the user to want to jump to a previously visited history page after the application is cold started again is relatively strong. In view of this, in order to reduce the inconvenience for the user to operate due to displaying the interactive control with the prompt message, in some optional embodiments of the present application, as shown in fig. 1f, before step 13a, the method further includes:

12a1, determining whether the application program is killed by the system before the cold start operation; if it is killed by the system, step 13a may be performed; otherwise, ending the page jump operation.

Optionally, the operating system in the terminal device may record the way in which the application program is killed, for example, the user actively kills or the system kills, and open an API interface to the application program; the application program can acquire the killed mode from the operating system through the API; whether the system is killed or not can be judged according to the acquired killed mode.

In the embodiment shown in fig. 1f, only when the application program is killed by the system, the interaction control with the prompt message is displayed on the landing page to remind the user to trigger the interaction control to jump to the history page displayed before the application program is killed, and the user can quickly jump to the history page displayed before the application program is killed through the interaction control and perform corresponding interaction operation on the history page. On the contrary, if the application program is actively killed by the user, the interaction control with the prompt information cannot be displayed on the landing page after the landing page is displayed, the user cannot jump to the history page displayed before the application program is killed through the interaction control, and the user can directly interact with the landing page. Through the judgment operation, the interactive control with the prompt information can be displayed under the necessary condition, so that the user can be helped to quickly jump to the historical page displayed before the application program is killed, and the user experience and the page conversion rate are improved; under the condition of no need, the interactive control with the prompt message is not displayed, so that the interference brought to the user by displaying the interactive control with the prompt message is reduced, and the user experience is improved.

In some optional embodiments of the present application, considering that the application may be cold-started for the first time, in this case, the application may not be killed before the cold-start, and there is naturally no history page displayed before being killed, i.e., there is no need to jump to the history page displayed before. In view of this, as shown in fig. 1f, before step 13a, the method further comprises:

12a2, judging whether page data of a history page displayed before the application program is killed can be read from the local designated storage space; if it can be read, it indicates that there is a need to jump to the history page displayed before, step 13a may be executed; otherwise, ending the page jump operation.

The local designated storage space is used for storing page data of a page which is newly jumped to when page jump behavior occurs in the application program every time, the page data stored in the storage space can be changed due to page jump, and finally the page data of a page which is displayed last before the application program is killed is stored.

In the embodiment shown in fig. 1f, by determining whether page data of a history page displayed before the application is killed can be read from a local specified storage space, an interactive control with prompt information can be displayed under the condition that a page jump requirement exists, so that a user is helped to jump to the history page displayed before the application is killed quickly, and the user experience and the page conversion rate are improved; under the condition that the page jump requirement is not met, the interactive control with the prompt information is not displayed, the interference brought to the user by displaying the interactive control with the prompt information is reduced, and the user experience is improved.

In some optional embodiments of the present application, it is considered that the application may have different landing pages in different cold-start scenarios, for example, in the case of cold-start of the application through an external link, the landing page may be a specific content page in the application, for example, a certain item detail page. In this case, the user would prefer to stay on the landing page rather than jumping to a history page displayed before the application is killed. In view of this, as shown in fig. 1f, before step 13a, the method further comprises:

12a3, judging whether the landing page belongs to a first white list, wherein page information capable of triggering page recovery operation is stored in the first white list; if the judgment result is yes, namely the landing page belongs to the first white list, the page recovery operation needs to be triggered, and the step 13a can be executed; if the judgment result is negative, which indicates that the user does not want to jump to the history page displayed before the application program is killed to a great extent, the page jump operation can be ended.

In this embodiment, a landing page that can trigger a page restore operation is defined by setting a white list, and information of the landing page that can trigger the page restore operation is stored in the white list. For example, a landing page that may trigger a page restore operation may be the top page, among others. Besides the home page, other application pages which can trigger the page recovery operation when the home page appears can be flexibly set according to application requirements, for example, a customer service page, a page for getting a coupon and an express delivery inquiry page can be set as the home page which can trigger the page recovery operation when the home page appears, and then the information of the home page and the information of the customer service page, the page for getting the coupon and the express delivery inquiry page can be added into a white list. For ease of description and distinction, the whitelist used herein to store information for landing pages that may trigger a page restore operation is referred to as the first whitelist. The page information stored in the first white list may uniquely represent a specific application page, and may be represented by, but is not limited to, the name of the container in which the page is located and a link of the page. In the Android system, the name of the container may be represented by an activity name (activityName), and the link of the page may be represented by a parameter filter item (paramcontainers).

In the embodiment shown in fig. 1f, by determining whether the landing page belongs to the landing page in the first white list, an interactive control with prompt information can be displayed under the condition that page skipping is required, so that a user is helped to quickly skip to a history page displayed before an application program is killed, and user experience and page conversion rate are improved; under the condition that the page jump is not needed, the interactive control with the prompt information is not displayed, the interference brought to the user by displaying the interactive control with the prompt information is reduced, and the user experience is improved.

In some optional embodiments of the present application, a second white list may be further provided, and the second white list is used for storing page information that can be recovered. Similarly, the page information in the second white list may uniquely represent a specific application page, and the page information may be represented by, but is not limited to, the name of the container in which the page is located and the link of the page. Through the second white list, the displayed historical page before the application program is killed can be selectively recovered and jumped, and the flexibility of page jump is improved. The page that can be restored in the second white list can be flexibly set according to the application requirement, and the setting is not limited to this. For example, taking an online shopping application as an example, in order to improve the transaction conversion rate of the user, an activity page, a tab (tab) page, a shopping cart page, a shop page, a commodity detail page, an order placement page, an order detail page, a payment page, a search result page, and the like may be added to the second whitelist as pages that can be restored. Accordingly, the history page in the present embodiment may be an activity page, a tab (tab) page, a shopping cart page, a shop page, an item detail page, an order placement page, an order detail page, a payment page, or a search result page, but is not limited thereto. Based on this, as shown in fig. 1f, before step 13a, the method further includes:

12a4, judging whether the history page displayed before the application program is killed belongs to a second white list, wherein the second white list stores recoverable page information; if yes, the history page is described as belonging to the page which can be recovered, and step 13a can be executed; if not, the historical page is not the page which can be recovered, and the page jump operation can be ended.

In the embodiment shown in fig. 1f, by determining whether the historical page belongs to a page that can be restored in the second white list, an interactive control with prompt information can be displayed when page jump is necessary, so as to help a user quickly jump to the historical page displayed before the application is killed, and improve user experience and page conversion rate; under the condition that page skipping is not needed, the interactive control with the prompt information is not displayed, so that the interference brought to the user by displaying the interactive control with the prompt information is reduced, and the user experience is improved.

It is explained here that, in order to meet more page jump requirements and also to improve the flexibility of the scheme, in addition to the above-mentioned several judgment operations, as shown in fig. 1f, before step 13a, the following judgment operations are also included:

12a5, judging whether the occurrence frequency of the interactive control is less than the upper limit value of the frequency in the specified period;

12a6, judging whether the version number of the application program belongs to the specified program version number;

12a7, judging whether the version number of the operating system of the terminal equipment where the application program is located belongs to the specified system version number;

12a8, judging whether the terminal equipment where the application program is located belongs to the release range of the terminal equipment in the AB test;

12a9, judging whether the time length of the killed application program is still in the set recovery time range.

With respect to step 12a5, a specified period may be set, and an upper limit value of the number of times the interactive control with prompt information is allowed to appear within the specified period may be set. The present embodiment does not limit the time length of the specified period, nor the upper limit of the number of times the interactive control is allowed to appear in the specified period. For example, it may be set that only 1 interactive control is allowed to appear within 1 minute, and if the application performs 2 cold starts within 1 minute, only the interactive control with the prompt information appears on the landing page after the 1 st cold start, and the interactive control with the prompt information does not appear on the landing page after the 2 nd cold start. For another example, only 10 interactive controls are allowed to appear within 1 day, and if the number of cold starts of the application program within 1 day exceeds 10, the interactive controls with the prompt information do not appear on the landing page of the cold start after 10 times. Through the mode, on the one hand, the interference caused to the user can be properly reduced, the interestingness of the application program is increased, the user experience function is attracted, and the viscosity of the user is increased.

Regarding the steps 12a6 and 12a7, the gradual popularization of the function can be flexibly controlled through the judgment operation of the program version number or the system version number, the use experience of the user can be collected, the function can be further reasonably popularized, and the problems that the whole user experience is reduced and the user runs off due to the fact that the function is popularized in a large area at one time under the condition that the user experience is poor can be avoided.

With respect to step 12a8, without determining the user experience of the page jump function, the AB test mode may be adopted to gradually promote, for example, the release amount of the terminal device may be gradually increased from 10% to 20%, 40%, 50%, and up to 100%. In each AB test stage, a part of terminal equipment is required to be selected according to the release range of the stage, and for the terminal equipment beyond the release range, the function is not started temporarily, namely if the terminal equipment where the application program is located belongs to the release range of the terminal equipment in the AB test, an interactive control with prompt information can be displayed on a landing page after the landing page is displayed; on the contrary, if the terminal device where the application program is located does not belong to the release range of the terminal device in the AB test, the interactive control with the prompt information cannot be displayed on the landing page after the landing page is displayed. For example, assuming that the number of the corresponding terminal devices is 1000 in the 10% zoom range, when the application on the 1001 st terminal device performs cold start, after the landing page is displayed, the interactive control with the prompt message is not displayed on the landing page.

With respect to step 12a9, page jumps may be rationalized by setting a recovery time range. The recovery time range can be flexibly set according to application requirements, and can be set within 10 minutes, 1 hour, 5 hours, 24 hours, 2 days and even longer, for example. If the application program is killed for a long time and exceeds the set recovery time range, the significance is not large from the view of the user intention or the view of the storage resource utilization rate, so that the page data of the historical page stored in the local appointed storage space can be deleted in time, the storage resource is released, and after the application program is cold started, an interactive control with prompt information does not need to be displayed on the landing page, and the interference to the user is reduced.

It should be noted that the above steps 12a1-12a9 may be used alternatively or in combination in any combination, that is, at least one of the steps 12a1-12a9 may be included before the step 13 a. And (3) when the judgment result of at least one step selected for use is yes, executing the step (13 a), otherwise, ending the page jump operation, namely, stopping on the displayed landing page for the user to interact with the landing page.

In the present embodiment, the execution order of the plurality of steps to be selected and used is not limited, and the plurality of steps may be executed sequentially or in parallel, regardless of which steps are selected and used. In FIG. 1f, steps 12a1-12a9 are sequentially executed as an example, but not limited thereto.

Whether the judgment operation is carried out or not, when the interactive control with the prompt information is determined to be displayed on the landing page, the prompt information bound with the interactive control can be obtained, and the prompt information and the interactive control are displayed on the landing page. In an alternative embodiment, the interactive control is a floating layer control, and for convenience of description and distinction, the floating layer control serving as the interactive control is denoted as a floating layer control B. The floating layer control needed to be displayed on the landing page may only be the floating layer control B, and other floating layer controls may also need to be displayed. If the landing page only needs to display the floating layer control B, the floating layer control B can be directly displayed on the landing page; if other floating layer controls are needed on the landing page, the priority between the floating layer control B and the other floating layer controls can be set in the application development process, and the floating layer control with high priority can be positioned on the floating layer control with low priority. Based on the above, after the landing page is displayed, the priority between the floating layer control B and other floating layer controls can be obtained, and the floating layer control B and other floating layer controls are sequentially displayed on the landing page according to the priority between the floating layer control B and other floating layer controls.

In an optional embodiment, the priority of the floating layer control B may be set to be the highest, and the floating layer control B is located at the top of all the floating layer controls; or the priority of the floating layer control B can be set to be the lowest, and then the floating layer control B is located at the lowest of all the floating layer controls, so that the influence of the floating layer control B on other floating layer controls can be reduced.

It should be noted that, in addition to being implemented as the floating layer control B, the interactive control may also be implemented as other control forms such as an icon or a popup window. Regardless of the control form, the interactive control is preferably implemented independently of the landing page, which provides greater flexibility. Of course, the interactive controls may also be implemented as controls in a landing page. Under the condition that the interactive control is realized independently of the landing page, in order to reduce the influence of the interactive control on the landing page or other controls or interface elements on the landing page, the user is allowed to close the interactive control, or the interactive control is automatically closed.

Optionally, the interactive control supports a closing operation, for example, the interactive control may have a closing button, and a user may click the closing button to initiate an operation of closing the interactive control; or, the user clicks other page areas except the interactive control to initiate the operation of closing the interactive control; and so on. The application program can respond to the triggering operation of closing the interactive control initiated by the user, and control the interactive control to disappear on the landing page, namely close the interactive control.

Optionally, a display duration threshold may also be set for the interactive control, where the display duration threshold refers to the longest displayable time of the interactive control on the landing page. Based on the above, after the interactive control is displayed on the landing page, the display duration of the interactive control can be recorded, and when the recorded display duration reaches the set display duration threshold, the interactive control is automatically controlled to disappear on the landing page. The recording of the display duration of the interactive control may be performed by a timer, for example, the timer may be used to count down a set display duration threshold, and when the count down is completed, the interactive control is controlled to disappear on the landing page, that is, the interactive control is closed.

In addition to the above manner, after the user triggers the interactive control, the interactive control can also disappear from the landing page; or, when the user returns to the landing page again after jumping from the landing page to another page, the interactive control may also disappear from the landing page.

In some embodiments of the present application, the application includes only native pages, and the history page displayed before the application is killed is a native page; accordingly, the landing page is also a native page. In other embodiments, the application includes not only native pages, but also non-native pages, such as web pages or weex pages; the history page displayed before the application is killed may be a native page or a non-native page, such as a web page or a weex page; similarly, the landing page may be a native page or a non-native page, which is not limited to this.

Implementations of the above-described embodiments of the present application rely on page data of a history page displayed before an application is killed being persisted before the application is killed. The process of persisting page data accessed by a user until the application is killed will be described in detail below.

And the storage space is pre-designated locally for storing the page data stored persistently. Therefore, before the application program is killed, the page jump behavior in the application program can be monitored, when the page jump behavior is monitored, the page which is last visited by the user is changed, so that the page data which is last visited by the user can be recovered to be convenient for later opportunity, and when the page jump behavior is monitored, the page data of the page which is latest jumped to can be durably stored. It should be noted that the page data of the page that is jumped to each time can be stored in the local specified storage space, so that any page that the user has accessed can be restored as needed or at an opportunity; or, an overlay storage mode can be adopted, and the page data saved before is overlaid by the latest page data each time, so that only the page data last accessed by the user can be saved, and the storage space can be saved.

In some embodiments of the present application, it is considered that a first page of an application is usually a composite page, and therefore, when a page jump behavior in the application is monitored, not only a jump behavior between independent pages existing in the application but also a jump behavior between sub-pages in the composite page may be monitored. No matter which kind of page jump behavior is monitored, information of various pages existing in the application program needs to be known in advance, for example, which independent pages exist, which compound pages exist, which sub-pages are included in the compound pages, identifications of the independent pages, the compound pages, and each sub-page, and the like. Based on the method, the jump behavior among the independent pages can be monitored based on the information of the independent pages existing in the application program, and the jump behavior among the sub-pages in the composite page can be monitored based on the composite page existing in the application program and the information of the sub-pages included in the composite page.

Further, under the condition that the page jump behavior is monitored, the page data of the page which is jumped to last can be stored persistently. In the embodiment, in two aspects of the process of persisting page data, on one hand, a first serialization function capable of converting a file into a link is called, and fixed main content in the page data of the latest jump-to page is serialized to obtain a link pointing to the latest jump-to page; on the other hand, a second serialization function supporting cross-process data transmission is called, and dynamic variable parameter content in page data of a newly jumped page is serialized to obtain serialized parameter content; and then, respectively storing the link pointing to the page which is jumped to the latest and the serialized parameter content into a local specified storage space, and finishing the persistent storage of the page data. The local designated storage space is a non-volatile storage space, and may be, for example, a hard disk, a magnetic disk, a flash memory, or the like.

It should be noted that the "application" in the embodiment of the present application has a function of monitoring page jump behavior and persistently storing the latest jump page data, and also has a function of displaying an interaction control with prompt information on a landing page after cold start, and a function of restoring a history page and jumping to the history page in response to a user's trigger operation on the interaction control. However, the embodiments of the present application are not limited to the technical means for implementing the above functions in the application program. In an alternative embodiment, as shown in fig. 1g, a floating layer manager may be added to the application program, and the floating layer manager cooperates with its corresponding configuration end to implement the aforementioned functions. In this embodiment, the interactive control is specifically implemented as a floating layer control.

Taking the Android system as an example, in an application program developed by Android, human-computer interaction (or screen interaction) is mainly provided by activity (activity), the activity is an application component in the Android system, each activity obtains a window for drawing an application page of the activity, and the window can be filled with a display screen of the terminal device or can be smaller than the display screen and float on other windows. An application is usually composed of a plurality of activities loosely linked to each other, and an activity may correspond to an independent page or a compound page. Of course, activities may jump to each other to perform different operations. When a new activity is started, the system pushes the new activity to the stack and obtains the operation focus of the user, the old activity stops, but the system keeps the old activity in the stack; when the user completes the current activity and presses the back button, the system pops it up from the stack for destruction and then reverts to the old activity.

It follows that the jump between application pages, as seen from the user perspective, is actually a jump between activities. Based on this, the process of monitoring the page jump behavior is actually the process of monitoring the activity state. Specifically, in an application program developed by Android, a floating layer manager is added, the floating layer manager monitors activity which is obtained from the application program for the first time and can interact with a user (onResume), and an application page corresponding to the activity belongs to a page currently visited by the user. In addition, the floating layer manager can also monitor the switching between Fragment (Fragment) level pages (or called sub-pages). Before this, the floating layer manager needs to access the activity including the Fragment level page, that is, needs to obtain the information of each sub-page included in the activity, so that each sub-page can be identified. For a compound page (such as a tab-type page) which is not accessed to the floating layer manager in advance, the floating layer manager only records the first access information of the whole compound page.

An Intent mechanism is provided in an Android system to assist interaction and communication between applications, Intent can be used not only between applications but also between activities within the applications, jumping between activities needs to be completed through Intent, and Intent can record information related to the activities, such as actions and page data corresponding to the activities. The process of persisting the latest jump-to page data may be understood as a process of persisting Intent. In this embodiment, the Intent. touri may be called to complete persistence of the main content in the Intent, and a parcel is called to perform parcel persistence on the bundle content in the Intent, and then the two persistent contents are respectively stored in a locally specified storage space, such as a certain file. The bundle is a class in Android development and is used for transmitting data between activities; the bundle content is mainly dynamically variable data in the activity corresponding page. Taking the order detail page as an example, the commodity information (such as commodity name, price and quantity) in the order belongs to dynamically variable data, and the part is called as parameter content in the page; the links and basic frame data of the order detail page belong to fixed and unchangeable data, and the part is called main content in the page.

Further, in order to pop up a floating layer control with prompt information on a landing page after the application program is cold started, a new floating layer type is expanded on the basis of the original floating layer type and is marked as a native type, and the corresponding function of the new floating layer type is designated as "open", namely, the previous historical page is reopened; based on this, after the application program is cold started, the floating layer manager can create a floating layer control with a type of native and a function of reopen, and display the floating layer control on the landing page after the prompt information is rendered, so as to remind a user that the user can jump to a history page displayed before the application program is killed by triggering the floating layer control. Optionally, the prompt information may be rendered in a simplified manner, and the prompt information is directly organized in the parameters of the floating layer control, for example, the prompt information of the type of the document or the picture may be directly organized in the parameters of the floating layer control, and the rendering is completed together with the floating layer control. It is noted that the naming of the types and functions of the float control is merely exemplary and not limited to "native" and "open".

Further, as shown in fig. 1g, after the new type of floating layer control is created, in order to manage the use of the new type of floating layer control, the floating layer manager may add a switch function to the new type of floating layer control, and the configuration end may open or close the use of the new type of floating layer control through configuration operation, to indirectly control whether the function of displaying the interactive control on the landing page is opened, thereby implementing control on whether the page jump scheme provided in the embodiment of the present application is opened. Optionally, the configuration end may send an opening instruction to enable the new type of floating layer control, that is, to instruct to open the function of displaying the interactive control; the floating layer manager can receive a starting instruction sent by the configuration end and start the function of displaying the interactive control.

Besides controlling whether the new type floating control is started, the configuration end can also control whether the floating layer manager starts a function of persistently storing newly jumped page data; if the configuration end closes the function, the floating layer manager stops persistence storage of the latest jump-to page data, and meanwhile, the locally stored page data which has been persisted is cleared, so that a storage error is avoided when the configuration end opens the function again.

Further, under the condition that the configuration end starts a new type floating control and starts the function of the floating layer manager for persistently storing the latest jumped page data, the configuration end can also issue at least one of a first white list, a second white list, a frequency upper limit value in a specified period, a specified program version number, a specified system version number, a release range and a recovery time range of the terminal equipment in the AB test to the floating layer manager. In addition, according to application requirements, the configuration end can flexibly update the first white list, the second white list, the upper limit value of times in a specified period, a specified program version number, a specified system version number, a release range and/or a recovery time range of the terminal device in the AB test. For a detailed description of these information items, reference may be made to the foregoing embodiments, which are not described in detail herein. It should be noted that the landing page that can trigger the page recovery operation and is stored in the first white list and the page information that can be recovered and is stored in the second white list may be configured by the configuration end, or may be flexibly configured by the user according to the needs of the user. For example, in an application program, an operation entry for configuring a first white list and a second white list may be provided for a user, and the user configures landing pages stored in the first white list, which may trigger a page restore operation, and page information stored in the second white list, which may be restored through the operation entry. The user can automatically determine which pages need to be restored by setting the page information which can be restored, and the user can give the user the option and control right, so that the user can restore the pages as required, the personalized requirements of the user are better met, and the use experience of the user is favorably improved.

Based on the above, the floating layer manager may respond to the cold start operation of the application program to which the floating layer manager belongs, display a landing page, and execute at least one judgment operation described in the above steps 12a1-12a9 according to the at least one information item issued by the configuration end; under the condition that the judgment result of the at least one judgment operation is yes, the new type of floating layer control is created, prompt information required by the floating layer control is rendered, and the floating layer control can be displayed on a landing page according to the priority of the floating layer control; if the user wants to jump to a history page displayed before the application program is killed, the user can click the floating layer control under the prompt of the prompt information; the floating layer manager responds to the clicking operation of a user on the floating layer control, can acquire the link pointing to the historical page and the serialized parameter content stored in the local designated storage space, performs deserialization on the two parts of content to obtain the main content and the parameter content in the historical page, integrates and restores the historical page by using the main content and the parameter content, and skips from the landing page to the historical page to complete page skipping. The user can then continue to interact with previously accessed history pages, for example, to continue to make orders, or to make payments.

Fig. 2a is a schematic flowchart of another page jump method according to an exemplary embodiment of the present application.

21a, responding to the cold start operation of the application program, displaying a landing page, and identifying whether the application program is killed by the system before the cold start operation;

and 22a, if the application program is killed by the system before the cold start operation, restoring the historical page according to the saved page data of the historical page displayed before the application program is killed, and jumping to the historical page from the landing page.

In this embodiment, the terminal device may execute a cold start procedure of the application program in response to a cold start operation of the application program. The cold start process of the application program includes but is not limited to: and establishing a process and an initialization stage for the application program, and displaying a landing page of the application program in the cold starting process.

Wherein, in response to the cold start operation of the application program, the displayed landing page is as shown in fig. 2 b. In fig. 2b, the first page of the application is illustrated as an example. In this embodiment, during the cold start of the application program, it may be further identified whether the application program is killed by the system before the cold start operation; if the application program is killed by the system before the cold start operation, the history page is restored according to the page data of the history page saved before the application program is killed, and the history page is jumped from the landing page to the history page, as shown in fig. 2 c. In FIG. 2c, the history page is illustrated as page A in FIG. 1 b. For the way to identify whether the application program is killed by the system before the cold start operation, reference may be made to the foregoing embodiments, and details are not described herein.

In the embodiment, considering that if the application is actively killed by the user, which largely indicates that the user wants to close the application, after the application is cold started again, the requirement that the user wants to jump to a history page visited before is not strong; conversely, if the user does not actively kill the application when exiting the application, it is largely indicated that the user does not want to actually relate to the application, but wants the application to temporarily enter background running, in which case, if the application is killed by the system, the need for the user to want to jump to a previously visited history page after the application is cold started again is relatively strong. Therefore, under the condition that the application program is identified to be killed by the system, the user can directly jump to the history page displayed before the application program is killed, the user can be helped to quickly jump to the history page displayed before the application program is killed without being triggered by an interactive control, and the user experience and the page conversion rate are improved.

It should be noted that, in the embodiment shown in fig. 2a, before jumping from the landing page to the history page, the determination operation described in at least one of steps 12a2, 12a3, 12a4, 12a6, 12a7, 12a8, and 12a9 may also be performed, and in a case that the determination result of at least one determination operation is yes, the operation of jumping from the landing page to the history page is performed. For a detailed description of the determination operations described in these steps, reference may be made to the foregoing embodiments, which are not described herein again.

It should be noted that the interface styles and contents shown in fig. 1b to 1e and fig. 2b and 2c in this embodiment are only examples, and do not constitute a limitation on the pages provided by the application program in this embodiment.

Fig. 3 is a flowchart illustrating a page jump method according to another exemplary embodiment of the present application.

31. In response to a cold start operation of the application, identifying whether the application was killed by the system prior to the cold start operation;

32. if the application program is killed by the system before the cold start operation, restoring the history page according to the saved page data of the history page displayed before the application program is killed, and displaying the history page.

In this embodiment, the terminal device may execute a cold start procedure of the application program in response to a cold start operation of the application program. The cold start process of the application program includes but is not limited to: a process is created for the application, an initialization phase, and an identification is made as to whether the application was killed by the system prior to a cold start operation. And if the application program is killed by the system before the cold start operation, restoring the historical page according to the page data of the historical page saved before the application program is killed, skipping over the landing page, and directly displaying the historical page.

Compared with the embodiment shown in fig. 2a, the embodiment skips the landing page and directly displays the history page, which can help the user to jump to the history page displayed before the application program is killed more quickly, thereby improving the user experience and the page conversion rate.

It should be noted that, in the embodiment shown in fig. 3, before jumping from the landing page to the history page, the determination operation described in at least one of steps 12a2, 12a4, 12a6, 12a7, 12a8, and 12a9 may be further performed, and when the determination result of at least one determination operation is yes, the operation of jumping from the landing page to the history page is performed. For a detailed description of the determination operations described in these steps, reference may be made to the foregoing embodiments, which are not described herein again.

Further, in this embodiment of the present application, after the application is cold started, the history page that can be skipped to may be any page that the user has visited before the application is killed, for example, the history page that can be skipped to after the application is cold started may be set as the page that the user has last visited before the application is killed by default, or the history page that can be skipped to after the application is cold started may be set as the specified page that the user has visited before the application is killed by default, and optionally, the specified page may be a page that is meaningful for promoting page conversion rate, such as a next order page or a payment page. Besides the default setting, the user can flexibly select the historical page which can be jumped to after the application program is cold started from the pages which are accessed before the application program is killed according to the application requirements.

For example, taking the embodiment shown in fig. 1a as an example, after the user performs a trigger operation on the interactive control on the landing page, a list of history pages that the user accessed before the application was killed is displayed, so that the user can select a history page that the user wishes to recover to from the list; and responding to the selection operation of the user in the history page list, acquiring the page data of the selected history page stored before the application program is killed, recovering the selected history page by using the page data of the selected history page, and jumping to the selected history page.

For another example, taking the embodiment shown in fig. 2a or fig. 3 as an example, if it is determined that the application program is killed by the system before the cold start operation, a history page list that the user visited before the application program was killed may be displayed for the user to select a history page that the user wishes to recover to; and responding to the selection operation of the user in the history page list, acquiring the page data of the selected history page stored before the application program is killed, recovering the selected history page by using the page data of the selected history page, and jumping to the selected history page.

In the above embodiment, the history page list stores therein information of history pages that the user accessed within a certain period of time before the application program was killed. In the embodiment of the present application, the time length of the certain period is not limited, and may be, for example, the latest 1 hour, 8 hours, one day, three days, one week, and the like, and may be flexibly set. The history page list accessed before the application program is killed is provided for the user, the user can automatically determine which pages need to be restored, and the selection and control right is given to the user, so that the user can restore the pages as required, the personalized requirements of the user are met better, and the use experience of the user is improved.

It should be noted that the execution subjects of the steps of the methods provided in the above embodiments may be the same device, or different devices may be used as the execution subjects of the methods. For example, the execution subjects of steps 11a to 15a may be device a; for another example, the execution subject of steps 11a-13a may be device a, and the execution subject of step 15a may be device B; and so on.

In addition, in some of the flows described in the above embodiments and the drawings, a plurality of operations are included in a specific order, but it should be clearly understood that the operations may be executed out of the order presented herein or in parallel, and the order of the operations, such as 11a, 13a, etc., is merely used to distinguish various operations, and the order itself does not represent any execution order. Additionally, the flows may include more or fewer operations, and the operations may be performed sequentially or in parallel. It should be noted that, the descriptions of "first", "second", etc. in this document are used for distinguishing different messages, devices, modules, etc., and do not represent a sequential order, nor limit the types of "first" and "second" to be different.

Fig. 4 is a schematic structural diagram of a terminal device according to an exemplary embodiment of the present application. As shown in fig. 4, the terminal device includes: memory 41, processor 42 and display 43.

The terminal device of the present embodiment has an application program installed thereon, and the memory 41 is configured to store a program code of the application program installed on the terminal device and may be configured to store other various data to support operations on the terminal device. Examples of such data include instructions for any application or method operating on the terminal device, contact data, phonebook data, messages, pictures, videos, etc.

A processor 42, coupled to the memory 41, for executing program code of the application program stored in the memory 41 for:

displaying a landing page on the display screen 43 in response to a cold start operation of the application;

displaying an interactive control with prompt information on the landing page, wherein the prompt information prompts a user to trigger the interactive control to jump to a history page displayed before the application program is killed;

responding to the triggering operation of the user on the interaction control, restoring the historical page according to the page data of the historical page stored before the application program is killed, and jumping to the historical page.

In an alternative embodiment, processor 42 is further configured to: before the interactive control with the prompt message is displayed on the landing page, at least one of the following judgment operations is executed:

judging whether the landing page belongs to a first white list or not, wherein page information capable of triggering page recovery operation is stored in the first white list;

judging whether page data of a history page displayed before the application program is killed can be read from a local appointed storage space;

judging whether the historical page belongs to a second white list or not, wherein the second white list stores recoverable page information;

determining whether the application was killed by the system prior to a cold start operation;

judging whether the occurrence frequency of the interactive control is smaller than the upper limit value of the frequency in a specified period or not;

judging whether the version number of the application program belongs to a specified program version number;

judging whether the version number of the operating system of the terminal equipment where the application program is located belongs to a specified system version number or not;

judging whether the terminal equipment where the application program is located belongs to the release range of the terminal equipment in the AB test;

judging whether the killed duration of the application program is within a set recovery time range;

and if the judgment result of the at least one judgment operation is yes, executing the operation of displaying the interactive control with the prompt information on the landing page.

In an optional embodiment, the interactive control is a floating layer control displayed on the landing page.

In an optional embodiment, when the processor 42 displays the interactive control with the prompt message on the landing page, it is specifically configured to: acquiring the priority between the floating layer control and other floating layer controls under the condition that other floating layer controls need to be displayed on the landing page; and sequentially displaying the floating layer control and other floating layer controls on the landing page according to the priority between the floating layer control and other floating layer controls.

Further optionally, the floating layer control has the highest priority; or the floating layer control has the lowest priority.

In an alternative embodiment, processor 42 is further configured to: after the interactive control with the prompt message is displayed on the landing page, responding to a triggering operation initiated by a user for closing the interactive control, and controlling the interactive control to disappear on the landing page; or recording the display duration of the interactive control, and controlling the interactive control to disappear on the landing page when the display duration reaches a set display duration threshold.

In an optional embodiment, the landing page is a home page of the application program.

In an optional embodiment, the type of the history page is a native page of the application program or a non-native page in the application program.

Further optionally, the history page is an activity page, a tab page, a shop page, a goods detail page, an order placement page, an order detail page, or a search result page in the application program.

In an alternative embodiment, processor 42 is further configured to: monitoring page jump behaviors in the application program before the application program is killed; and when the page jump behavior is monitored, persistently storing the page data of the page which is jumped to latest.

Further optionally, when monitoring the page jump behavior in the application, the processor 42 is specifically configured to: the method comprises the steps of monitoring the jump behavior among independent pages based on the information of the independent pages in an application program, and monitoring the jump behavior among sub-pages in a composite page based on the information of the composite page and the sub-pages contained in the composite page.

Further optionally, when the processor 42 persistently stores the page data of the page which is newly jumped to, the processor is specifically configured to: calling a first serialization function which can convert a file into a link, and serializing fixed main content in page data of a latest jump-to page to obtain a link pointing to the latest jump-to page; calling a second serialization function supporting cross-process data transmission, and serializing the dynamically variable parameter content in the page data of the latest jump-to page to obtain serialized parameter content; and respectively storing the link pointing to the page which is jumped to the latest and the serialized parameter content into a local designated storage space.

Further optionally, the processor 42 is further configured to: before the interactive control with the prompt information is displayed on the landing page, starting the function of displaying the interactive control according to a starting instruction sent by a configuration end; and receiving at least one of a first white list, a second white list, a time upper limit value in a specified period, a specified program version number, a specified system version number, a release range and a recovery time range of the terminal equipment in the AB test, which are issued by the configuration end.

In an alternative embodiment, processor 42 is further configured to: after responding to the triggering operation of the user on the interaction control, displaying a history page list accessed by the user before the application program is killed, so that the user can select a history page which the user wants to recover to from the history page list; and responding to the selection operation of the user in the history page list, acquiring the page data of the selected history page stored before the application program is killed, recovering the selected history page by using the page data of the selected history page, and jumping to the selected history page.

Further, as shown in fig. 4, the terminal device further includes: communication components 44, power components 45, audio components 46, and the like. Only some of the components are schematically shown in fig. 4, and it is not meant that the terminal device includes only the components shown in fig. 4.

Accordingly, the present application also provides a computer readable storage medium storing a computer program, and the computer program can implement the steps in the method embodiments shown in fig. 1a and fig. 1f when executed.

The embodiment of the present application further provides a terminal device, where an implementation structure of the terminal device is the same as or similar to the implementation structure of the terminal device shown in fig. 4, and may be implemented by referring to the structure of the terminal device shown in fig. 4. The difference between the terminal device provided in this embodiment and the terminal device in the embodiment shown in fig. 4 mainly lies in: the functions performed by the processor to execute the program code of the application program stored in the memory are different. For the terminal device provided in this embodiment, the processor executes the program code stored in the memory, and the program code is configured to: displaying a landing page on the display screen in response to a cold start operation of an application program, and identifying whether the application program is killed by a system before the cold start operation; and if the application program is killed by the system before the cold start operation, restoring the historical page according to the saved page data of the historical page displayed before the application program is killed, and jumping to the historical page from the landing page.

In an alternative embodiment, the processor is further configured to: in the case that the application program is identified to be killed by the system before the cold start operation, displaying a history page list visited by the user before the application program is killed, so that the user can select a history page which the user wants to recover to; and responding to the selection operation of the user in the history page list, acquiring the page data of the selected history page stored before the application program is killed, recovering the selected history page by using the page data of the selected history page, and jumping to the selected history page.

For other functional operations that can be realized by the processor in this embodiment, reference may be made to the foregoing embodiments, which are not described herein again.

The embodiment of the present application further provides a terminal device, where an implementation structure of the terminal device is the same as or similar to the implementation structure of the terminal device shown in fig. 4, and may be implemented by referring to the structure of the terminal device shown in fig. 4. The difference between the terminal device provided in this embodiment and the terminal device in the embodiment shown in fig. 4 mainly lies in: the functions performed by the processor to execute the program code of the application program stored in the memory are different. For the terminal device provided in this embodiment, the processor executes the program code stored in the memory, and the program code is configured to: in response to a cold start operation of an application, identifying whether the application was killed by a system prior to the cold start operation; and if the application program is killed by the system before the cold start operation, restoring the history page according to the saved page data of the history page displayed before the application program is killed, and displaying the history page.

The memory in the above embodiments may be implemented by any type or combination of volatile or non-volatile memory devices, such as Static Random Access Memory (SRAM), electrically erasable programmable read-only memory (EEPROM), erasable programmable read-only memory (EPROM), programmable read-only memory (PROM), read-only memory (ROM), magnetic memory, flash memory, magnetic or optical disks.

The communication component in the above embodiments is configured to facilitate communication between the device in which the communication component is located and other devices in a wired or wireless manner. The device where the communication component is located can access a wireless network based on a communication standard, such as a WiFi, a 2G, 3G, 4G/LTE, 5G and other mobile communication networks, or a combination thereof. In an exemplary embodiment, the communication component receives a broadcast signal or broadcast related information from an external broadcast management system via a broadcast channel. In one exemplary embodiment, the communication component further includes a Near Field Communication (NFC) module to facilitate short-range communications. For example, the NFC module may be implemented based on Radio Frequency Identification (RFID) technology, infrared data association (IrDA) technology, Ultra Wideband (UWB) technology, Bluetooth (BT) technology, and other technologies.

The display screen in the above embodiments includes a screen, which may include a Liquid Crystal Display (LCD) and a Touch Panel (TP). If the screen includes a touch panel, the screen may be implemented as a touch screen to receive an input signal from a user. The touch panel includes one or more touch sensors to sense touch, slide, and gestures on the touch panel. The touch sensor may not only sense the boundary of a touch or slide action, but also detect the duration and pressure associated with the touch or slide operation.

The power supply assembly of the above embodiments provides power to various components of the device in which the power supply assembly is located. The power components may include a power management system, one or more power supplies, and other components associated with generating, managing, and distributing power for the device in which the power component is located.

The audio component in the above embodiments may be configured to output and/or input an audio signal. For example, the audio component includes a Microphone (MIC) configured to receive an external audio signal when the device in which the audio component is located is in an operational mode, such as a call mode, a recording mode, and a voice recognition mode. The received audio signal may further be stored in a memory or transmitted via a communication component. In some embodiments, the audio assembly further comprises a speaker for outputting audio signals.

As will be appreciated by one skilled in the art, embodiments of the present application may be provided as a method, system, or computer program product. Accordingly, the present application may take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects. Furthermore, the present application may take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, and the like) having computer-usable program code embodied therein.

The present application is described with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of the application. It will be understood that each flow and/or block of the flow diagrams and/or block diagrams, and combinations of flows and/or blocks in the flow diagrams and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.

These computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture including instruction means which implement the function specified in the flowchart flow or flows and/or block diagram block or blocks.

These computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.

In a typical configuration, a computing device includes one or more processors (CPUs), input/output interfaces, network interfaces, and memory.

The memory may include forms of volatile memory in a computer readable medium, Random Access Memory (RAM) and/or non-volatile memory, such as Read Only Memory (ROM) or flash memory (flash RAM). Memory is an example of a computer-readable medium.

Computer-readable media, including both non-transitory and non-transitory, removable and non-removable media, may implement information storage by any method or technology. The information may be computer readable instructions, data structures, modules of a program, or other data. Examples of computer storage media include, but are not limited to, phase change memory (PRAM), Static Random Access Memory (SRAM), Dynamic Random Access Memory (DRAM), other types of Random Access Memory (RAM), Read Only Memory (ROM), Electrically Erasable Programmable Read Only Memory (EEPROM), flash memory or other memory technology, compact disc read only memory (CD-ROM), Digital Versatile Discs (DVD) or other optical storage, magnetic cassettes, magnetic tape magnetic disk storage or other magnetic storage devices, or any other non-transmission medium that can be used to store information that can be accessed by a computing device. As defined herein, a computer readable medium does not include a transitory computer readable medium such as a modulated data signal and a carrier wave.

It should also be noted that the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising an … …" does not exclude the presence of other like elements in a process, method, article, or apparatus that comprises the element.

The above description is only an example of the present application and is not intended to limit the present application. Various modifications and changes may occur to those skilled in the art. Any modification, equivalent replacement, improvement, etc. made within the spirit and principle of the present application should be included in the scope of the claims of the present application.

Claims

1. A page jump method is characterized by comprising the following steps:

responding to the cold start operation of the application program, and displaying a landing page;

2. The method of claim 1, further comprising at least one of the following determination operations before displaying the interactive control with prompt information on the landing page:

3. The method of claim 1, wherein the interactive control is a floating-layer control displayed on the landing page.

4. The method of claim 3, wherein displaying the interactive control with prompt information on the landing page comprises:

acquiring the priority between the floating layer control and other floating layer controls under the condition that other floating layer controls need to be displayed on the landing page;

and sequentially displaying the floating layer control and other floating layer controls on the landing page according to the priority between the floating layer control and other floating layer controls.

5. The method of claim 4, wherein the floating layer control has a highest priority; or the floating layer control has the lowest priority.

6. The method of claim 1, wherein after displaying the interactive control with prompt information on the landing page, further comprising:

responding to a triggering operation of closing the interactive control initiated by a user, and controlling the interactive control to disappear on the landing page;

or

Recording the display duration of the interactive control, and controlling the interactive control to disappear on the landing page when the display duration reaches a set display duration threshold.

7. The method of claim 1, wherein the landing page is a home page of the application.

8. The method of claim 1, wherein the type of the history page is a native page of the application or a non-native page in the application.

9. The method of claim 8, wherein the history page is an activity page, a tab page, a store page, a product detail page, an order placement page, an order detail page, or a search results page in the application.

10. The method of any of claims 1-9, further comprising, before the application is killed:

monitoring page jump behaviors in the application program; and

and when the page jump behavior is monitored, persistently storing the page data of the page which is jumped to latest.

11. The method of claim 10, wherein intercepting page jump behavior in the application comprises:

based on the information of each independent page existing in the application program, monitoring the jump behavior between the independent pages, and

and monitoring the jump behavior among the sub-pages in the composite page based on the composite page existing in the application program and the information of the sub-pages contained in the composite page.

12. The method of claim 11, wherein persisting page data for a last skipped page comprises:

calling a first serialization function which can convert a file into a link, and serializing fixed main content in page data of a latest jump-to page to obtain a link pointing to the latest jump-to page;

calling a second serialization function supporting cross-process data transmission, and serializing the dynamically variable parameter content in the page data of the latest jump-to page to obtain serialized parameter content;

and respectively storing the link pointing to the page which is jumped to the latest and the serialized parameter content into a local designated storage space.

13. The method of claim 2, wherein before displaying the interactive control with prompt information on the landing page, further comprising:

starting a function of displaying the interactive control according to a starting instruction sent by a configuration end; and

and receiving at least one of a first white list, a second white list, a time upper limit value in a specified period, a specified program version number, a specified system version number, a release range of the terminal equipment in the AB test and a recovery time range which are issued by a configuration end.

14. A page jump method is characterized by comprising the following steps:

responding to the cold start operation of the application program, displaying a landing page, and identifying whether the application program is killed by a system before the cold start operation;

and if the application program is killed by the system before the cold start operation, restoring the historical page according to the saved page data of the historical page displayed before the application program is killed, and jumping to the historical page from the landing page.

15. A page jump method is characterized by comprising the following steps:

in response to a cold start operation of an application, identifying whether the application was killed by a system prior to the cold start operation;

and if the application program is killed by the system before the cold start operation, restoring the history page according to the saved page data of the history page displayed before the application program is killed, and displaying the history page.

16. A terminal device, comprising: a memory, a processor and a display screen;

the memory is used for storing the program codes of the application programs installed on the terminal equipment;

the processor, coupled with the memory, to execute the program code to:

responding to the cold start operation of an application program, and displaying a landing page on the display screen;

17. A terminal device, comprising: a memory, a processor and a display screen;

the processor, coupled with the memory, to execute the program code to:

displaying a landing page on the display screen in response to a cold start operation of an application program, and identifying whether the application program is killed by a system before the cold start operation;

18. A terminal device, comprising: a memory and a processor;

the processor, coupled with the memory, to execute the program code to:

19. A computer-readable storage medium having a computer program stored thereon, which, when executed by a processor, causes the processor to carry out the steps of the method according to any one of claims 1 to 15.