Method for inter-application page jump and electronic device

Abstract

The application provides a method and an electronic device for inter-application page jump, relates to the technical field of terminals, and can realize direct jump from a pulled-up page back to a page of a page-pulling side, without experiencing layer-by-layer jump of multiple pages of the page-pulling side, so that more time is not wasted, the efficiency of page jump is improved, and the use experience of a user is improved. In the method, the electronic device displays a first page of a first application, and after responding 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 for saving opened pages in the second application, and the page marker is used for indicating that the second page is pulled up 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

Technical Field

[0001] This application relates to the field of terminal technology, and in particular to a method and electronic device for page navigation between applications. Background Technology

[0002] Currently, cross-application functionality allows one app to use the features of another. For example, when a user is buying goods using a shopping app, clicking the purchase button will launch the payment app's payment page, where the user can complete the payment. Afterwards, if the user wants to continue browsing products, they can make a back gesture on the payment page to trigger the device to redisplay the shopping app's page, thus navigating to the next page.

[0003] However, if the user has already browsed some pages in the payment app before the payment page is brought up, the device will sequentially display the history pages that the user has browsed in the payment app after the user makes a back gesture on the payment page. Only after all the history pages have been displayed will the device display the shopping app page again.

[0004] As can be seen, in the above-mentioned page redirection process, if the payment application has already browsed many pages before the payment page is launched, it will take a long time to redirect back to the shopping application page. This will not only reduce the efficiency of page redirection, but also affect the user experience. Summary of the Invention

[0005] This application provides a method and electronic device for page navigation between applications, which can directly navigate from the page that was pulled up back to the page that pulled up the application, without having to go through multiple layers of navigation between the pages that were pulled up, thus saving time and improving the efficiency of page navigation and enhancing the user experience.

[0006] To achieve the above objectives, the embodiments of this application adopt the following technical solutions:

[0007] Firstly, a method for page navigation between applications is provided. Taking an electronic device as an example, the electronic device displays a first page of a first application. Upon receiving an operation from the first application to launch a second page of a second application, the electronic device displays the second page of the second application. The second page is added to the main task stack of the second application and is configured with a page marker. The main task stack stores pages opened within the second application, and the page marker indicates that the second page has been launched by another application. The electronic device receives a back gesture on the displayed second page and, in response, displays the first page of the first application.

[0008] In the above method, after the second page is displayed, the electronic device can save the second page with the page marker in the main task stack of the second application. Then, when the electronic device displays the second page with the page marker, it will respond to a back gesture and return to the first page of the first application, thus achieving page navigation between applications. This page navigation is implemented directly across applications. If there are other pages in the main task stack of the second application before the second page, there is no need to navigate back layer by layer within the main task stack, thereby saving time and improving the efficiency of page navigation between applications.

[0009] In one possible implementation of the first aspect, the second application includes multiple pages, including a second page and a third page. After displaying the second page of the second application, if the second application receives a page jump event, the electronic device displays the third page of the second application upon receiving the page jump event, wherein 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.

[0010] In the above implementation, if the electronic device receives a back gesture while displaying a page without a page marker in the second application, it will first execute a page jump in the main task stack, redirecting the displayed page to the page preceding that page in the main task stack. This achieves page jump within the second application. After the electronic device displays the second page, if it receives another back gesture, it will directly display the first page of the first application. This also enables direct page jumps between applications, saving time and improving page jump efficiency.

[0011] In one possible implementation of the first aspect, the electronic device obtains parameter information from a first application, wherein the parameter information is used to indicate a second page. The electronic device sends the parameter information to a second application and obtains the second page determined by the second application based on the parameter information; subsequently, the electronic device displays the second page.

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

[0013] In one possible implementation of the first aspect, the return gesture is a swipe gesture from the edge of the screen to the center of the screen, such as swiping a finger from the left edge of the screen to the right or swiping a finger from the right edge of the screen to the left.

[0014] In the above implementation, these back gestures are all commonly used or familiar to users. Therefore, users can use these back gestures to operate the second page displayed on the electronic device or to operate the electronic device itself, which is in line with user habits and ensures a good user experience.

[0015] In one possible implementation of the first aspect, the electronic device responds to an operation of the first application to launch a second page of the second application, including: the electronic device receiving an operation from a user on a function control of the first page, and responding to the operation to display a second page of the second application; wherein the second page displays content associated with the first page or the function control.

[0016] In the above implementation, users can trigger page navigation between applications through functional controls on the first page of the first application. For example, the functional controls on the first page can provide functions such as payment and login. User operations on the functional controls can trigger the first application to launch the second page of the second application, and the second page can display payment information, login information, etc. provided by the second application.

[0017] In one possible implementation of the first aspect, after the electronic device responds to an operation whereby the first application launches a second page of the second application again, it displays the second page of the second application. Subsequently, the electronic device receives an operation to return to the desktop on the displayed second page, cancels the page marker on the second page, and displays the desktop.

[0018] It is understandable that the aforementioned page markers can be pre-configured by the application developer for the application pages before the application is released, or they can be configured automatically by the application after the application pages are launched. When the electronic device receives a return-to-desktop operation on the displayed second page, it indicates that the call chain between the second application and the first application is broken. That is, the call relationship between the second page and the first page of the first application no longer exists. If the page markers are configured automatically by the application after the application pages are launched, then the call chain is broken, and the page markers for the second page do not need to exist. Therefore, the electronic device can cancel the page markers for the second page.

[0019] Secondly, a method for page navigation between applications is provided. Taking an electronic device as an example, the electronic device displays the first page of a first application. After responding to an operation where the first application launches a second page of a second application, the electronic device displays the second page of the second application. The second page is added to the temporary task stack of the second application, which is at least used to store the second page launched from the first page. The second page is the first page pushed onto the temporary task stack of the second application. Subsequently, 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.

[0020] In the above method, after the second page is displayed, the electronic device saves it in the temporary task stack of the second application. The electronic device will only respond to the back gesture and return to the first page of the first application when displaying the second page that was first pushed onto the temporary task stack (or a page placed on the stack in the temporary task stack), thus realizing page navigation between applications. This page navigation is implemented directly across applications. If there are other pages in the main task stack of the second application before the second page, there is no need to perform page navigation back layer by layer in the main task stack, thereby saving the time of page navigation between applications and improving the efficiency of page navigation.

[0021] In one possible implementation of the second aspect, the temporary task stack is also used to store at least one page opened in the second application after the second page is launched. After displaying the second page of the second application, if the second application receives a page jump event, the electronic device displays a third page of the second application after receiving the page jump event, wherein 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. Subsequently, 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.

[0022] In the above implementation, if the electronic device receives a back gesture while displaying a page that is not the first page pushed onto the temporary task stack of the second application, the electronic device will first execute the page jump in the temporary task stack, jumping to the page that precedes the current page in the temporary task stack, thus achieving page jump within the second application. After the electronic device displays the second page, if it receives a back gesture again, it will directly display the first page of the first application. In this way, direct page jump between applications can also be achieved, thereby saving time and improving the efficiency of page jump.

