Method for page navigation between applications, and electronic device

Abstract

The present application relates to the technical field of terminals, and provides a method for page navigation between applications, and an electronic device, capable of implementing direct navigation from a launched page back to a page of a launching application, without sequentially navigating through multiple pages of the launched application, thereby avoiding wasting a lot of time, further improving the page navigation efficiency, and improving the user experience. In the method, an electronic device displays a first page of a first application; in response to an operation that the first application launches a second page of a second application, the electronic device displays the second page of the second application, wherein the second page is added to a main task stack of the second application, the second page is configured with a page mark, the main task stack is used for saving an opened page in the second application, and the page mark is used for indicating that the second page is launched by another application; the electronic device receives a return gesture on the displayed second page, and in response to the return gesture, displays the first page of the first application.

Description

Method for inter-application page jump and electronic device

[0001] The present application claims priority from the Chinese patent application No. 202411380600.5 filed on September 27, 2024, and entitled "Method for inter-application page jump and electronic device", the content of which is incorporated herein by reference in its entirety. TECHNICAL FIELD

[0002] The present application relates to the technical field of terminals, and in particular to a method for inter-application page jump and an electronic device. BACKGROUND

[0003] Currently, inter-application pull-up can enable one application to use the function of another application. For example, when a user is using a shopping application to purchase goods, after clicking a purchase control, the shopping application pulls up a payment page of a payment application, and the user can complete payment on the payment page. Then, if the user wants to continue browsing goods, the user can make a return gesture on the payment page to trigger the device to display the page of the shopping application again, thereby realizing page jump.

[0004] However, if the user has browsed some pages in the payment application before the payment page is pulled up, after the user makes a return gesture on the payment page, the device displays the historical pages browsed by the user in the payment application in sequence, and only after the historical pages are displayed, the device displays the page of the shopping application again.

[0005] It can be seen that in the above page jump process, if the payment application has been browsed for a large number of pages before the payment page is pulled up, it takes a lot of time to jump back to the page of the shopping application, which not only reduces the efficiency of page jump, but also affects the user experience. SUMMARY

[0006] The present application provides a method for inter-application page jump and an electronic device, which can realize direct jump from the pulled-up page to the page of the pull-up side without experiencing one-layer jump of the pulled-up side pages, thereby saving a lot of time, improving the efficiency of page jump, and improving the user experience.

[0007] To achieve the above object, the embodiments of the present application adopt the following technical solutions:

[0008] In a first aspect, a method for inter-application page jump is provided. In an example where the method is applied to an electronic device, the electronic device displays a first page of a first application, and in response to an operation of pulling up a second page of a second application by the first application, the electronic device displays the second page of the second application. The second page is added to a main task stack of the second application, and the second page is configured with a page marker. The main task stack is used to save the pages that are opened in the second application, and the page marker is used to indicate that the second page is pulled up by another application. The electronic device receives a back gesture on the displayed second page, and in response to the back gesture, displays the first page of the first application.

[0009] In the above method, after the second page is pulled up, the electronic device can save the second page with the page marker in the main task stack of the second application. Thereafter, when the electronic device displays the second page with the page marker, the electronic device can return to the first page of the first application in response to a back gesture, thereby realizing the page jump between applications. Such page jump is directly realized across applications. If there are other pages in the main task stack of the second application before the second page, the page jump does not need to be performed layer by layer in the main task stack, thereby saving the time for page jump between applications and improving the efficiency of page jump.

[0010] In an implementation of the first aspect, the second application includes multiple pages, and the multiple pages include the second page and a third page. After the second page of the second application is displayed, if the second application receives a page jump event, the electronic device displays the third page of the second application in response to the page jump event received by the second application. The page jump event is used to indicate a jump from the second page to the third page, and the third page is added to the main task stack of the second application. The electronic device receives a back gesture on the displayed third page, and in response to the back gesture, displays the second page of the second application.

[0011] In the above implementation, if the electronic device receives a back gesture when displaying a page of the second application that is not configured with a page marker, the electronic device first performs a jump of the page in the main task stack, and jumps the displayed page to a page before the page in the main task stack, thereby realizing the page jump in the second application. After the second page is displayed, if a back gesture is received again, the electronic device directly displays the first page of the first application. In this way, the direct jump of the page between applications can also be realized, thereby saving time and improving the efficiency of page jump.

[0012] In an implementation of the first aspect, the electronic device obtains parameter information from the first application, where the parameter information is used to indicate the second page. The electronic device sends the parameter information to the second application, and obtains the second page determined by the second application according to the parameter information. Thereafter, the electronic device displays the second page.

[0013] In the above implementation, when responding to the operation of the first application pulling up the page of the second application, the electronic device can more accurately determine the page of the second application to be pulled up and displayed through the parameter information sent by the first application, thereby bringing a better user experience.

[0014] In an implementation of the first aspect, the return gesture is a gesture of sliding from an edge of the screen to the middle of the screen, for example, a gesture of sliding a finger from the left edge of the screen to the right or a gesture of sliding a finger from the right edge of the screen to the left.

[0015] In the above implementation, these return gestures are the return gestures that are commonly used by users or the return gestures that are most familiar to users, so that the user operates the second page displayed by the electronic device or operates the electronic device through these return gestures, which conforms to the use habit of the user and ensures the user experience.

[0016] In an implementation of the first aspect, in response to the operation of the first application pulling up the second page of the second application, the electronic device includes: receiving, by the electronic device, an operation of a user on a function control of the first page, and displaying, in response to the operation, the second page of the second application; and wherein the second page displays content associated with the first page or the function control.

[0017] In the above implementation, the user can trigger the page jump between applications through the function control on the first page of the first application. For example, the function control of the first page can provide functions such as payment and login, and the operation of the user on the function control can trigger the operation of the first application pulling up the second page of the second application, and the second page can display payment information, login information, and the like provided by the second application.

[0018] In an implementation of the first aspect, after the electronic device responds to the operation of the first application pulling up the second page of the second application again, the electronic device displays the second page of the second application. Then, the electronic device receives, on the displayed second page, an operation of returning to the desktop, cancels the page mark of the second page, and displays the desktop.

[0019] It can be understood that the above page mark can be configured by the developer of the application before the application is launched, or can be configured by the application after the application page is pulled up. The electronic device receives, on the displayed second page, the operation of returning to the desktop, indicating that the calling chain between the second application and the first application is disconnected, that is, the calling relationship between the second page and the first page of the first application no longer exists. If the page mark is configured by the application after the application page is pulled up, the calling chain is disconnected, and the page mark of the second page also does not need to exist, so that the electronic device can cancel the page mark of the second page.

[0020] In a second aspect, a method for inter-application page jump is provided. In an example where the method is applied to an electronic device, the electronic device displays a first page of a first application, and in response to an operation of pulling up a second page of a second application from the first page, the electronic device displays the second page of the second application, where the second page is added to a temporary task stack of the second application, the temporary task stack of the second application is used at least to save the second page pulled up from the first page, and the second page is the first page added to the temporary task stack of the second application. Then, the electronic device receives a back gesture on the displayed second page, and in response to the back gesture, displays the first page of the first application.

[0021] In the above method, after the second page is pulled up, the electronic device saves the second page in the temporary task stack of the second application. The electronic device returns to the first page of the first application in response to the back gesture only when the first page of the first application is the first page added to the temporary task stack (or the page at the top of the temporary task stack). The page jump between applications is directly implemented across applications. If there are other pages in the main task stack of the second application before the second page, the page jump does not need to be performed layer by layer in the main task stack, thereby saving the time for page jump between applications and improving the efficiency of page jump.

[0022] In an implementation of the second aspect, the temporary task stack is further used to save at least one page of the second application that is opened after the second page is pulled up. After the second page of the second application is displayed, if the second application receives a page jump event, the electronic device displays a third page of the second application in response to the page jump event, where the page jump event is used to indicate a jump from the second page to the third page, and the third page is added to the temporary task stack of the second application. Then, the electronic device receives a back gesture on the displayed third page, and in response to the back gesture, displays the second page of the second application and removes the third page from the temporary task stack.