[0023] In one possible implementation 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.

[0024] In the above implementation, the return of the displayed content from the second page to the first page and the second application being placed in the background both indicate that the call chain between the first and second applications is broken. The application's temporary task stack does not affect the application's main task stack. After the call chain between the first and second applications is broken, the temporary task stack is destroyed, while the second application's main task stack continues to exist. When the user brings the second application back into the foreground, the pages opened in the second application will be added to the second application's main task stack.

[0025] In one possible implementation of the second aspect, after displaying the second page of the second application, if the second application launches a fourth page of the third application, the electronic device, in response to the launch of the third application's fourth page, displays the fourth page of the third application. The fourth page is added to the temporary task stack of the third application, and is the first page pushed onto the stack. Subsequently, the electronic device receives a back gesture on the displayed fourth page and, in response to the gesture, displays the second page of the second application.

[0026] In the above implementation, the second application can also launch a page from the third application. In this case, after the fourth page of the third application is launched, it is stored in the temporary task stack of the third application. The electronic device will only respond to the back gesture and return to the second page of the second application when displaying the fourth page, which is the first page pushed into the temporary task stack, thus realizing page navigation between applications. This kind of page navigation is implemented directly across applications. If there are other pages in the main task stack of the second application before the second page, there is no need to perform page navigation back layer by layer in the main task stack, thereby saving the time of page navigation between applications and improving the efficiency of page navigation.

[0027] In one possible implementation of the second aspect, after the electronic device responds to the operation of the second application launching the fourth page of the third application, it destroys the temporary task stack of the second application; when at least one page is still stored in the temporary task stack of the second application, at least one page is saved to the main task stack of the second page; the main task stack is used to store the pages opened in the second application.

[0028] The above implementation ensures that at least one page already opened in the second application will not be destroyed. This way, when the user uses the second application again, they can still view the last page they viewed, thus guaranteeing a good user experience.

[0029] Understandably, the lifecycle of an application's main task stack is consistent with the application's lifecycle, while the application's temporary task stack only exists when the application is called by other applications and the called application is in the foreground.

[0030] In one possible implementation of the second aspect, the electronic device obtains parameter information from a first application, wherein the parameter information is used to instruct a second page. The electronic device sends the parameter information to the second application and obtains the second page determined by the second application based on the parameter information. Then, the electronic device displays the second page.

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

[0032] In one possible implementation of the second aspect, the electronic device responds to an operation by the first application to launch a second page of the second application, including: the electronic device receiving an operation by a user on a function control of the first page, and responding to the operation by displaying a second page of the second application; wherein the second page displays content associated with the first page or the function control.

[0033] In the above implementation, users can trigger page navigation between applications through functional controls on the first page of the first application. For example, the functional controls on the first page can provide functions such as payment and login. User operations on the functional controls can trigger the first application to launch the second page of the second application, and the second page can display payment information, login information, etc. provided by the second application.

[0034] In one possible implementation of the second aspect, the return gesture is a swipe gesture from the edge of the screen to the center of the screen, such as swiping a finger from the left edge of the screen to the right or swiping a finger from the right edge of the screen to the left.

[0035] These back gestures are all commonly used or familiar to users. Therefore, using these back gestures to operate the second page displayed on the electronic device or to operate the electronic device itself is in line with user habits and ensures a good user experience.

[0036] Thirdly, an electronic device is provided, including a memory and one or more processors; the memory is coupled to the processors; wherein the memory stores computer program code, the computer program code including computer instructions, which, when executed by the processor, cause the electronic device to perform the inter-application page jump method as described in the first aspect and any of its implementable embodiments, or to perform the inter-application page jump method as described in the second aspect and any of its implementable embodiments.

[0037] Fourthly, a computer-readable storage medium is provided, including computer instructions that, when executed on an electronic device, cause the electronic device to perform the inter-application page jump method as described in the first aspect and any of its possible implementations, or to perform the inter-application page jump method as described in the second aspect and any of its possible implementations.

[0038] Fifthly, a computer program product is provided that, when the computer program product is run on a computer, causes the computer to execute the method of inter-application page navigation as described in the first aspect and any of its implementable embodiments, or to execute the method of inter-application page navigation as described in the second aspect and any of its implementable embodiments.

[0039] The beneficial effects that the electronic equipment 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 can be referred to the beneficial effects that can be achieved in the first aspect and any of its implementations, or to the beneficial effects that can be achieved in the second aspect and any of its implementations, and will not be repeated here. Attached Figure Description

[0040] Figure 1 A schematic diagram of the task stack of the application provided in an embodiment of this application is shown;

[0041] Figure 2 A schematic diagram of the return control provided in an embodiment of this application is shown;

[0042] Figure 3 A schematic diagram of the structure of the electronic device provided in the embodiments of this application is shown. Figure 1 ;

[0043] Figure 4 A schematic diagram of the structure of the electronic device provided in the embodiments of this application is shown. Figure 2 ;

[0044] Figure 5 This illustration shows a schematic diagram of the processing procedure for the operation management service in an electronic device provided in an embodiment of this application;

[0045] Figure 6 This application provides a flowchart illustrating the method for inter-application page navigation according to an embodiment. Figure 1 ;

[0046] Figure 7 This illustration shows a schematic diagram of inter-application page navigation provided in an embodiment of this application;

[0047] Figure 8 A schematic diagram of the return gesture provided in an embodiment of this application is shown;

[0048] Figure 9 This illustration shows a page navigation method provided in an embodiment of this application. Figure 1 ;

[0049] Figure 10 This illustration shows a page navigation method provided in an embodiment of this application. Figure 2 ;

[0050] Figure 11This application provides a flowchart illustrating the method for inter-application page navigation according to an embodiment. Figure 2 ;

[0051] Figure 12 This illustration shows a page navigation method provided in an embodiment of this application. Figure 3 ;

[0052] Figure 13 A schematic diagram of the structure of the electronic device provided in the embodiments of this application is shown. Figure 3 . Detailed Implementation

[0053] The technical solutions of the embodiments of this application will be described below with reference to the accompanying drawings. In the description of this application, unless otherwise stated, " / " indicates that the objects before and after are in an "or" relationship. For example, A / B can represent A or B. "And / or" in this application is merely a description of the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can represent: A alone, A and B simultaneously, and B alone, where A and B can be singular or plural. Furthermore, in the description of this application, unless otherwise stated, "multiple" refers to two or more. "At least one of the following" or similar expressions refer to any combination of these items, including any combination of single or plural items. For example, at least one of a, b, or c can represent: a, b, c, ab, ac, bc, or abc, where a, b, and c can be single or multiple. Furthermore, to facilitate a clear description of the technical solutions in the embodiments of this application, the terms "first" and "second" are used in the embodiments of this application to distinguish identical or similar items with substantially the same function and effect. Those skilled in the art will understand that the terms "first" and "second" do not limit the quantity or execution order, and that "first" and "second" are not necessarily different. Meanwhile, in the embodiments of this application, the terms "exemplary" or "for example" are used to indicate that something is being used as an example, illustration, or description. Any embodiment or design scheme described as "exemplary" or "for example" in the embodiments of this application should not be construed as being more preferred or advantageous than other embodiments or design schemes. Specifically, the use of terms such as "exemplary" or "for example" is intended to present related concepts in a concrete manner for ease of understanding.

[0054] Furthermore, the business scenarios described in the embodiments of this application are for the purpose of more clearly illustrating the technical solutions of the embodiments of this application, and do not constitute a limitation on the technical solutions provided in the embodiments of this application. As those skilled in the art will know, with the emergence of new business scenarios, the technical solutions provided in the embodiments of this application are also applicable to similar technical problems.

[0055] Applications typically have their own task stacks to store or manage the pages opened within the application. A task stack is a Last-In-First-Out (LIFO) data structure, where the first page pushed onto the stack is placed at the bottom, and the last page pushed onto the stack is placed at the top.

[0056] Currently, cross-application support allows one application to use the functionality of another.

[0057] For example, when a user purchases an item using a shopping app, clicking the purchase button will launch the payment app's payment page, where the user can complete the payment. Once launched, the payment page is added to the payment app's task stack. Afterward, if the user wants to continue browsing products, they can perform a back gesture on the payment page to trigger the device to redisplay the shopping app's page, thus navigating to the next page.

[0058] However, if the user has already browsed some pages in the payment app before the payment page is displayed, then some pages are already stored in the task stack before the payment page is pushed onto the stack. After the user makes a back gesture on the payment page, the device will, according to the characteristics of the task stack, sequentially display the historical pages that the user has browsed in the payment app. Only after all the historical pages have been displayed will the device display the shopping app page again, thus realizing the page jump between the payment app and the shopping app.

[0059] In the aforementioned page navigation process, if the payment application has already viewed many pages before the payment page is launched, then navigating back to the shopping application page requires performing page back operations layer by layer within the payment application. This wastes a lot of time, thereby reducing the efficiency of page navigation. Furthermore, this layer-by-layer page return also affects the user experience.

[0060] In some solutions, the page of the launched application can be added to the task stack of the launching application, thereby enabling page navigation between applications. For example, see... Figure 1 As shown, when application A launches a page from application B, it only needs to add that page to application A's task stack for management, thus achieving a one-step application jump. For example, after the user finishes their operation on application B's page, they can return to application A's page using the back button or a back gesture. In this approach, because application B's page is added to application A's task stack, application B's own task stack remains independent and unaffected. However, the launched application page is not in the launched application's own task stack, which is not conducive to the launched application's management of the page.

[0061] In other solutions, a default back control or back button can be provided when the launched application page is displayed, allowing users to navigate between pages in the application by clicking the back control. For example, see... Figure 2 As shown, a control corresponding to "Shopping App" is displayed in the upper left corner of the information page, indicating that the currently displayed information page is a page launched by the shopping app. After viewing the information page, users can click the control corresponding to "Shopping App" to directly jump back to the shopping app page.

[0062] While this approach avoids adding the launched page to the application's task stack, placing the back control or button at the top of the page can be inconvenient for users with larger screens, especially when operating it with one hand. Furthermore, users are accustomed to using a global back gesture for page navigation; using this back control disrupts their usual workflow, negatively impacting the user experience.

[0063] Based on the above, this application provides a method for page navigation between applications. In this method, users can follow their daily usage habits and make a back gesture on the page that is pulled up, thereby causing the displayed page to jump back to the page that pulled up the page, thus ensuring a good user experience. Furthermore, users can also control page navigation with one hand, making the operation more convenient. In addition, this method can also realize direct navigation from the page that was pulled up back to the page that pulled up the page, without having to go through multiple layers of navigation between pages that were pulled up, thus saving time and improving the efficiency of page navigation and enhancing the user experience.

[0064] For example, taking the above method applied to an electronic device, the electronic device can display the first page of a first application. Through clicks, confirmations, or navigation on the first page, in response to the first application launching a second application, the electronic device can then display the second page of the second application. The second page is added to the main task stack of the second application and is configured with page markers. The main task stack stores pages opened within the second application; the page markers indicate pages within the second application that can be launched by other applications. Subsequently, the electronic device receives a back gesture on the displayed second page and, in response, displays the first page.

[0065] In this scheme, after the second page is pulled up, the electronic device saves the second page with the page mark in the task stack of the second application. When the electronic device displays the page with the page mark, it will respond to the back gesture and jump back to the first page of the first application, thus realizing page jump between applications.

[0066] For another example, taking the above method applied to an electronic device, the electronic device can display the first page of a first application. Through clicks, confirmations, or navigation on the first page, in response to the first application launching a second application, the electronic device can then display the second page of the second application. The second page is added to the temporary task stack of the second application, which is at least used to store the second page launched from the first page, and the second page is the first page added to the temporary task stack. Subsequently, the electronic device receives a back gesture on the displayed second page and, in response to the back gesture, displays the first page.

[0067] 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. The electronic device will only respond to the back gesture to jump back to the first page of the first application when the second page in the temporary task stack is displayed, thus realizing page jump between applications.

[0068] When the above method is applied to electronic devices, in some embodiments, see [reference needed]. Figure 3 As shown, the electronic device 100 may 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 button 190, a motor 191, an indicator 192, a camera 193, a display screen 194, and a subscriber identification module (SIM) card interface 195, etc.

[0069] It is understood that the structures illustrated in the embodiments of this application do not constitute a specific limitation on the electronic device 100. In other embodiments of this application, the electronic device 100 may include more or fewer components than illustrated, or combine some components, or split some components, or have different component arrangements.