[0023] In the above implementation, if the electronic device receives a back gesture when the displayed page is not the first page added to the temporary task stack of the second application, the electronic device first performs a jump of the page in the temporary task stack, and jumps the displayed page to a page before the page in the temporary task stack, to implement a page jump in the second application. When the electronic device displays the second page, if a back gesture is received again, the electronic device directly displays the first page of the first application. In this way, the page jump between applications is directly implemented, thereby saving time and improving the efficiency of page jump.

[0024] In an implementation form of the second aspect, the temporary task stack of the second application is destroyed after the first page of the first application is displayed; or the temporary task stack of the second application is destroyed after the second application is placed in the background.

[0025] In the above implementation form, the display of the content by the second page jumping back to the first page and the second application being placed in the background both indicate that the call chain between the first application and the second application is disconnected. The temporary task stack of the application does not affect the main task stack of the application. After the call chain between the first application and the second application is disconnected, the temporary task stack is destroyed, and the main task stack of the second application still exists. When the user places the second application in the foreground of the mobile phone again, the page opened in the second application is added to the main task stack of the second application.

[0026] In an implementation form of the second aspect, after the second page of the second application is displayed, if the second application pulls up the fourth page of the third application, the electronic device displays the fourth page of the third application in response to the operation of the second application pulling up the fourth page of the third application, the fourth page is added to the temporary task stack of the third application, and the fourth page is the first page in the temporary task stack of the third application. Then, the electronic device receives a return gesture on the displayed fourth page, and displays the second page of the second application in response to the return gesture.

[0027] In the above implementation form, the second application can also pull up the page of the third application. In this case, after the fourth page of the third application is pulled up, the fourth page is saved in the temporary task stack of the third application. The electronic device returns the second page of the second application in response to the return gesture only when the first-in fourth page in the temporary task stack is displayed, thereby realizing the page jumping between applications. Such page jumping is directly realized across applications. If there are other pages in the main task stack of the second application before the second page, the page jumping does not need to be performed layer by layer in the main task stack, thereby saving the time of page jumping between applications and improving the efficiency of page jumping.

[0028] In an implementation form of the second aspect, the electronic device destroys the temporary task stack of the second application in response to the operation of the second application pulling up the fourth page of the third application; when the temporary task stack of the second application still saves at least one page, the at least one page is saved into the main task stack of the second page; and the main task stack is used to save the opened page in the second application.

[0029] In the above implementation form, it can be ensured that the at least one page opened in the second application is not destroyed. In this way, when the user uses the second application again, the last browsed page can still be viewed, thereby ensuring the user experience.

[0030] It can be understood that the life cycle of the main task stack of the application is consistent with the life cycle of the application, and the temporary task stack of the application only exists when the application is called by another application and the called application is in the foreground.

[0031] In an implementation form of the second aspect, the electronic device obtains parameter information from the first application, where the parameter information is used to indicate the second page. The electronic device sends the parameter information to the second application, and obtains the second page determined by the second application according to the parameter information. Then, the electronic device displays the second page.

[0032] In the implementation form above, in response to the operation of the first application pulling up the page of the second application, the electronic device can more accurately determine the page of the second application to be pulled up and displayed through the parameter information sent by the first application, thereby bringing a better user experience.

[0033] In an implementation form of the second aspect, in response to the operation of the first application pulling up the second page of the second application, the electronic device includes: the electronic device receives an operation of a user on a function control of the first page, and displays the second page of the second application in response to the operation; where the second page displays content associated with the first page or the function control.

[0034] In the implementation form above, the user can trigger the page jump between applications through the function control on the first page of the first application. For example, the function control of the first page can provide functions such as payment and login, and the operation of the user on the function control can trigger the operation of the first application pulling up the second page of the second application, and the second page can display payment information, login information, etc. provided by the second application.

[0035] In an implementation form of the second aspect, the return gesture is a gesture of sliding from the edge of the screen to the middle of the screen, such as a gesture of sliding a finger from the left edge of the screen to the right or a gesture of sliding a finger from the right edge of the screen to the left.

[0036] These return gestures are common return gestures used by users, or return gestures that users are used to, so that the user operates the second page displayed by the electronic device or operates the electronic device through these return gestures, which conforms to the use habit of the user and ensures the use experience of the user.

[0037] In a third aspect, an electronic device is provided, including a memory and one or more processors; the memory is coupled to the processor; and the memory stores computer program codes including computer instructions, which, when executed by the processor, cause the electronic device to perform the method for page jump between applications as described in the first aspect and any implementation form thereof, or perform the method for page jump between applications as described in the second aspect and any implementation form thereof.

[0038] In a fourth aspect, a computer readable storage medium is provided, including computer instructions, when the computer instructions are run on an electronic device, causing the electronic device to perform the method for inter-application page jump as described in the first aspect and any possible implementation thereof, or perform the method for inter-application page jump as described in the second aspect and any possible implementation thereof.

[0039] In a fifth aspect, a computer program product is provided, when the computer program product is run on a computer, causing the computer to perform the method for inter-application page jump as described in the first aspect and any possible implementation thereof, or perform the method for inter-application page jump as described in the second aspect and any possible implementation thereof.

[0040] The electronic device provided in the third aspect, the computer readable storage medium provided in the fourth aspect, and the computer program product provided in the fifth aspect can achieve the beneficial effects as described in the first aspect and any possible implementation thereof, or the beneficial effects as described in the second aspect and any possible implementation thereof, which will not be described here again. BRIEF DESCRIPTION OF DRAWINGS

[0041] FIG. 1 shows a schematic diagram of a task stack of an application according to an embodiment of the present application;

[0042] FIG. 2 shows a schematic diagram of a return control according to an embodiment of the present application;

[0043] FIG. 3 shows a schematic diagram of a structure of an electronic device according to an embodiment of the present application;

[0044] FIG. 4 shows a schematic diagram of a structure of an electronic device according to an embodiment of the present application;

[0045] FIG. 5 shows a schematic diagram of a processing procedure of a running management service in an electronic device according to an embodiment of the present application;

[0046] FIG. 6 shows a schematic diagram of a method for inter-application page jump according to an embodiment of the present application;

[0047] FIG. 7 shows a schematic diagram of inter-application page jump according to an embodiment of the present application;

[0048] FIG. 8 shows a schematic diagram of a return gesture according to an embodiment of the present application;

[0049] FIG. 9 shows a schematic diagram of page jump according to an embodiment of the present application;

[0050] FIG. 10 shows a schematic diagram of page jump according to an embodiment of the present application;

[0051] FIG. 11 shows a flow diagram of a method for inter-application page jump according to an embodiment of the present application;

[0052] FIG. 12 shows a diagram of a page jump according to an embodiment of the present application;

[0053] FIG. 13 shows a diagram of an electronic device according to an embodiment of the present application. DETAILED DESCRIPTION

[0054] The technical solutions in the embodiments of the present application will be described below with reference to the drawings in the embodiments of the present application. In the description of the present application, unless otherwise specified, " / " represents an "or" relationship between the associated objects before and after, for example, A / B can represent A or B; in the present application, "and / or" is only a description of the associated relationship between the associated objects, which means that there can be three relationships, for example, A and / or B, which means that there are three cases of A alone, A and B together, and B alone, where A and B can be singular or plural. In the description of the present application, unless otherwise specified, "multiple" means two or more than two. "At least one of the following" or similar expressions means any combination of these items, including any combination of single item or multiple items. For example, at least one of a, b, or c, can mean a, b, c, a-b, a-c, b-c, or a-b-c, where a, b, and c can be single or multiple. In addition, in order to clearly describe the technical solutions of the embodiments of the present application, in the embodiments of the present application, "first", "second", and the like are used to distinguish the same items or similar items with basically the same function and effect. Those skilled in the art can understand that "first", "second", and the like do not limit the quantity and execution order, and "first", "second", and the like do not necessarily mean different. At the same time, in the embodiments of the present application, "exemplary" or "for example" means to serve as an example, illustration or description. Any embodiment or design scheme described as "exemplary" or "for example" in the embodiments of the present application should not be interpreted as more preferred or more advantageous than other embodiments or design schemes. Rather, the use of "exemplary" or "for example" is intended to present the relevant concept in a specific manner, for easy understanding.

[0055] In addition, the business scenarios described in the embodiments of the present application are used to more clearly illustrate the technical solutions of the embodiments of the present application, and do not constitute a limitation on the technical solutions provided by the embodiments of the present application. Those skilled in the art can know that as new business scenarios appear, the technical solutions provided by the embodiments of the present application are also applicable to similar technical problems.

[0056] An application usually has a respective task stack to save or manage the opened pages in the application. The task stack is a data structure of last-in first-out, the first-in stack is placed at the bottom of the stack, and the last-in stack is placed at the top of the stack.

[0057] Currently, the mutual pull-up between applications can enable one application to use the function of another application.

[0058] For example, when a user purchases a product using a shopping application, after clicking a purchase control, the shopping application pulls up a payment page of a payment application, and the user can complete payment on the payment page. After the payment page is pulled up, the payment page is added to the task stack of the payment application. Then, if the user wants to continue browsing the product, the user can make a return gesture on the payment page to trigger the device to display the page of the shopping application again, thereby realizing the page jump.

[0059] However, if the user has browsed some pages in the payment application before the payment page is pulled up, the task stack has already saved some pages before the payment page is stacked. After the user makes a return gesture on the payment page, the device displays the historical pages that the user has browsed in the payment application according to the characteristics of the task stack, and then displays the page of the shopping application again, thereby realizing the page jump between the payment application and the shopping application.

[0060] In the above page jump process, if the payment application has been browsed for many pages before the payment page is pulled up, the return of the page in the payment application needs to be performed layer by layer to jump back to the page of the shopping application, which wastes a lot of time, thereby reducing the efficiency of the page jump, and the layer-by-layer return of the page also affects the user experience.

[0061] In some solutions, the pulled-up application page can be added to the task stack of the pull-up application, thereby realizing the page jump between applications. For example, referring to FIG. 1, when the application A pulls up the page of the application B, the page only needs to be added to the task stack of the application A for management, thereby realizing one-step jump to the application. For example, after the user finishes the operation on the page of the application B, the page is returned to the page of the application A through the return key or the return gesture. In this solution, because the page of the application B is added to the task stack of the application A, the task stack of the application B is independent and is not affected. However, the pulled-up application page is not in the task stack of the pulled-up application, which is not conducive to the management of the pulled-up application page.

[0062] In some other solutions, a default return control or return button can be provided when the pulled-up application page is displayed, and the user can click the return control to realize the page jump between applications. For example, as shown in FIG. 2, a control corresponding to the shopping application is displayed in the upper left corner of the information page, thereby indicating that the currently displayed information page is a page pulled up by the shopping application. After viewing the information page, the user can click the control corresponding to the shopping application, thereby directly jumping back to the page of the shopping application.

[0063] Although this solution can not add the pulled-up page to the task stack of the pulled-up application, the return control or return button is arranged above the page, which is very inconvenient for the user to operate with one hand for some devices with a large screen. In addition, the user may be used to using a global return gesture to perform the page jump operation in the daily use of the device. The page jump through the return control as described above will also make the user's operation inconsistent with the usual use habit, thereby affecting the user experience.

[0064] Based on the above, the embodiments of the present application provide a method for page jump between applications, in which the user can follow the usual use habit to make a return gesture on the pulled-up page, thereby jumping the displayed page back to the page of the pulling side. In this way, the user experience can be ensured. In addition, the user can control the page jump with one hand, so that the user's operation is more convenient. In addition, the method can also realize the direct jump from the pulled-up page back to the page of the pulling side without experiencing the layer-by-layer jump of the pages of the pulling side, thereby saving a lot of time and improving the efficiency of page jump and the user experience.

[0065] For example, the above method is applied to an electronic device, which can display a first page of a first application. Through a click operation, a confirmation operation or a jump operation and the like on the first page, the electronic device can display a second page of a second application in response to the operation of the first application pulling up the second application, wherein the second page is added to the main task stack of the second application, and the second page is configured with a page marker. The main task stack is used to save the opened pages in the second application. The page marker is used to indicate the pages of the second application that can be pulled up by other applications. Then, the electronic device receives a return gesture on the displayed second page, and displays the first page in response to the return gesture.

[0066] In this solution, after the second page is pulled up, the electronic device saves the second page with the page marker in the task stack of the second application. When the electronic device displays the page with the page marker, the electronic device can jump back to the first page of the first application in response to the return gesture, thereby realizing the page jump between applications.

[0067] For example, the above method is applied to an electronic device, the electronic device can display a first page of a first application. Through a click operation, a confirmation operation or a jump operation on the first page, the electronic device can display a second page of a second application in response to the operation of the first application pulling up the second application, wherein the second page is added to a temporary task stack of the second application, the temporary task stack of the second application is used to save at least the second page pulled up by the first page, and the second page is the first page in the temporary task stack. Subsequently, the electronic device receives a return gesture on the displayed second page, and displays the first page in response to the return gesture.

[0068] In this scheme, after the second page is pulled up, the electronic device saves the second page in the temporary task stack of the second application, and the electronic device only jumps back to the first page of the first application in response to the return gesture when the second page in the temporary task stack is displayed, thereby realizing the page jump between applications.

[0069] When the above method is applied to the electronic device, in some embodiments, referring to FIG. 3, the electronic device 100 can include a processor 110, an external memory interface 120, an internal memory 121, a universal serial bus (USB) interface 130, a charging management module 140, a power management module 141, a battery 142, an antenna 1, an antenna 2, a mobile communication module 150, a wireless communication module 160, an audio module 170, a sensor module 180, a key 190, a motor 191, an indicator 192, a camera 193, a display screen 194, and a subscriber identification module (SIM) card interface 195, etc.

[0070] It can be understood that the structure shown in the embodiments of the present application does not constitute a specific limitation on the electronic device 100. In some other embodiments of the present application, the electronic device 100 can include more or fewer components than shown, or combine some components, or split some components, or different arrangement of components.

[0071] The processor 110 can include one or more processing units (not shown in FIG. 3), for example: the processor 110 can include an application processor (AP), a modem processor, a graphics processing unit (GPU), an image signal processor (ISP), a controller, a memory, a video codec, a digital signal processor (DSP), a baseband processor, and / or a neural-network processing unit (NPU), etc. Among them, different processing units can be independent devices, or can be integrated in one or more processors.

[0072] The controller can be the nerve center and command center of the electronic device 100. The controller can generate operation control signals according to instruction operation codes and timing signals, and complete the control of fetching instructions and executing instructions.

[0073] The processor 110 can also be provided with a memory for storing instructions and data.

[0074] In some embodiments, the processor 110 can include one or more interfaces (not shown in FIG. 3).

[0075] Among them, the USB interface 130 is an interface conforming to the USB standard specification, which can be a Mini USB interface, a Micro USB interface, a USB Type C interface, etc.

[0076] The charging management module 140 is used to receive charging input from the charger. Among them, the charger can be a wireless charger, or a wired charger.

[0077] The power management module 141 is used to connect the battery 142 and the charging management module 140 with the processor 110. The power management module 141 receives input from the battery 142 and / or the charging management module 140, and supplies power to the processor 110, the internal memory 121, the external memory, the display screen 194, the camera 193, and the wireless communication module 160, etc. The power management module 141 can also be used to monitor parameters such as battery capacity, battery cycle number, battery health status (leakage, impedance), etc.

[0078] The wireless communication function of the electronic device 100 can be realized through the antenna 1, the antenna 2, the mobile communication module 150, the wireless communication module 160, the modem processor, and the baseband processor, etc.

[0079] Antenna 1 and antenna 2 are used for transmitting and receiving electromagnetic wave signals. Each antenna in electronic device 100 can be used to cover a single or multiple communication frequency bands. Different antennas can also be multiplexed to improve the utilization of antennas. For example: antenna 1 can be multiplexed as a diversity antenna for wireless local area networks. In some other embodiments, antennas can be used in combination with tuning switches.

[0080] Mobile communication module 150 can provide solutions for wireless communication including 2G / 3G / 4G / 5G, etc. applied on electronic device 100.