[0070] Processor 110 may include one or more processing units ( Figure 3(Not shown in the image), for example, processor 110 may include an application processor (AP), a modem processor, a graphics processing unit (GPU), an image signal processor (ISP), a controller, memory, a video codec, a digital signal processor (DSP), a baseband processor, and / or a neural network processing unit (NPU), etc. Different processing units may be independent devices or integrated into one or more processors.

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

[0072] The processor 110 may also include a memory for storing instructions and data.

[0073] In some embodiments, processor 110 may include one or more interfaces ( Figure 3 (Not shown in the image).

[0074] Among them, the USB interface 130 is an interface that conforms to the USB standard specification, specifically it can be a Mini USB interface, MicroUSB interface, USB Type C interface, etc.

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

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

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

[0078] Antenna 1 and antenna 2 are used to transmit and receive electromagnetic wave signals. Each antenna in electronic device 100 can be used to cover one or more communication frequency bands. Different antennas can also be multiplexed to improve antenna utilization. For example, antenna 1 can be multiplexed as a diversity antenna for a wireless local area network. In some other embodiments, the antennas can be used in conjunction with tuning switches.

[0079] The mobile communication module 150 can provide wireless communication solutions, including 2G / 3G / 4G / 5G, for use on electronic devices 100.

[0080] The wireless communication module 160 can provide solutions for wireless communication applications on the electronic device 100, 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 (IR) technology, etc.

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

[0082] Electronic device 100 implements display functions through a GPU, a display screen 194, and an application processor. The GPU is a microprocessor for image processing, connecting the display screen 194 and the application processor. The GPU is used to perform mathematical and geometric calculations and for graphics rendering.

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

[0084] In some examples, display screen 194 (which may be referred to as a screen in subsequent embodiments) may display icons of applications in electronic device 100. When a user clicks an application icon, the application is launched, and display screen 194 may further display the application's page.

[0085] In some examples, when a user is using the first application, if they perform certain actions on the first application or on its page, such as clicking, confirming, or navigating, it may trigger the first application to launch a page of the second application. After that page of the second application is launched, the display screen 194 will also display that page of the second application. If the user makes a back gesture on the display screen 194 while the second application's page is displayed, the display screen 194 will also display the page of the first application again, giving the user the effect of navigating back from the second application's page to the first application's page.

[0086] Electronic device 100 can perform shooting functions through an ISP, camera 193, video codec, GPU, display 194, and application processor. The ISP is used to process data fed back by the camera 193. The camera 193 is used to capture still images or videos.

[0087] The external storage 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 storage interface 120 to perform data storage functions. For example, music, video, and other files can be saved on the external memory card.

[0088] Internal memory 121 can be used to store computer executable program code, which includes instructions. Processor 110 executes various functional applications and data processing of electronic device 100 by running the instructions stored in internal memory 121.

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

[0090] In some examples, when a user is using the first application, if the first application launches a page of the second application, the processor 110 also executes instructions stored in internal memory 121 to save that page of the second application in the task stack of the second application, and controls the screen to switch from displaying the page of the first application to displaying the page of the second application. Subsequently, the processor 110 also executes instructions stored in internal memory 121 to recognize the user's gestures on the screen and whether the page displayed on the screen has a page marker. If the user makes a back gesture and the page displayed on the screen has a page marker, the processor 110 executes instructions stored in internal memory 121 to control the screen to switch from displaying the page of the second application to displaying the page of the first application.

[0091] In some examples, when a user is using the first application, if the first application launches a page of the second application, the processor 110 also executes instructions stored in internal memory 121 to save that page of the second application in the temporary task stack of the second application, and controls the screen to jump from the page of the first application to the page of the second application. Subsequently, the processor 110 also executes instructions stored in internal memory 121 to identify the user's gesture on the screen and whether the page displayed on the screen is the page at the bottom of the temporary task stack of the second application. If the user makes a back gesture, and the page displayed on the screen is the page at the bottom of the temporary task stack of the second application, then the processor 110 executes instructions stored in internal memory 121 to control the screen to jump from the page of the second application to the page of the first application.

[0092] The audio module 170 is used to convert digital audio information into analog audio signals for output, and also to convert analog audio input into digital audio signals. Buttons 190 include a power button, volume buttons, etc. A motor 191 can generate vibration feedback. An indicator 192 can be an indicator light, used to indicate charging status, battery level changes, messages, missed calls, notifications, etc. A SIM card interface 195 is used to connect a SIM card.

[0093] When implementing the application page jump method provided in this application embodiment using the above-described electronic device, the user can follow their daily usage habits and make a back gesture on the pulled-up page. The electronic device can jump back from the displayed pulled-up page to the pull-up page, thus ensuring the user's user experience. Furthermore, the user can also control the page jump with one hand, making the operation more convenient. In addition, the above method can realize a direct jump from the pulled-up page back to the pull-up page without going through multiple layers of pull-up pages, saving time and improving the efficiency of page jump and enhancing the user experience.

[0094] In some embodiments, the software system of electronic device 100 may adopt a layered architecture, event-driven architecture, microkernel architecture, microservice architecture, or cloud architecture. This application embodiment uses a layered mobile operating system as an example to exemplify the software structure of electronic device 100.

[0095] Among them, see Figure 4 As shown, the layered architecture of the electronic device 100 divides the software into several layers, each with a clear role and division of labor. Layers communicate with each other through software interfaces. In some embodiments, the mobile operating system is divided into four layers, from top to bottom: the application layer, the application framework layer, the system service layer, and the kernel layer.

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

[0097] like Figure 4 As shown, the application package can include applications such as shopping, payment, camera, calendar, calling, gallery, map, navigation, Bluetooth, music, video, and SMS.

[0098] The application framework layer provides application programming interfaces (APIs) and a programming framework for applications in the application layer. The application framework layer includes some predefined functions.

[0099] like Figure 4 As shown, the application framework layer may include a window manager, content provider, view system, phone manager, resource manager, notification manager, etc.

[0100] The window manager is used to manage windowed applications. It can retrieve screen size, determine the presence of a status bar, lock the screen, and capture screenshots, among other things.

[0101] Content providers store and retrieve data, making that data accessible to applications. This data may include videos, images, audio, made and received phone calls, browsing history and bookmarks, phone books, etc.

[0102] A view system includes visual controls, such as controls for displaying text and controls for displaying images. View systems can be used to build applications. A display interface can consist of one or more views. For example, a display interface including a text notification icon could include views for displaying text and views for displaying images.

[0103] The phone manager is used to provide communication functions for electronic device 100.

[0104] The file explorer provides applications with various resources, such as localized strings, icons, images, layout files, video files, and more.

[0105] The notification manager allows applications to display notifications in the status bar. These notifications can be used to convey informational messages and can disappear automatically after a short pause, requiring no user interaction. The notification manager can also display notifications as icons or scrollbar text in the top status bar, such as notifications from background applications, or as dialog boxes on the screen.

[0106] In some examples, the application framework layer may also include a routing framework. The routing framework enables navigation between pages within the application; for example, it can navigate from page 1 of the first application to page 2 of the first application.

[0107] In some examples, the routing framework can also provide multiple interfaces, each enabling in-application page navigation across different operating systems. Furthermore, each interface can provide functionality for tagging application pages.

[0108] Application developers can configure page tags for application pages through the above interface. Page tags are used to indicate that the application page can be launched by other applications.

[0109] Alternatively, the application can call the above interface to configure page tags for the page that has been launched by another application.

[0110] When the screen is currently displaying an application page with page markers and a back gesture is received, the electronic device 100 can switch between application pages. In other words, it can switch the currently displayed application page with page markers to a page of another application that launches that page.

[0111] The system service layer can include multiple functional modules. For example: surface manager, media libraries, 3D graphics processing libraries (e.g., OpenGL ES), 2D graphics engines (e.g., SGL, Vulkan), etc.

[0112] The Surface Manager is used to manage the display subsystem and provides the blending of 2D and 3D layers for multiple applications.

[0113] The media library supports playback and recording of various common audio and video formats, as well as still image files. It supports multiple audio and video encoding formats, such as MPEG4, H.264, MP3, AAC, and AMR.

[0114] The 3D graphics processing library is used to implement 3D graphics drawing, image rendering, compositing, and layer processing.

[0115] A 2D graphics engine is a graphics engine for 2D drawing.

[0116] In some examples, the system service layer may also include a runtime management service. The runtime management service manages the application's task stack and enables page navigation between the applications. Specifically, when one application launches another, the runtime management service records the launch relationship between the applications (or application pages).

[0117] For example, see Figure 5As shown in (a), when a user is using application A, if application A launches page B3 of application B, the runtime management service can add page B3 to the task stack of application B (pages B1 and B2 of application B already exist in the task stack), and instruct the screen to display page B3. Since page B3 was launched by application A, page B3 has a pre-configured page tag. After the user makes a back gesture on the screen displaying page B3, the runtime management service determines that page B3 has a page tag, thus determining that page B3 was launched by another application. Based on the launch relationship, the runtime management service then determines that page B3 was launched by application A, thereby instructing the screen to display the page of application A, realizing page jump between application A and application B without going through pages B2 and B1 in the task stack.

[0118] For example, see Figure 5 As shown in (b), when a user is using application A, if application A launches page B3 of application B, the runtime management service can add page B3 to application B's temporary task stack and instruct the screen to display page B3. Application B's temporary task stack does not affect application B's task stack (i.e., the main task stack). The temporary task stack stores pages launched by other applications and subsequent pages opened by application B, while the main task stack stores pages launched from the desktop or navigated within the application. After the user makes a back gesture on the screen displaying page B3, if page B3 is the page at the bottom of the temporary task stack, the runtime management service determines that page B3 was launched by another application. Based on the launch relationship, the runtime management service then determines that page B3 was launched by application A, thus instructing the screen to display application A's page, achieving page navigation between application A and application B.

[0119] The kernel layer is the layer between hardware and software. The kernel layer contains at least the display driver, camera driver, audio driver, and sensor driver.

[0120] When implementing the application page jump method provided in this application embodiment using the above-described electronic device, the user can follow their daily usage habits and make a back gesture on the pulled-up page. The electronic device can jump back from the displayed pulled-up page to the pull-up page, thus ensuring the user's user experience. Furthermore, the user can also control the page jump with one hand, making the operation more convenient. In addition, the above method can realize a direct jump from the pulled-up page back to the pull-up page without going through multiple layers of pull-up pages, saving time and improving the efficiency of page jump and enhancing the user experience.

[0121] The aforementioned electronic devices can be mobile phones, tablets, personal computers, wearable devices (such as smartwatches, smart bracelets, etc.), smart home devices (such as televisions, etc.), vehicle-mounted systems (such as in-vehicle terminals), and other terminal devices.

[0122] The following examples use a mobile phone as an example to illustrate the method of page navigation between applications.

[0123] In some embodiments, before an application is listed on an app store, the application developer will configure the page tags of the application pages by calling the interface provided by the operating system or the routing framework of the operating system to which the application is compatible.

[0124] For example, The provided interfaces are StartActivity, The provided interfaces are pushViewController and HarmonyOS. The provided interface is pushPath.

[0125] The page tags mentioned above are used to indicate that an application page is launched by another application, or to indicate that an application page can be launched by another application. In other words, within an application, pages launched by other applications are configured with page tags.

[0126] In some embodiments, after the application is listed and installed on the phone, see [link to relevant documentation]. Figure 6 As shown, the method for page navigation between applications can include the following steps S601-S604.

[0127] S601, the phone displays the first page of the first application.

[0128] Understandably, the first application refers to the app on the phone that can launch other applications.

[0129] In some examples, the first page can be any page in the first application, and when a user performs an action on the first page, it can trigger the first application to launch pages of other applications.

[0130] For example, when the first application is a shopping application, the first page can be an order confirmation page. When the user performs a payment operation on the order confirmation page, such as clicking the function control that indicates payment, the shopping application can trigger the payment application's payment page.

[0131] For example, when the first application is a shopping application, the first page can be a login page. On the login page, the user performs the operation of logging in using the account of the chat application, such as clicking the function control that indicates login, which can trigger the shopping application to launch the authorization page of the chat application.

[0132] For another example, when the first application is a video application, the first page can be a live page with a link to a certain product. When a user clicks on the product link on the live page, the video application can trigger the product page of the shopping application to be launched.

[0133] S602: After the mobile phone responds to the operation of the first application to launch the second page of the second application, it displays the second page of the second application.

[0134] Understandably, the second application refers to the application that was launched on the phone by another application.

[0135] In some examples, the second page is a page within a second application that can be launched by other applications. In S602, the phone can present a page transition effect between applications that navigate from the first page to the second page.

[0136] For example, the first application is a shopping application, the second application is a payment application, the first page is the order confirmation page, and the second page is the payment page, see [link to relevant documentation]. Figure 7 As shown in (a), after the payment page is launched by the shopping application, the page displayed on the phone jumps from the order confirmation page to the payment page, which displays payment information such as price, account, and password prompts.

[0137] 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. See [link / reference]. Figure 7 As shown in (b), after the authorization page is launched by the shopping application, the page displayed on the mobile phone jumps from the login page to the authorization page, which displays login information such as prompts for authorization.

[0138] For another example, the first application is a video application, the second application is a shopping application, the first page is a live streaming page, and the second page is a product page, see [link to example]. Figure 7 As shown in (c), after the product page is launched by the video application, the page displayed on the mobile phone jumps from the live broadcast page to the product page.

[0139] In some examples, the first application and the second application each have their own main task stack, which is used to store the pages opened in the first application or the second application.

[0140] For example, when a user clicks on an app icon on the phone's home screen, the app is launched from the home screen, meaning the app is opened. After the app is opened, the phone displays the app's home page, and the phone also adds this page to the app's main task stack. Subsequently, if the user continues to click on controls or make gestures on the app's home page, causing other pages of the app to open, the phone will also add these other pages to the app's main task stack.

[0141] When the second page of the second application is launched by the first application, the phone can add the second page to the main task stack corresponding to the second application.

[0142] In some examples, since pages in the second application that can be launched by other applications are pre-configured with page tags, the second pages saved in the main task stack are also configured with page tags.

[0143] In some examples, the phone can also obtain parameter information from the first application to indicate the second page, and send the parameter information to the second application. The second application determines the second page based on the parameter information, and then the phone displays the second page.

[0144] For example, after a user performs an action on page A1 of application A, application A is triggered to launch page B3 of application B. In this case, application A sends the parameter information indicating page B3 to the phone's operation management service. The operation management service then sends the parameter information to application B, which determines the page B3 that needs to be launched based on the parameter information. The operation management service then instructs the phone to display page B3.

[0145] Alternatively, after receiving the parameter information, the operation management service can determine the page B3 of the application B that needs to be launched based on the parameter information, and then instruct the mobile phone to display page B3.

[0146] In this way, when responding to the first application launching the second application's page, the phone can more accurately determine the page of the second application to launch and display based on the parameter information sent by the first application, thus providing a better user experience.

[0147] S603: The phone receives a back gesture on the second page with page markers displayed.

[0148] In some examples, the aforementioned back gesture can be a back gesture that users are accustomed to using when operating their phones, also known as a global back gesture. The back gesture can be a swipe from the edge of the screen towards the center, for example... Figure 8 The gesture shown in (a) is a finger swiping from the left edge of the screen to the right, or, for example... Figure 8 The gesture shown in (b) is a finger swiping from the right edge of the screen to the left.

[0149] Since these back gestures are commonly used or familiar to users, using them to operate the second page displayed on the phone or to operate the phone itself aligns with user habits and ensures a good user experience.

[0150] S604: In response to a back gesture, the phone displays the first page of the first application.

[0151] Understandably, the second page has page markers. When the phone is displaying the second page with page markers, it will only display the first page if a back gesture is received. See, for example... Figure 9 As shown in (a), when application A displays page A1, it launches page B3 of application B. When the phone displays page B3 with page tags, it receives a back gesture, thus displaying page A1 of application A. However, if the phone receives a back gesture while displaying a page without page tags, it will perform an in-app page return, that is, jump to display the previous page in the main task stack, or place the page in the background and display the phone's home screen, for example, see [reference 1]. Figure 9 As shown in (b), when the phone displays page B2 of application B, it receives a back gesture, thereby displaying page B1 of application B.

[0152] In S604, the phone can present a page jump effect that allows users to jump directly from the second application back to the first application.

[0153] In the solutions S601-S604 described above, after the second page is launched, the phone can save the second page with the page marker in the main task stack of the second application. Then, when the phone displays the second page with the page marker, it will respond to a back gesture to return to the first page of the first application, thus achieving page navigation between applications. This page navigation is implemented directly across applications. If there are other pages in the main task stack of the second application before the second page, there is no need to perform page navigation layer by layer in the main task stack, thereby saving time and improving the efficiency of page navigation between applications.

[0154] Furthermore, in the above solution, the page of the launched second application remains in the main task stack of the second application, which also facilitates the second application's management of the page. Users can use common back gestures to switch between applications based on their usual usage habits, thus ensuring a good user experience. In addition, users can operate with one hand on the screen to control page switching, making the operation more convenient.

[0155] In some examples, the second application may include multiple pages. After the first application launches and displays the second page, the user can continue to operate on the second page, causing the second application to receive a page navigation event. This allows the phone to display other pages within the second application, such as a third page, which the user can then browse. In this case, the phone continues to add other pages of the second application after the second page in the main task stack. Subsequently, if the phone receives a back gesture while displaying other pages of the second application, a page navigation within the second application is achieved.

[0156] For example, see Figure 10 As shown in (a), the main task stack of application B includes pages B1 and B2. After application A launches page B3 of application B, the phone adds page B3 to the main task stack (page B3 has a page tag configured), and the phone displays page B3 of application B. If application B receives a page jump event, the phone displays page B4 of application B corresponding to the page jump event. The page jump event is used to indicate that the displayed page B3 will jump to page B4. After page B4 is jumped, the phone can add page B4 to the aforementioned main task stack, and page B4 is pushed onto the stack after page B3.

[0157] See afterward. Figure 10 As shown in (b), the phone receives a back gesture on the displayed page B4 and, in response, displays page B3. Since page B3 has no page marker configured, the phone can determine that page B3 was not launched by another application. Therefore, the phone does not perform a page jump between applications, but instead displays page B3, which precedes page B4, according to the structure of the main task stack. Afterwards, the phone receives a back gesture on the displayed page B3 and, in response, displays page A1 of application A.

[0158] The aforementioned page navigation events can be triggered automatically by the second application, or they can be triggered after the second application receives a user's action. For example, if the phone displays a second page and the user swipes their finger upwards on the phone screen, the second application will receive a page navigation event. Another example is if the phone displays a second page and the user clicks the "Next Page" control on that page, or if the phone displays a second page and the user clicks on a title, content, or link on that page, the second application will receive a page navigation event.

[0159] In the example above, if the phone receives a back gesture on a page in the second application that does not have a page marker configured, the phone will first execute the page jump in the main task stack, jumping the displayed page to the page preceding that page in the main task stack, thus achieving page jump within the second application. After the phone displays the second page, if it receives another back gesture, it will directly display the first page of the first application. In this way, direct page jumps between applications can also be achieved, thereby saving time and improving the efficiency of page jumps.

[0160] In some embodiments, the aforementioned page markers may not be pre-configured, but rather configured automatically by the second application after its page is launched. In this case, after the electronic device responds to the first application's operation of launching the second page of the second application, it displays the second page of the second application. Subsequently, the electronic device receives a return-to-desktop operation on the displayed second page, cancels the page markers on the second page, and displays the desktop.

[0161] When the electronic device receives a "return to desktop" operation on the second page it displays, it means that the call chain between the second application and the first application is broken. In other words, the call relationship between the second page and the first page of the first application no longer exists. Since the call chain is broken, the page tag of the second page does not need to exist, and the electronic device can cancel the page tag of the second page.

[0162] In some embodiments, see Figure 11 As shown, the above method for page navigation between applications may also include the following steps S1101-S1104.

[0163] S1101, the phone displays the first page of the first application.

[0164] The first application and the first page can be referred to in the aforementioned embodiment S601, and will not be repeated here.

[0165] S1102. After the mobile phone responds to the operation of the first application to launch the second page of the second application, it displays the second page of the second application.

[0166] The second application and the second page can refer to the content in the aforementioned embodiment S602, and will not be repeated here. Furthermore, in S1102, the mobile phone can present the user with a page transition effect between applications that jump from the first page to the second page.

[0167] In some examples, in addition to the main task stack of the second application, the phone can also create a temporary task stack for the second application and store the second page in the temporary task stack. Understandably, the second page is the first page pushed onto the temporary task stack.

[0168] In some examples, before creating a temporary task stack for the second application, the phone needs to obtain the launch type of the second application or page. The launch type indicates whether the second application or page is launched from the phone's home screen or from another application. If the phone determines that the second application or page was launched from another application, it creates a temporary task stack and adds the second page to that stack. If the phone determines that the second application or page was launched from the home screen, it adds the second page to the main task stack of the second application.

[0169] For example, after the second page is launched, the runtime management service can obtain information about the launcher, such as the phone's desktop or the application. Then, the runtime management service determines the launch type based on the launcher information. If the launch type indicates that the second page is launched by another application, the runtime management service will create a temporary task stack for the second application.

[0170] In some examples, the phone can also obtain parameter information from the first application to indicate the second page, and send this parameter information to the second application. The second application then determines the second page based on the parameter information, and the phone displays the second page. In this way, when responding to the first application launching the second application's page, the phone can more accurately determine the second application's page to launch and display based on the parameter information sent by the first application, providing a better user experience.

[0171] S1103, the phone receives a return gesture on the second page displayed.

[0172] The back gesture can be referred to in the aforementioned embodiment S603, and will not be repeated here. Since these back gestures are commonly used or familiar to users, using them to operate the second page displayed on the phone or to operate the phone itself is in line with user habits and ensures a good user experience.

[0173] It is understandable that, since the task stack is a last-in-first-out data structure, and the second page is the first page pushed onto the temporary task stack, when the phone displays the second page, the temporary task stack may only contain the second page. Therefore, the above S603 can also be seen as the phone receiving a back gesture when displaying the page at the bottom of the temporary task stack.

[0174] S1104. In response to the back gesture, the phone displays the first page of the first application.

[0175] Understandably, the second page is the first page pushed onto the temporary task stack. When the phone is displaying the second page, which is the first page pushed onto the temporary task stack, it will only display the first page if a back gesture is received. (See example...) Figure 12 As shown in (a), when application A displays page A1, it launches page B3 of application B. When the phone displays page B3, which was the first page entered in the temporary task stack, it receives a back gesture, thus displaying page A1 of application A. However, if the phone receives a back gesture on another page in the displayed temporary task stack, it will perform an in-app page return, that is, jump to display the previous page in the temporary task stack, for example, see [reference 1]. Figure 12 As shown in (b), when the phone displays page B4 in the temporary task stack of application B, it receives a back gesture, thereby displaying page B3 of application B.

[0176] In S1104, the phone can present a page jump effect where the user is directly redirected from the second application back to the first application.

[0177] Understandably, the aforementioned temporary task stack stores pages launched by other applications within the second application and other pages opened within the second application after those pages. The main task stack, on the other hand, stores pages launched from the desktop within the second application, or pages opened within the application itself.

[0178] In some examples, after the phone navigates back to display the first page of the first application, it indicates that the task of launching the second page has been completed, or that the call chain between the first and second applications has been broken. In this case, the page no longer exists 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 launched again by the first application or another application, the phone will recreate the temporary task stack for the second application.

[0179] In some examples, after the second page is launched, the second application runs in the foreground, indicating that a call chain exists between the first and second applications. After the second application is moved to the background, it indicates that the call chain between the first and second applications is broken, in which case the temporary task stack of the second application can be destroyed. When the second application's page is launched again by the first application or another application, the phone recreates a temporary task stack for the second application.

[0180] The temporary task stack of the above applications will not affect the main task stack of the applications. After the call chain between the first application and the second application is broken, the temporary task stack will be destroyed, while the main task stack of the second application will continue to exist. When the user puts the second application back in the foreground, the pages opened in the second application will be added to the main task stack of the second application.

[0181] In some examples, when the temporary task stack of the second application is destroyed, if at least one page is still stored in the temporary task stack of the second application, then at least one page is stored in the main task stack of the second application to ensure that 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, they can still view the last page they viewed, thus ensuring a good user experience.

[0182] For example, the main task stack of the second application contains pages B1 and B2, while its temporary task stack contains pages B3, B4, and B5. When the temporary task stack is destroyed, the phone saves pages B3, B4, and B5 into the main task stack, resulting in the main task stack containing pages B1, B2, B3, B4, and B5 in that order. When the user brings the second application back to the foreground, page B5 is displayed. If the user performs a back gesture on page B5, the phone can jump to page B4; if the user performs a back gesture on page B4, the phone can jump to page B3; if the user performs a back gesture on page B3, the phone can jump to page B2, and so on.

[0183] In the above-described solutions S1101-S1104, after the second page is launched, the phone saves the second page in the temporary task stack of the second application. The phone only responds to the back gesture to return to the first page of the first application when displaying the second page that was first added to the temporary task stack (or the page at the bottom of the temporary task stack), thus realizing page switching between applications. This page switching is implemented directly across applications. If there are other pages in the main task stack of the second application before the second page, there is no need to perform page switching back layer by layer in the main task stack, thereby saving the time of page switching between applications and improving the efficiency of page switching.

[0184] Furthermore, the above solution eliminates the need for application developers to configure page markers for pages that can be launched. Users can also use common back gestures to navigate between applications based on their usual usage habits, ensuring a good user experience. In addition, users can operate with one hand on the screen to control page navigation, making the operation more convenient.

[0185] In some examples, the second application may include multiple pages. After the first application launches and displays the second page, the user can continue to operate on the second page, causing the second application to receive a page navigation event. This allows the phone to display other pages within the second application, which the user can then browse. In this case, the phone will continue to add other pages of the second application after the second page in the second application's temporary task stack. Subsequently, if the phone receives a back gesture while displaying other pages of the second application, a page navigation within the second application will be achieved.

[0186] For example, after displaying the second page, if the second application receives a page jump event, the phone displays the third page of the second application corresponding to the page jump event. The page jump event indicates a jump from the displayed second page to the third page. After the third page is jumped to, the phone can add the third page to the temporary task stack of the second application, pushing it after the second page. Then, the phone receives a back gesture on the displayed third page and, in response, displays the second page. Since the third page is not the first page pushed onto the temporary task stack (or not the page at the bottom of the stack), the phone can determine that the third page was not launched by another application. Therefore, the phone will not perform a page jump between applications, but instead displays the second page, preceding the third page, according to the structure of the temporary task stack. Then, the phone receives a back gesture on the displayed second page and, in response, displays the first page of the first application.

[0187] The page redirection event described above can be referred to in the previous embodiments, and will not be repeated here.

[0188] In the example above, if the phone receives a back gesture while displaying a page that is not the first page added to the temporary task stack of the second application, the phone will first execute the page jump in the temporary task stack, switching the displayed page to the page preceding that page in the temporary task stack. This achieves page jump within the second application. After the phone displays the second page, if it receives another back gesture, it will directly display the first page of the first application. This also enables direct page jumps between applications, saving time and improving page jump efficiency.

[0189] In some examples, the second application can also launch pages from other applications. If the first application launches the second application's page, and then the second application launches other applications, this indicates that the call chain between the first and second applications is broken. The temporary task stack of the second application will be destroyed, and the phone can create temporary task stacks for other applications. The page navigation between the second application and other applications can then refer to the page navigation between the first and second applications in the aforementioned embodiments. Here, "other applications" can be applications other than the first application, or other applications can include the first application.

[0190] For example, after the phone displays the second page, if the second application launches the fourth page of the third application, the 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. The fourth page is the first page pushed onto the third application's temporary task stack. Then, if the phone receives a back gesture on the displayed fourth page, it responds by displaying the second page of the second application. This achieves page navigation between applications.

[0191] In the example above, the second application can also launch a page from the third application. In this case, after the fourth page of the third application is launched, the fourth page is saved in the third application's temporary task stack, while the second application's temporary task stack is destroyed. The phone will only respond to the back gesture and return to the second page of the second application when it displays the fourth page, which was the first page added to the temporary task stack, thus achieving page navigation between applications. This kind of page navigation is implemented directly across applications. If there are other pages in the second application's main task stack before the second page, there is no need to perform page navigation back layer by layer in the main task stack, thereby saving time for page navigation between applications and improving the efficiency of page navigation.

[0192] The methods described in this application embodiment can enable page navigation between applications. In other embodiments, the methods can also enable navigation between mini-programs within an application, or between an application and a mini-program in another application. Mini-program developers can configure page tags for mini-program pages, or the mobile phone can create a temporary task stack for the mini-program. More specific implementation methods can be found in the foregoing embodiments, and will not be repeated here.

[0193] The above embodiments are examples of mobile phones implementing the method of page jump between applications in this application embodiment to illustrate the method. In other embodiments, terminal devices such as tablet computers, personal computers, wearable devices, smart furniture devices, and in-vehicle systems can also implement the above-mentioned method of page jump between applications. For specific implementation methods, please refer to the content in the foregoing embodiments, which will not be repeated here.

[0194] This application also provides an electronic device, such as... Figure 13 As shown, the electronic device may include one or more processors 1301, memory 1302 and communication interface 1303.

[0195] The memory 1302, communication interface 1303, and processor 1301 are coupled together. For example, the memory 1302, communication interface 1303, and processor 1301 can be coupled together via bus 1304.

[0196] The communication interface 1303 is used for 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 inter-application page navigation method described in this embodiment.

[0197] The processor 1301 may be a processor or controller, such as 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 devices, transistor logic devices, hardware components, or any combination thereof. It can implement or execute the various exemplary logic blocks, modules, and circuits described in conjunction with this disclosure. The processor may also be a combination that implements computational functions, such as a combination of one or more microprocessors, a combination of a DSP and a microprocessor, etc.

[0198] 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 address bus, data bus, control bus, etc. For ease of representation, Figure 13 The bus is represented by a single thick line, but this does not mean that there is only one bus or one type of bus.

[0199] This application also provides a computer-readable storage medium that includes computer instructions. When the computer instructions are executed on an electronic device, the electronic device performs the relevant method steps described in the above method embodiments.

[0200] This application also provides a computer program product that, when run on a computer, causes the computer to execute the relevant method steps described in the above method embodiments.

[0201] The electronic devices, computer-readable storage media, or computer program products provided in this application are all used to perform the corresponding methods provided above. Therefore, the beneficial effects they can achieve can be referred to the beneficial effects in the corresponding methods provided above, and will not be repeated here.

[0202] Through the above description of the embodiments, those skilled in the art can clearly understand that, for the sake of convenience and brevity, only the division of the above functional modules is used as an example. In actual applications, the above functions can be assigned to different functional modules as needed, that is, the internal structure of the device can be divided into different functional modules to complete all or part of the functions described above.

[0203] In the several embodiments provided in this application, it should be understood that the disclosed apparatus and methods can be implemented in other ways. For example, the apparatus embodiments described above are merely illustrative; for instance, the division of modules or units is only a logical functional division, and in actual implementation, there may be other division methods. For example, multiple units or components may be combined or integrated into another device, or some features may be ignored or not executed. Furthermore, the mutual coupling or direct coupling or communication connection shown or discussed may be through some interfaces; the indirect coupling or communication connection between devices or units may be electrical, mechanical, or other forms.

[0204] The units described as separate components may or may not be physically separate. A component shown as a unit can be one or more physical units; that is, it can be located in one place or distributed in multiple different locations. Some or all of the units can be selected to achieve the purpose of this embodiment according to actual needs.

[0205] Furthermore, the functional units in the various embodiments of this application can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit. The integrated unit can be implemented in hardware or as a software functional unit.

[0206] If the integrated unit is implemented as a software functional unit and sold or used as an independent product, it can be stored in a readable storage medium. Based on this understanding, the technical solution of the embodiments of this application, in essence, or the part that contributes, or all or part of the technical solution, can be embodied in the form of a software product. This software product is stored in a storage medium and includes several instructions to cause a device (which may be a microcontroller, chip, etc.) or processor to execute all or part of the steps of the methods described in the various embodiments of this application. The aforementioned storage medium includes various media capable of storing program code, such as USB flash drives, portable hard drives, read-only memory (ROM), random access memory (RAM), magnetic disks, or optical disks.

Claims

1. 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; 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 storing opened pages in the second application; the page mark is used for indicating that the second page is pulled up by other applications; the second application further comprises a third page; after the second application receives a page jump event, displaying the third page of the second application; the page jump event is used for indicating that the third page is jumped from the second page; 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; receiving a return gesture on the displayed second page; in a case where it is identified that the second page is configured with a page mark, in response to the return gesture, canceling the page mark of the second page, and displaying the first page of the first application.

2. The method of claim 1, wherein, The displaying of the second page of the second application comprises: obtaining parameter information from the first application; the parameter information is used for indicating 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.

3. The method of claim 1, wherein, The return gesture is a gesture of sliding from the edge of the screen to the middle of the screen.

4. The method of claim 1, wherein, 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.

5. The method according to any one of claims 1 to 4, 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 a return desktop operation on the displayed second page, canceling the page mark of the second page; displaying the desktop. 6.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 for storing at least the second page pulled up through the first page, and the second page is the first-in stack page in the temporary task stack of the second application; the temporary task stack is further used for storing at least one page opened in the second application after the second page is pulled up; after the second application receives a page jump event, displaying a third page of the second application; the page jump event is used for indicating that the third page is jumped from the second page; the third page is added to the temporary task stack of the second application; receiving a return gesture on the displayed third page; In response to the return gesture, the second page of the second application is displayed, and the third page is removed from the temporary task stack; A return gesture is received on the second page that is displayed; In response to the return gesture, the temporary task stack of the second application is destroyed, and the first page of the first application is displayed.

7. The method of claim 6, wherein, After the first page of the first application is displayed, the temporary task stack of the second application is destroyed; or, after the second application is placed in the background, the temporary task stack of the second application is destroyed.

8. The method of claim 6, wherein, After displaying the second page of the second application, the method further includes: Upon responding to the operation of the second application launching the fourth page of the third application, the fourth page of the third application is displayed; the fourth page is added to the temporary task stack of the third application; the fourth page is the first page pushed onto the temporary task stack of the third application. A return gesture is received on the fourth page that is displayed; In response to the return gesture, the second page of the second application is displayed.

9. The method of claim 8, wherein, The method further includes: After responding to the second application's operation of launching the third application's fourth page, the temporary task stack of the second application is destroyed; When the temporary task stack of the second application still contains at least one page, the at least one page is saved to the main task stack of the second application; the main task stack is used to save the pages opened in the second application.

10. The method of claim 6, wherein, The second page displaying the second application includes: Parameter information is obtained from the first application; the parameter information is used to instruct the second page; Send the parameter information to the second application; Obtain the second page determined by the second application based on the parameter information; The second page will be displayed.

11. The method of claim 6, wherein, The operation of launching the second page of the second application in response to the first application includes: Receive user operations on the functional controls of the first page; In response to the operation, the second page is displayed; wherein the second page displays content associated with the first page or the functional control.

12. The method according to any one of claims 6-11, characterized in that, The return gesture is a swipe gesture from the edge of the screen towards the center of the screen.

13. An electronic device, comprising: The device includes a memory and one or more processors; the memory is coupled to the processors; wherein the memory stores computer program code, the computer program code including computer instructions, which, when executed by the processor, cause the electronic device to perform the inter-application page navigation method as described in any one of claims 1-5, or to perform the inter-application page navigation method as described in any one of claims 6-12.

14. A computer-readable storage medium, characterized in that, The method includes computer instructions that, when executed on an electronic device, cause the electronic device to perform the method of inter-application page navigation as described in any one of claims 1-5, or the method of inter-application page navigation as described in any one of claims 6-12.

15. 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 navigation as described in any one of claims 1-5, or to perform the method of inter-application page navigation as described in any one of claims 6-12.

Images