[0081] Wireless communication module 160 can provide solutions for wireless communication including wireless local area networks (WLAN) (such as wireless fidelity (Wi-Fi) networks), Bluetooth (BT), global navigation satellite system (GNSS), frequency modulation (FM), near field communication (NFC), infrared technology (IR), etc. applied on electronic device 100.

[0082] In some embodiments, antenna 1 of electronic device 100 is coupled with mobile communication module 150, and antenna 2 is coupled with wireless communication module 160, so that electronic device 100 can communicate with networks and other devices through wireless communication technologies.

[0083] Electronic device 100 realizes display functions through GPU, display screen 194, and application processor, etc. GPU is a microprocessor for image processing, connected with display screen 194 and application processor. GPU is used to perform mathematical and geometric calculations for graphics rendering.

[0084] Display screen 194 is used to display images, videos, etc.

[0085] In some examples, display screen 194 (which can be referred to as a screen in subsequent embodiments) can display icons of applications in electronic device 100. After a user clicks an application icon, the application is started, and display screen 194 can further display a page of the application.

[0086] In some examples, when the user uses the first application, if some operations, such as a click operation, a confirmation operation, or a jump operation, are performed on the first application or on a page of the first application, the first application can trigger the pull-up of a page of the second application. After the page of the second application is pulled up, the display screen 194 also displays the page of the second application. When the display screen 194 displays the page of the second application, if the user makes a return gesture on the display screen 194, the display screen 194 also displays the page of the first application again, thereby presenting the user with the effect of jumping back from the page of the second application to the page of the first application.

[0087] The electronic device 100 can implement a photographing function through an ISP, the camera 193, a video codec, a GPU, the display screen 194, and an application processor.

[0088] The external memory interface 120 can be used to connect an external memory card, such as a Micro SD card, to expand the storage capacity of the electronic device 100. The external memory card communicates with the processor 110 through the external memory interface 120 to implement a data storage function. For example, music, video, and other files are saved in the external memory card.

[0089] The internal memory 121 can be used to store computer executable program codes, which include instructions. The processor 110 executes various function applications and data processing of the electronic device 100 by running the instructions stored in the internal memory 121.

[0090] In some examples, when a page of an application is opened, the processor 110 can save the page in the task stack of the application by running the instructions stored in the internal memory 121, and control the screen to display the page.

[0091] In some examples, when the user uses the first application, if the first application pulls up a page of the second application, the processor 110 also saves the page of the second application in the task stack of the second application by running the instructions stored in the internal memory 121, and controls the screen to jump from the displayed page of the first application to the page of the second application. Subsequently, the processor 110 also identifies whether the user makes a return gesture and whether the displayed page has a page marker by running the instructions stored in the internal memory 121. If the user makes a return gesture and the displayed page has a page marker, the processor 110 controls the screen to jump from the displayed page of the second application to the page of the first application by running the instructions stored in the internal memory 121.

[0092] In some examples, when the user is using the first application, if the first application pulls up a page of the second application, the processor 110 further saves the page of the second application in the temporary task stack of the second application by running the instructions stored in the internal memory 121, and controls the page displayed on the screen to jump to the page of the second application. Then, the processor 110 further identifies whether the gesture of the user on the screen and the page displayed on the screen are the page at the bottom of the temporary task stack of the second application by running the instructions stored in the internal memory 121. If the user makes a return gesture and the page displayed on the screen is the page at the bottom of the temporary task stack of the second application, the processor 110 controls the page displayed on the screen to jump to the page of the first application by running the instructions stored in the internal memory 121.

[0093] The audio module 170 is configured to convert digital audio information into analog audio signals and convert analog audio input into digital audio signals. The keys 190 include a power key, a volume key, and the like. The motor 191 can generate a vibration prompt. The indicator 192 can be an indicator light, which can be used to indicate a charging state, a power change, and can also be used to indicate a message, a missed call, a notification, and the like. The SIM card interface 195 is configured to connect a SIM card.

[0094] When the above-mentioned electronic device implements the method for inter-application page jumping provided in the embodiments of the present application, the user can follow the daily use habit to make a return gesture on the pulled-up page, and the electronic device can jump from the displayed pulled-up page back to the pulled-up page, so as to ensure the user experience. In addition, the user can also control the page jumping with one hand, so that the user operation is more convenient. In addition, the above-mentioned method can directly jump from the pulled-up page back to the pulled-up page, without experiencing a layer-by-layer jump of the pulled-up page, so as to save a lot of time, improve the efficiency of page jumping, and improve the user experience.

[0095] In some embodiments, the software system of the electronic device 100 can adopt a layered architecture, an event-driven architecture, a microkernel architecture, a microservice architecture, or a cloud architecture. The embodiments of the present application take a layered architecture of a mobile operating system as an example to exemplarily illustrate the software structure of the electronic device 100.

[0096] Referring to FIG. 4, the layered architecture of the electronic device 100 divides the software into several layers, each layer has a clear role and division of labor. The layers communicate with each other through a software interface. In some embodiments, the mobile operating system is divided into four layers, from top to bottom, an application layer, an application framework layer, a system service layer, and a kernel layer.

[0097] The application layer can include a series of application packages.

[0098] As shown in FIG. 4, the application package can include applications such as shopping, payment, camera, calendar, call, gallery, map, navigation, Bluetooth, music, video, short message, etc.

[0099] The application framework layer provides an application programming interface (API) and a programming framework for the applications of the application layer. The application framework layer includes some pre-defined functions.

[0100] As shown in FIG. 4, the application framework layer can include a window manager, a content provider, a view system, a phone manager, a resource manager, a notification manager, etc.

[0101] The window manager is used to manage window programs. The window manager can acquire the size of a display screen, determine whether there is a status bar, lock a screen, capture a screen, etc.

[0102] The content provider is used to store and acquire data, and make the data accessible to applications. The data can include videos, images, audios, dialed and received calls, browsing history and bookmarks, phone books, etc.

[0103] The view system includes visual controls, such as a control for displaying text, a control for displaying pictures, etc. The view system can be used to build an application. A display interface can be composed of one or more views. For example, a display interface including a short message notification icon can include a view for displaying text and a view for displaying pictures.

[0104] The phone manager is used to provide the communication function of the electronic device 100.

[0105] The resource manager provides various resources for applications, such as localized strings, icons, pictures, layout files, video files, etc.

[0106] The notification manager makes it possible for an application to display notification information in a status bar, which can be used to convey a message of the notification type, which can automatically disappear after a short stay without user interaction. The notification manager can also be a notification appearing in the form of a chart or a scroll bar text in the top status bar of the system, such as a notification of an application running in the background, or a notification appearing in the form of a dialog window on the screen.

[0107] In some examples, the application framework layer can also include a routing framework. The routing framework can implement the jump of an intra-application page, for example, the routing framework can implement the jump from page 1 of a first application to page 2 of the first application.

[0108] In some examples, the routing framework can also provide multiple interfaces, different interfaces can implement the intra-application page jump in different operating systems. In addition, each interface can provide a function of marking an application page.

[0109] The developer of the application can configure the page mark of the application page through the above interface, and the page mark is used to indicate that the application page can be pulled up by other applications.

[0110] Alternatively, the application can also call the above interface to configure the page mark of the pulled-up page after the page is pulled up by other applications.

[0111] In the case that the screen currently displays an application page with a page mark and a return gesture is received, the electronic device 100 can implement the page jump between applications, that is, the currently displayed application page with a page mark can be switched to the page of the other application that pulls up the page.

[0112] The system service layer can include multiple function modules. For example: a surface manager, media libraries, a three-dimensional graphics processing library (for example: OpenGL ES), a 2D graphics engine (for example: SGL, Vulkan) and the like.

[0113] The surface manager is used to manage the display subsystem, and provides fusion of 2D and 3D layers for multiple applications.

[0114] The media library supports playback and recording of multiple commonly used audio, video formats, and static image files and the like. The media library can support multiple audio and video encoding formats, for example: MPEG4, H.264, MP3, AAC, AMR and the like.

[0115] The three-dimensional graphics processing library is used to implement three-dimensional graphics drawing, image rendering, synthesis, and layer processing and the like.

[0116] The 2D graphics engine is a drawing engine for 2D drawing.

[0117] In some examples, the system service layer can also include a running management service. The running management service can manage the task stack of the application and implement the above-mentioned page jump between applications. When one application pulls up another application, the running management service records the pull-up relationship between the applications (or application pages).

[0118] For example, referring to (a) of FIG. 5, when the user is using application A, if application A pulls up page B3 of application B, the running management service can add page B3 (pages B1 and B2 of application B previously exist in the task stack of application B) in the task stack of application B, and instruct the screen to display page B3. Since page B3 is pulled up by application A, page B3 has a pre-configured page marker. After the user makes a return gesture on the screen displaying page B3, the running management service determines that page B3 has a page marker, and thus determines that page B3 is pulled up by another application. According to the pull-up relationship, the running management service determines that page B3 is pulled up by application A, and thus instructs the screen to display the page of application A, realizing the page jump between application A and application B without going through page B2 and page B1 in the task stack.

[0119] For another example, referring to (b) of FIG. 5, when the user is using application A, if application A pulls up page B3 of application B, the running management service can add page B3 in the temporary task stack of application B, and instruct the screen to display page B3. The temporary task stack of application B does not affect the task stack (i.e., the main task stack) of application B. The temporary task stack saves the pages of application B pulled up by other applications and the pages of application B opened after the pages. The main task stack saves the pages of application B pulled up by the desktop or the pages of application B jumped within the application. After the user makes a return gesture on the screen displaying page B3, if page B3 is the page at the bottom of the temporary task stack, the running management service determines that page B3 is pulled up by another application. According to the pull-up relationship, the running management service determines that page B3 is pulled up by application A, and thus instructs the screen to display the page of application A, realizing the page jump between application A and application B.

[0120] The kernel layer is a layer between hardware and software. The kernel layer at least includes a display driver, a camera driver, an audio driver, and a sensor driver.

[0121] When the above-described electronic device implements the method for page jump between applications provided by the embodiments of the present application, the user can follow the daily use habit to make a return gesture on the pulled-up page, and the electronic device can jump from the displayed pulled-up page back to the pull-up page, which can ensure the user experience. In addition, the user can control the page jump with one hand, which makes the operation of the user more convenient. In addition, the above-described method can realize the direct jump from the pulled-up page back to the pull-up page without going through the layer-by-layer jump of the pulled-up pages, which does not waste much time, thereby improving the efficiency of page jump and the user experience.

[0122] The electronic device can be a mobile phone, a tablet computer, a personal computer, a wearable device (such as a smart watch, a smart bracelet, etc.), a smart home device (such as a television, etc.), a vehicle terminal (such as a vehicle-mounted terminal), or the like.

[0123] The following embodiments take the mobile phone as an example to describe the method for inter-application page jump.

[0124] In some embodiments, before the application is put on the shelf, the developer of the application can call an interface provided by an operating system or a routing framework of the operating system to configure a page mark of the application page according to an operating system to which the application is adapted.

[0125] For example, the interface provided by the Android operating system is StartActivity, The interface provided by the Android operating system is StartActivity, The interface provided by the Android operating system is StartActivity, The interface provided by the Android operating system is StartActivity,

[0126] The page mark is used to indicate that the application page is a page pulled up by another application, or is used to indicate that the application page can be pulled up by another application. That is, the page pulled up by another application in an application is configured with the page mark.

[0127] In some embodiments, after the application is put on the shelf and installed on the mobile phone, referring to FIG. 6, the method for inter-application page jump can include the following steps S601-S604.

[0128] S601, the mobile phone displays a first page of a first application.

[0129] It can be understood that the first application represents a puller that can pull up other applications in the mobile phone.

[0130] In some examples, the first page can be any page in the first application, and the user performs an operation on the first page, which can trigger the first application to pull up a page of another application.

[0131] For example, when the first application is a shopping application, the first page can be an order confirmation page, and the user performs a payment operation on the order confirmation page, such as clicking a function control representing payment, etc., which can trigger the shopping application to pull up a payment page of a payment application.

[0132] For example, when the first application is a shopping application, the first page can be a login page, and the user performs an operation of logging in using an account of a chat application on the login page, such as clicking a function control representing login, etc., which can trigger the shopping application to pull up an authorization page of the chat application.

[0133] For example, when the first application is a video application, the first page can be a live broadcast page with a link to a certain product. If the user performs an operation of clicking the link to the product on the live broadcast page, the video application can be triggered to pull up the product page of the shopping application.

[0134] S602, the mobile phone displays the second page of the second application in response to the operation of pulling up the second page of the second application by the first application.

[0135] It can be understood that the second application represents a pulled-up party in the mobile phone that is pulled up by other applications.

[0136] In some examples, the second page is a page in the second application that can be pulled up by other applications. In S602, the mobile phone can present the user with a page jump effect between the application from which the first page jumps to the second page.

[0137] For example, the first application is a shopping application, the second application is a payment application, the first page is an order confirmation page, and the second page is a payment page. As shown in (a) of FIG. 7, after the payment page is pulled up by the shopping application, the mobile phone displays a page jump from the order confirmation page to the payment page, and the payment page displays payment information such as a price, an account, and a password prompt box.

[0138] For example, the first application is a shopping application, the second application is a chat application, the first page is a login page, and the second page is an authorization page. As shown in (b) of FIG. 7, after the authorization page is pulled up by the shopping application, the mobile phone displays a page jump from the login page to the authorization page, and the authorization page displays login information such as a prompt to authorize login.

[0139] For example, the first application is a video application, the second application is a shopping application, the first page is a live broadcast page, and the second page is a product page. As shown in (c) of FIG. 7, after the product page is pulled up by the video application, the mobile phone displays a page jump from the live broadcast page to the product page.

[0140] In some examples, the first application and the second application each have a respective main task stack, where the main task stack is used to save a page that is opened in the first application or the second application.

[0141] For example, after the user clicks an icon of an application on the desktop of the mobile phone, the application is pulled up by the desktop of the mobile phone, that is, the application is opened. After the application is opened, the mobile phone displays a home page of the application. Accordingly, the mobile phone adds the page to the main task stack of the application. Subsequently, if the user continues to click a control or performs a gesture on the home page of the application, other pages of the application are opened, and the mobile phone also adds the other pages to the main task stack of the application.

[0142] When the second page of the second application is pulled up by the first application, the mobile phone can add the second page to the main task stack corresponding to the second application.

[0143] In some examples, since the pages in the second application that can be pulled up by other applications are pre-configured with page markers, the second page saved in the main task stack is also configured with a page marker.

[0144] In some examples, the mobile phone can also obtain parameter information indicating the second page from the first application, and send the parameter information to the second application, so that the second application determines the second page according to the parameter information, and the mobile phone displays the second page again.

[0145] For example, after the user performs an operation on the page A1 of the application A, the application A is triggered to pull up the page B3 of the application B. In this case, the application A sends parameter information indicating the page B3 to the running management service in the mobile phone. The running management service sends the parameter information to the application B, and the application B determines the page B3 to be pulled up according to the parameter information, so that the running management service instructs the mobile phone to display the page B3 again.

[0146] Alternatively, after receiving the parameter information, the running management service can determine the page B3 of the application B to be pulled up according to the parameter information, so that the running management service instructs the mobile phone to display the page B3 again.

[0147] In this way, when responding to the operation of pulling up the page of the second application by the first application, the mobile phone can more accurately determine the page of the second application to be pulled up and displayed through the parameter information sent by the first application, thereby providing a better user experience.

[0148] S603, the mobile phone receives a return gesture on the displayed second page configured with a page marker.

[0149] In some examples, the return gesture can be a return gesture that the user is used to using when operating the mobile phone, which can also be referred to as a global return gesture. The return gesture can be a gesture of sliding from the edge of the screen to the middle of the screen, for example, the gesture of sliding the finger from the left edge of the screen to the right as shown in (a) of FIG. 8, or the gesture of sliding the finger from the right edge of the screen to the left as shown in (b) of FIG. 8, etc.

[0150] Since these return gestures are the return gestures that the user is more used to using, or the return gestures that the user is more used to, the user operates the second page displayed by the mobile phone through these return gestures, or operates the mobile phone, which conforms to the user's usage habits and ensures the user's experience.

[0151] S604, in response to the return gesture, the mobile phone displays the first page of the first application.

[0152] It can be understood that the second page is configured with a page marker, and the mobile phone displays the first page only when the return gesture is received when displaying the second page with the page marker, for example, as shown in (a) of FIG. 9, when the application A displays the page A1 and pulls up the page B3 of the application B, the mobile phone displays the page B3 configured with the page marker, and receives the return gesture, thereby displaying the page A1 of the application A. If the mobile phone receives the return gesture when displaying a page without a page marker, the page return within the application is performed, that is, the previous page of the page in the main task stack is displayed, or the page is placed in the background of the mobile phone, and the desktop of the mobile phone is displayed, for example, as shown in (b) of FIG. 9, when the mobile phone displays the page B2 of the application B, the return gesture is received, thereby displaying the page B1 of the application B.

[0153] In S604, the mobile phone can present the page jump effect of directly jumping back to the page of the first application by the second application for the user.

[0154] In the above-mentioned solution of S601-S604, after the second page is pulled up, the mobile phone can save the second page with the page marker in the main task stack of the second application, and then the mobile phone displays the second page with the page marker, and returns to the first page of the first application in response to the return gesture, thereby realizing the page jump between applications. Such page jump is directly realized across applications, and if there are other pages in the main task stack of the second application before the second page, it is also unnecessary to return to the page jump one by one in the main task stack, thereby saving the time of page jump between applications and improving the efficiency of page jump.

[0155] In addition, in the above-mentioned solution, the pulled-up page of the second application is still saved in the main task stack of the second application, which is also convenient for the second application to manage the page. The user can use the commonly used return gesture to realize the page jump between applications according to the usual use habit, which can ensure the user experience, and the user can use one hand to operate on the screen to control the page jump, so that the user's operation is more convenient.

[0156] In some examples, the above-mentioned second application can include multiple pages, and after the second application is pulled up and displays the second page by the first application, the user can continue to operate on the second page, so that the second application receives the page jump event, thereby the mobile phone displays some other pages of the second application, for example, a third page, and the user can continue to browse some other pages of the second application. In this case, the mobile phone will continue to add some other pages of the second application after the second page in the main task stack of the second application. Then, if the mobile phone receives the return gesture when displaying some other pages of the second application, the page return jump within the second application is realized.

[0157] For example, as shown in (a) of FIG. 10, the main task stack of the application B includes the page B1 and the page B2, the page B3 of the application B is pulled up by the application A, the phone adds the page B3 to the main task stack (the page B3 is configured with a page marker), and the phone displays the page B3 of the application B. If the application B receives a page jump event, the phone displays the page B4 of the application B corresponding to the page jump event, wherein the page jump event is used to indicate that the displayed page B3 is jumped to the page B4. After the page B4 is jumped, the phone can add the page B4 to the main task stack, and the page B4 is stacked after the page B3.

[0158] Then, as shown in (b) of FIG. 10, the phone receives a back gesture on the displayed page B4, and displays the page B3 in response to the back gesture. The page B3 is not configured with a page marker, so the phone can determine that the page B3 is not pulled up by other applications, and thus the phone does not perform page jump between applications, but displays the page B3 before the page B4 according to the structure characteristics of the main task stack. Then, the phone receives a back gesture on the displayed page B3, and displays the page A1 of the application A in response to the back gesture.

[0159] The above-mentioned page jump event can be automatically triggered by the second application, or triggered by the second application after receiving a user operation. For example, the phone displays a second page, and the user performs a finger upward sliding operation on the screen of the phone, and then the second application receives a page jump event. For another example, the phone displays a second page, and the user clicks a "next page" control on the second page, and then the second application receives a page jump event. For another example, the phone displays a second page, and the user clicks a title, content or link on the second page, and then the second application receives a page jump event.

[0160] In the above examples, if the phone receives a back gesture on the displayed second page which is not configured with a page marker in the second application, the phone first performs page jump in the main task stack, jumps the displayed page to the page before the page in the main task stack, to realize page jump in the second application. After the phone displays the second page, if a back gesture is received again, the first page of the first application is directly displayed. In this way, direct page jump between applications can also be realized, thereby saving time and improving the efficiency of page jump.

[0161] In some embodiments, the above-mentioned page marker can also not be pre-configured, but configured by the second application after the second page of the second application is pulled up. In this case, the electronic device displays the second page of the second application in response to the operation of the first application pulling up the second page of the second application, then receives a return desktop operation on the displayed second page, cancels the page marker of the second page, and displays the desktop.

[0162] In some embodiments, the electronic device receives an operation of returning to the desktop on the displayed second page, indicating that the call chain between the second application and the first application is disconnected, i.e., the call relationship between the second page and the first page of the first application no longer exists, and the call chain is disconnected, and the page marker of the second page does not need to exist, so that the electronic device can cancel the page marker of the second page.

[0163] In some embodiments, referring to FIG. 11, the method of inter-application page jump described above can further include steps S1101-S1104.

[0164] S1101, the mobile phone displays a first page of a first application.

[0165] The first application and the first page can refer to the content in the foregoing embodiment S601, which will not be repeated here.

[0166] S1102, the mobile phone displays a second page of a second application in response to an operation of the first application pulling up the second page of the second application.

[0167] The second application and the second page can refer to the content in the foregoing embodiment S602, which will not be repeated here. In S1102, the mobile phone can present the user with a page jump effect between applications jumped from the first page to the second page.

[0168] In some examples, in addition to the main task stack of the second application, the mobile phone can also create a temporary task stack for the second application and save the second page in the temporary task stack. It can be understood that the second page is the first page stacked in the temporary task stack.

[0169] In some examples, before creating the temporary task stack of the second application, the mobile phone needs to obtain a pull-up type of the second application or the second page being pulled up. The pull-up type can indicate whether the second application or the second page is pulled up by the mobile phone desktop or by other applications. If the mobile phone determines that the second application or the second page is pulled up by other applications, the mobile phone will create a temporary task stack and add the second page to the temporary task stack; and if the mobile phone determines that the second application or the second page is pulled up by the desktop, the mobile phone will add the second page to the main task stack of the second application.

[0170] For example, after the second page is pulled up, the running management service can obtain pull-up side information, such as the mobile phone desktop or the application, and then determine the pull-up type according to the pull-up side information. When the pull-up type indicates that the second page is pulled up by other applications, the running management service will create a temporary task stack of the second application.

[0171] In some examples, the phone can further acquire, from the first application, parameter information used for indicating the second page, and send the parameter information to the second application, so that the second application determines the second page according to the parameter information, and the phone displays the second page. In this way, when responding to the operation of pulling up the page of the second application by the first application, the phone can more accurately determine the page of the second application to be pulled up and displayed through the parameter information sent by the first application, thereby bringing better user experience.

[0172] S1103. The phone receives a return gesture on the displayed second page.

[0173] The return gesture can refer to the content in the foregoing embodiment S603, which will not be described here again. Since these return gestures are the return gestures that are commonly used by users or the return gestures that are more accustomed to by users, the user operates the second page displayed by the phone or operates the phone through these return gestures, which conforms to the use habit of the user and guarantees the use experience of the user.

[0174] It can be understood that since the task stack is a first-in-last-out data structure, and the second page is the first-stacked page in the temporary task stack, when the phone displays the second page, the temporary task stack can only include the second page. Therefore, the foregoing S603 can also be regarded as that the phone receives a return gesture when displaying the first-stacked page in the temporary task stack.

[0175] S1104. The phone displays the first page of the first application in response to the return gesture.

[0176] It can be understood that the second page is the first-stacked page in the temporary task stack, and the phone displays the first page only when the first-stacked second page in the temporary task stack is displayed and a return gesture is received. For example, referring to (a) in FIG. 12, when the phone displays the first-stacked page B3 in the temporary task stack of the application B, a return gesture is received, and thus the page A1 of the application A is displayed. If the phone receives a return gesture when displaying other pages in the temporary task stack, the page return in the application is performed, that is, the previous page of the page in the temporary task stack is displayed. For example, referring to (b) in FIG. 12, when the phone displays the page B4 in the temporary task stack of the application B, a return gesture is received, and thus the page B3 of the application B is displayed.

[0177] In S1104, the phone can present the page jump effect of directly jumping back to the page of the first application by the second application to the user.

[0178] It can be understood that the temporary task stack stores the page pulled up by other applications in the second application and other pages opened after the page in the second application. The main task stack stores the page pulled up by the desktop in the second application or the page opened in the application.

[0179] In some examples, after the mobile phone jumps back to display the first page of the first application, it is indicated that the pulling task of the second page has been completed or that the call chain between the first application and the second application is disconnected. In this case, there is no page in the temporary task stack of the second application, and the temporary task stack of the second application can be destroyed. After the page of the second application is pulled up again by the first application or other applications, the mobile phone re-creates the temporary task stack for the second application.

[0180] In some examples, after the second page is pulled up, the second application is placed in the foreground of the mobile phone, indicating that the call chain between the first application and the second application exists. After the second application is placed in the background of the mobile phone, it can be indicated that the call chain between the first application and the second application is disconnected. In this case, the temporary task stack of the second application can be destroyed. After the page of the second application is pulled up again by the first application or other applications, the mobile phone re-creates the temporary task stack for the second application.

[0181] The temporary task stack of the above application does not affect the main task stack of the application. After the call chain between the first application and the second application is disconnected, the temporary task stack is destroyed, and the main task stack of the second application still exists. When the user places the second application in the foreground of the mobile phone again, the page opened in the second application is added to the main task stack of the second application.

[0182] In some examples, when the temporary task stack of the second application is destroyed, if the temporary task stack of the second application still stores at least one page, the at least one page is stored in the main task stack of the second application, so as to ensure that the at least one page that has been opened in the second application is not destroyed. In this way, when the user uses the second application again, the last page browsed before can still be viewed, thereby ensuring the user experience.

[0183] For example, the second application has saved the page B1 and the page B2 in the main task stack, and has saved the page B3, the page B4 and the page B5 in the temporary task stack. When the temporary task stack is destroyed, the phone saves the page B3, the page B4 and the page B5 in the main task stack, so that the main task stack includes the page B1, the page B2, the page B3, the page B4 and the page B5 in turn. After the user places the second application in the foreground of the phone again, the displayed page of the second application is the page B5. The user makes a return gesture on the page B5, and the phone can jump to display the page B4. The user makes a return gesture on the page B4, and the phone can jump to display the page B3. The user makes a return gesture on the page B3, and the phone can jump to display the page B2.

[0184] In the above scheme of S1101-S1104, after the second page is pulled up, the phone saves the second page in the temporary task stack of the second application. The phone returns to the first page of the first application in response to the return gesture only when the first-in-stack second page (or the page at the bottom of the temporary task stack) in the temporary task stack is displayed, so as to realize the page jump between applications. Such page jump is directly realized across applications. If the main task stack of the second application has other pages before the second page, it is not necessary to return page by page in the main task stack, so that the time of page jump between applications is saved, and the efficiency of page jump is improved.

[0185] In addition, in the above scheme, the developer of the application does not need to configure the page mark for the page that can be pulled up. The user can use the common return gesture to realize the page jump between applications according to the usual use habit, so as to ensure the use experience of the user. In addition, the user can operate on the screen with one hand to control the page jump, so that the operation of the user is more convenient.

[0186] In some examples, the above second application can include multiple pages. After the second application is pulled up and the second page is displayed by the first application, the user can continue to operate on the second page, so that the second application receives the page jump event, and the phone displays some other pages of the second application. In this case, the phone continues to add some other pages of the second application to the temporary task stack of the second application after the second page. Then, if the phone receives a return gesture on the some other pages of the second application, the page return jump in the second application is realized.

[0187] For example, after displaying the second page, if the second application receives a page jump event, the mobile phone displays a third page of the second application corresponding to the page jump event, where the page jump event is used to indicate that the second page to be displayed is jumped to the third page. After the third page is jumped, the mobile phone can add the third page to the temporary task stack of the second application, and the third page is stacked after the second page. Subsequently, the mobile phone receives a back gesture on the displayed third page, and in response to the back gesture, the second page is displayed. Wherein the third page is not the first page stacked in the temporary task stack (or is not the page at the bottom of the temporary task stack), so the mobile phone can determine that the third page is not pulled up by other applications, and the mobile phone does not perform page jump between applications, but displays the second page before the third page according to the structure characteristics of the temporary task stack. Subsequently, the mobile phone receives a back gesture on the displayed second page, and in response to the back gesture, the first page of the first application is displayed.

[0188] The above page jump event can refer to the content in the foregoing embodiments, which will not be described here.

[0189] In the above example, if the mobile phone receives a back gesture when displaying a page in the temporary task stack of the second application that is not the first page stacked, the mobile phone will first perform page jump in the temporary task stack to jump the displayed page to the page before the page in the temporary task stack, to realize page jump within the second application. After the mobile phone displays the second page, if a back gesture is received again, the first page of the first application is directly displayed. In this way, direct page jump between applications can also be realized, thereby saving time and improving the efficiency of page jump.

[0190] In some examples, the second application can also pull up the pages of other applications. After the first application pulls up the page of the second application, the second application pulls up other applications. This situation can also indicate that the call chain between the first application and the second application is disconnected, and the temporary task stack of the second application is also destroyed. In addition, the mobile phone can also establish a temporary task stack of other applications. Subsequently, the page jump manner between the second application and other applications can refer to the page jump manner between the first application and the second application in the foregoing embodiments. Wherein the other applications can be applications other than the first application, or the other applications can include the first application.

[0191] For example, after the mobile phone displays the second page, if the second application pulls up the fourth page of the third application, the mobile phone displays the fourth page, destroys the temporary task stack of the second application, and adds the fourth page to the temporary task stack of the third application, where the fourth page is the first-in stack page in the temporary task stack of the third application. Then, the mobile phone receives a back gesture on the displayed fourth page, and in response to the back gesture, displays the second page of the second application. Thus, the page jump between applications is realized.

[0192] In the above example, the second application can also pull up the page of the third application. In this case, after the fourth page of the third application is pulled up, the fourth page is saved in the temporary task stack of the third application, and the temporary task stack of the second application is destroyed. The mobile phone will only return to the second page of the second application in response to the back gesture when the first-in stack fourth page is displayed in the temporary task stack, thereby realizing the page jump between applications. Such page jump is directly realized across applications. If there are other pages in the main task stack of the second application before the second page, it is not necessary to perform page jump return layer by layer in the main task stack, thereby saving the time of page jump between applications and improving the efficiency of page jump.

[0193] In some other embodiments, the above method can also realize the jump between miniprograms in an application, the jump between a miniprogram in an application and a miniprogram in another application, and the like. The developer of a miniprogram can configure a page marker for a miniprogram page, or the mobile phone can create a temporary task stack for a miniprogram, and more specific implementation manners can refer to the content in the foregoing embodiments, which will not be described here.

[0194] In the above embodiments, the method for realizing the page jump between applications in the embodiments of the present application is taken as an example to be described. In some other embodiments, a tablet computer, a personal computer, a wearable device, a smart home device, a vehicle device, and the like can also realize the above method for realizing the page jump between applications, and the specific implementation manners can refer to the content in the foregoing embodiments, which will not be described here.

[0195] The embodiments of the present application also provide an electronic device, as shown in FIG. 13, which can include one or more processors 1301, a memory 1302, and a communication interface 1303.

[0196] The memory 1302 and the communication interface 1303 are coupled with the processor 1301. For example, the memory 1302 and the communication interface 1303 can be coupled together with the processor 1301 through a bus 1304.

[0197] The communication interface 1303 is configured to perform data transmission with other devices. The memory 1302 stores computer program code. The computer program code includes computer instructions, which, when executed by the processor 1301, cause the electronic device to perform the method for inter-application page jump in the embodiments of the present application.

[0198] The processor 1301 can be a processor or a controller, for example, a CPU, a general-purpose processor, a Digital Signal Processor (DSP), an Application-Specific Integrated Circuit (ASIC), a Field Programmable Gate Array (FPGA) or other programmable logic device, a transistor logic device, a hardware component, or any combination thereof. The processor can implement or execute the various exemplary logical blocks, modules and circuits described in connection with the present disclosure. The processor can also be a combination of computing functions, such as a combination of one or more microprocessors, a combination of a DSP and a microprocessor, and the like.

[0199] The bus 1304 can be a Peripheral Component Interconnect (PCI) bus or an Extended Industry Standard Architecture (EISA) bus, etc. The bus 1304 can be divided into an address bus, a data bus, a control bus, etc. For ease of representation, only one thick line is shown in FIG. 13, but it does not mean that there is only one bus or only one type of bus.

[0200] The embodiments of the present application also provide a computer-readable storage medium, which includes computer instructions, when the computer instructions are run on an electronic device, the electronic device performs the related method steps in the above method embodiments.

[0201] The embodiments of the present application also provide a computer program product, when the computer program product is run on a computer, the computer performs the related method steps in the above method embodiments.

[0202] The electronic device, the computer-readable storage medium or the computer program product provided in the present application are used to perform the corresponding methods provided above, and thus the beneficial effects achieved thereby can refer to the beneficial effects in the corresponding methods provided above, which will not be repeated here.

[0203] Through the description of the above embodiments, those skilled in the art can clearly understand that, for the convenience and brevity of description, only the division of the above functional modules is exemplified, and in actual application, the above functions can be completed by different functional modules according to needs, that is, the internal structure of the device is divided into different functional modules to complete all or part of the functions described above.

[0204] In several embodiments provided in the present application, it should be understood that the disclosed device and method can be implemented in other ways. For example, the device embodiments described above are only illustrative, for example, the division of the modules or units is only a logical function division, and actual implementation can have another division manner, for example, a plurality of units or components can be combined or integrated into another device, or some features can be ignored or not executed. In addition, the coupling or direct coupling or communication connection between the displayed or discussed units can be indirect coupling or communication connection through some interfaces, devices or units, which can be electrical, mechanical or other forms.

[0205] The units described as separate components can or can not be physically separated, and the components displayed as units can be one physical unit or multiple physical units, that is, can be located in one place or can be distributed to multiple different places. Part or all of the units can be selected according to actual needs to achieve the purpose of the embodiment scheme.

[0206] In addition, the functional units in each embodiment of the present application can be integrated in one processing unit, or each unit can exist physically, or two or more units can be integrated in one unit. The integrated unit can be realized in the form of hardware or in the form of a software functional unit.

[0207] The integrated unit, if realized in the form of a software functional unit and sold or used as an independent product, can be stored in a readable storage medium. Based on such understanding, the technical scheme of the embodiment of the present application essentially or the part that contributes or the whole or part of the technical scheme can be embodied in the form of a software product, which is stored in a storage medium and includes a plurality of instructions for causing an apparatus (which can be a single-chip microcomputer, a chip, etc.) or a processor to execute all or part of the steps of the method described in the embodiments of the present application. The foregoing storage medium includes: a U disk, a mobile hard disk, a read-only memory (ROM), a random access memory (RAM), a magnetic disk or an optical disk, and various program code storage media.

Claims

1. A method for inter-application page jump, applied to an electronic device, and comprising the steps of: The method comprises: displaying a first page of a first application; after an operation of pulling up a second page of a second application by the first application, displaying the second page of the second application; wherein the second page is added to a main task stack of the second application, the second page is configured with a page mark; the main task stack is used to save the opened pages in the second application; and the page mark is used to indicate that the second page is pulled up by other applications; receiving a return gesture on the displayed second page; in response to the return gesture, displaying the first page of the first application.

2. The method of claim 1, wherein, The second application comprises a plurality of pages, including the second page and a third page; after the second page of the second application is displayed, the method further comprises: after the second application receives a page jump event, displaying the third page of the second application; the page jump event is used to indicate a jump from the second page to the third page; and the third page is added to the main task stack of the second application; receiving a return gesture on the displayed third page; in response to the return gesture, displaying the second page of the second application.

3. The method according to claim 1 or 2, characterized in that, The display of the second page of the second application comprises: obtaining parameter information from the first application; the parameter information is used to indicate the second page; sending the parameter information to the second application; obtaining the second page determined by the second application according to the parameter information; displaying the second page.

4. The method according to any one of claims 1 to 3, characterized in that, The return gesture is a gesture of sliding from the screen edge to the screen middle.

5. The method according to any one of claims 1 to 4, characterized in that, The operation of pulling up the second page of the second application by the first application comprises: receiving an operation of a user on a function control of the first page; in response to the operation, displaying the second page; wherein the second page displays content associated with the first page or the function control.

6. The method according to any one of claims 1 to 5, characterized in that, The method further comprises: after an operation of pulling up the second page of the second application by the first application again, displaying the second page of the second application; receiving an operation of returning to the desktop on the displayed second page, canceling the page mark of the second page; displaying the desktop. 7.A method of inter-application page jump, applied to an electronic device, and comprising: The method comprises: displaying a first page of a first application; after an operation of pulling up a second page of a second application by the first application, displaying the second page of the second application; the second page is added to a temporary task stack of the second application; the temporary task stack of the second application is used to save at least the second page pulled up by the first page, and the second page is the first page in the temporary task stack of the second application; receiving a return gesture on the displayed second page; in response to the return gesture, displaying the first page of the first application.

8. The method of claim 7, wherein, The temporary task stack is also used to save at least one page opened in the second application after the second page is pulled up; after the second page of the second application is displayed, the method further comprises: display a third page of the second application after the second application receives a page jump event; the page jump event is used to indicate a jump from the second page to the third page; the third page is added to a temporary task stack of the second application; receive a back gesture on the displayed third page; in response to the back gesture, display the second page of the second application and remove the third page from the temporary task stack.

9. The method according to claim 7 or 8, characterized in that, the temporary task stack of the second application is destroyed after the first page of the first application is displayed; or the temporary task stack of the second application is destroyed after the second application is placed in the background.

10. The method according to any one of claims 7-9, characterized in that, after the second page of the second application is displayed, the method further comprises: display a fourth page of a third application after the second application pulls up the fourth page of the third application in response to an operation; the fourth page is added to a temporary task stack of the third application; the fourth page is the first page to be added to the temporary task stack of the third application; receive a back gesture on the displayed fourth page; in response to the back gesture, display the second page of the second application.

11. The method of claim 10, wherein, the method further comprises: destroy the temporary task stack of the second application after the second application pulls up the fourth page of the third application in response to an operation; when the temporary task stack of the second application still stores at least one page, save the at least one page to a main task stack of the second application; the main task stack is used to store the opened pages in the second application.

12. The method according to any one of claims 7-11, characterized in that, the display of the second page of the second application comprises: obtain parameter information from the first application; the parameter information is used to indicate the second page; send the parameter information to the second application; obtain the second page determined by the second application according to the parameter information; display the second page.

13. The method according to any one of claims 7 to 12, characterized in that, the operation of pulling up the second page of the second application by the first application comprises: receive an operation of a user on a function control of the first page; in response to the operation, display the second page; wherein the second page displays content associated with the first page or the function control.

14. The method according to any one of claims 7 to 13, characterized in that, the back gesture is a gesture of sliding from the edge of the screen to the middle of the screen.

15. An electronic device, comprising: include a memory and one or more processors; the memory is coupled with the processor; wherein the memory stores computer program code, the computer program code includes computer instructions, when the computer instructions are executed by the processor, make the electronic device execute the inter-application page jump method as claimed in any one of claims 1-6, or execute the inter-application page jump method as claimed in any one of claims 7-14.

16. A computer-readable storage medium, characterized in that, include computer instructions, when the computer instructions run on an electronic device, make the electronic device execute the inter-application page jump method as claimed in any one of claims 1-6, or execute the inter-application page jump method as claimed in any one of claims 7-14.

17. A computer program product, characterised in that, When the computer program product is run on a computer, it causes the computer to perform the method of inter-application page jump as claimed in any one of claims 1-6, or the method of inter-application page jump as claimed in any one of claims 7-14.

Images