Window display method and related device

Abstract

Embodiments of the present application provide a window display method and related device, and relate to the technical field of terminals. After receiving a preset operation of a user, an electronic device can display an independent embedded window. The embedded window can include a function page of an application program, so that the user can conveniently use the function of the application program. The embedded window is independent of any application program installed in the electronic device, and therefore, the display and interaction of the embedded window will not interrupt the running of the application program in the electronic device.

Description

Technical Field

[0001] This application relates to the field of terminal technology, and in particular to a window display method and related apparatus. Background Technology

[0002] With the development of terminal technology, electronic devices are able to support the operation of a wide variety of applications.

[0003] In some implementations, for applications loaded on electronic devices, if a user wants to use a certain function of the application, the user needs to click the application icon on the electronic device. After the application is launched, the user has to find the function level by level in the application's various pages before they can use it.

[0004] However, the above implementation makes the user's operation of the application cumbersome, which affects the user experience. Summary of the Invention

[0005] This application provides a window display method and related apparatus, which simplifies the way to open application functions.

[0006] In a first aspect, embodiments of this application provide a window display method applied to an electronic device, comprising:

[0007] The system displays a first interface, which includes page content corresponding to the first task of the first application; receives a first preset operation; responds to the first preset operation by displaying an embedded window on top of the first interface without interrupting the execution of the first task, the embedded window including page content corresponding to the second task of the second application; receives a second preset operation; responds to the second preset operation by canceling the display of the embedded window and restoring the display of page content corresponding to the first task of the first application.

[0008] In this way, embedded windows can be displayed in a way that is convenient for users to operate. Tasks can be provided to users in the embedded windows, allowing them to easily use the tasks in the embedded windows. Moreover, displaying the embedded windows does not interrupt the applications already running on the electronic device, thus ensuring better continuity of the applications running on the electronic device, reducing interference with the user's application use, and improving the user experience.

[0009] In one possible implementation, the page content corresponding to the second task of the second application is displayed in the first area of ​​the embedded window. The embedded window also includes a second area, located above the first interface. The second area of ​​the embedded window further displays: a first icon corresponding to the second task and a second icon corresponding to the third task; wherein the first icon is selected, and the second icon is unselected. In this way, the embedded window can provide multiple tasks, allowing users to conveniently use multiple applications. The task currently displaying page content is selected in the second area, while other tasks not displaying page content can be unselected, making it easier for users to understand the name of the task they are currently using.

[0010] In one possible implementation, before receiving the second preset operation, the method further includes: receiving a third preset operation in the embedded window to switch the second task to a third task; in response to the third preset operation, displaying the interface content corresponding to the third task in a first area of ​​the embedded window, and displaying a first icon and a second icon in a second area of ​​the embedded window; wherein the first icon is in an unselected state, and the second icon is in a selected state. This allows users to flexibly switch between multiple tasks within the embedded window, increasing the convenience of using multiple tasks.

[0011] In one possible implementation, after displaying the interface content corresponding to the third task in the first area of ​​the embedded window, the method further includes: receiving an upward swipe operation in the first area of ​​the embedded window; responding to the upward swipe operation, displaying a first button in the first area of ​​the embedded window; and when a trigger operation is received on the first button, displaying the page content associated with the first button in the third task in the first area of ​​the embedded window. This enriches the content of the embedded window, enabling users to access more services based on it.

[0012] In one possible implementation, the first button includes a second button within the page content associated with the third task. The method further includes: when a trigger operation on the second button is received, restoring the display of the interface content corresponding to the first task in the first area of ​​the embedded window. This allows users to conveniently return to the previous page within the embedded window.

[0013] In one possible implementation, the third task can be: a task of the first application, a task of the second application, or a task of the third application. This allows users to utilize different tasks from different applications within an embedded window, increasing the richness and convenience of the user experience.

[0014] In one possible implementation, the page content corresponding to the second task of the second application includes a third button. The method further includes: when a trigger is received on the third button, displaying an input box in the embedded window; when a trigger is received on the input box, displaying the keyboard; and displaying the input content received from the keyboard in the input box. This allows users to conveniently input data using the embedded window.

[0015] In one possible implementation, after displaying the embedded window on top of the first interface, the process further includes: receiving a notification message; continuing to display the embedded window, and displaying the notification message in the form of a capsule or banner on top of the embedded window. This allows the user to see the notification message instantly while using the embedded window.

[0016] In one possible implementation, the method further includes: displaying a second interface, the second interface including a first switch; when a trigger operation for turning on the first switch is received, displaying a third interface, the third interface including an added column and a not added column, the added column including identifiers of one or more user-defined added tasks, and the not added column including identifiers of one or more tasks provided by the electronic device that have not been added by the user; when an operation for deleting a first target task from the added column is received, the display of the identifier of the first target task is removed from the added column, and the identifier of the first target task is displayed in the not added column; or, when an operation for adding a second target task from the not added column is received, the display of the identifier of the second target task is removed from the not added column, and the identifier of the second target task is displayed in the added column. This allows users to conveniently customize the tasks they need.

[0017] In one possible implementation, the "Not Added" column includes an identifier for a third target task whose corresponding application is not installed on the electronic device. The method further includes displaying a prompt message when an operation to add the third target task from the "Not Added" column is received, prompting the user to install the application corresponding to the third target task. This allows users to customize a wider range of tasks, not limited to applications already installed on the electronic device.

[0018] In one possible implementation, the third interface also includes a second switch, and the method further includes: when a trigger operation to turn on the second switch is received, displaying a recommendation icon in a blank area of ​​the added column. This allows the electronic device to recommend suitable tasks to the user based on the user's context.

[0019] In one possible implementation, in response to a first preset operation, an embedded window is displayed on top of the first interface. This embedded window includes page content corresponding to the second task of the second application. The process includes: responding to the first preset operation, when it is determined that the second switch is in an "on" state, determining the second task of the second application based on a recommendation algorithm. This recommendation algorithm is related to one or more of the following: time information, the user's geofence, or user-related information in the user profile. The embedded window is then displayed on top of the first interface, including the page corresponding to the second task of the second application. In this way, the electronic device can recommend suitable quick task cards to the user based on the user's current scenario, improving the user experience.

[0020] In one possible implementation, the second task of the second application is determined based on a recommendation algorithm, including: when the recommendation algorithm determines that the user will travel, the second task of the second application is determined to be a travel-related task; or, when the recommendation algorithm determines that the user will check in, the second task of the second application is determined to be a check-in-related task; or, when the recommendation algorithm determines that the user will make a payment, the second task of the second application is determined to be a payment-related task; or, when the recommendation algorithm determines that the user will take public transportation, the second task of the second application is determined to be a public transportation code-related task. In this way, the electronic device can recommend suitable quick task cards to the user based on the user's current scenario, improving the user experience.

[0021] In one possible implementation, the first application includes an application that supports playing video or audio content. While the electronic device displays the embedded window, the first application continues to play video or audio. This allows the application that was originally running on the electronic device to continue running.

[0022] In one possible implementation, the method further includes: when the electronic device receives a first preset operation while in a black or screen-off state, illuminating the electronic device's display screen; displaying a lock screen interface, the lower layer of which includes an embedded window; and displaying the embedded window when correct unlock input is received in the lock screen interface. In this way, the electronic device can display the embedded window from a black or screen-off state based on a simple user trigger.

[0023] In one possible implementation, the method further includes: when the electronic device receives a first preset operation while in a screen-on / locked state, displaying a lock screen interface, the lower layer of which includes an embedded window; and when correct unlock input is received in the lock screen interface, displaying the embedded window. In this way, the electronic device can display the embedded window from a screen-on / locked state based on a simple user trigger.

[0024] In one possible implementation, in response to a first preset operation, an embedded window is displayed on top of the first interface without interrupting the execution of the first task. The embedded window includes page content corresponding to the second task of the second application. This includes: in response to the first preset operation, creating a new task for the second application and displaying the embedded window on top of the first interface without interrupting the execution of the first task. This allows the second application to provide the embedded window with the page content corresponding to the second task based on the newly created task, without requiring the electronic device to switch to the second application, thus ensuring better continuity of the second application's operation.

[0025] In one possible implementation, receiving a first preset operation includes receiving a double-click operation on the back of the electronic device. This operation method is relatively convenient and easy for users to implement.

[0026] Secondly, embodiments of this application provide a window display device, which can be an electronic device, or a chip or chip system within an electronic device. The window display device may include a display unit and a processing unit. When the window display device is an electronic device, the display unit may be a display screen. The display unit is used to perform display steps to enable the electronic device to implement a window display method described in the first aspect or any possible implementation of the first aspect. When the window display device is an electronic device, the processing unit may be a processor. The window display device may further include a storage unit, which may be a memory. The storage unit is used to store instructions, and the processing unit executes the instructions stored in the storage unit to enable the electronic device to implement a window display method described in the first aspect or any possible implementation of the first aspect. When the window display device is a chip or chip system within an electronic device, the processing unit may be a processor. The processing unit executes the instructions stored in the storage unit to enable the electronic device to implement a window display method described in the first aspect or any possible implementation of the first aspect. The storage unit can be a storage unit inside the chip (e.g., a register, cache, etc.) or a storage unit located outside the chip within the electronic device (e.g., a read-only memory, random access memory, etc.).

[0027] For example, a display unit is used to display a first interface, which includes page content corresponding to a first task of a first application; a processing unit is used to receive a first preset operation; the display unit is further used to respond to the first preset operation by displaying an embedded window on top of the first interface without interrupting the execution of the first task, the embedded window including page content corresponding to a second task of a second application; the processing unit is further used to receive a second preset operation; the display unit is further used to respond to the second preset operation by canceling the display of the embedded window and restoring the display of the page content corresponding to the first task of the first application.

[0028] In one possible implementation, the page content corresponding to the second task of the second application is displayed in the first area of ​​the embedded window. The embedded window also includes a second area. Above the first interface, the second area of ​​the embedded window also displays: a first icon corresponding to the second task and a second icon corresponding to the third task; wherein the first icon is selected and the second icon is unselected.

[0029] In one possible implementation, the processing unit is further configured to receive a third preset operation in the embedded window for switching the second task to the third task; the display unit is further configured to, in response to the third preset operation, display the interface content corresponding to the third task in a first area of ​​the embedded window, and display a first icon and a second icon in a second area of ​​the embedded window; wherein the first icon is in an unselected state, and the second icon is in a selected state.

[0030] In one possible implementation, the processing unit is further configured to receive an upward swipe operation in a first area of ​​the embedded window; the display unit is further configured to display a first button in the first area of ​​the embedded window in response to the upward swipe operation; and the display unit is further configured to display the page content associated with the first button in the third task in the first area of ​​the embedded window when a trigger operation on the first button is received.

[0031] In one possible implementation, the first button includes a second button in the page content associated with the third task. The display unit is also used to restore the display of the interface content corresponding to the first task in the first area of ​​the embedded window when a trigger operation on the second button is received.

[0032] In one possible implementation, the third task is either the task of the first application, the task of the second application, or the task of the third application.

[0033] In one possible implementation, the page content corresponding to the second task of the second application includes a third button. The display unit is also used to display an input box in the embedded window when a trigger is received on the third button; to display the keyboard when a trigger is received on the input box; and to display the input content received from the keyboard in the input box.

[0034] In one possible implementation, the display unit is further configured to continue displaying the embedded window when a notification message is received, and to display the notification message in the form of a capsule or banner on top of the embedded window.

[0035] In one possible implementation, the display unit is further configured to display a second interface, the second interface including a first switch; when a trigger operation for turning on the first switch is received, a third interface is displayed, the third interface including an added column and an unadded column, the added column including identifiers of one or more tasks added by the user, and the unadded column including identifiers of one or more tasks provided by the electronic device that have not been added by the user; when an operation for deleting a first target task from the added column is received, the display of the identifier of the first target task is canceled in the added column, and the identifier of the first target task is displayed in the unadded column; or, when an operation for adding a second target task from the unadded column is received, the display of the identifier of the second target task is canceled in the unadded column, and the identifier of the second target task is displayed in the added column.

[0036] In one possible implementation, the "Not Added" column includes an identifier for a third target task, the application corresponding to which the third target task is not installed in the electronic device, and the display unit is further configured to display a prompt message when an operation to add the third target task in the "Not Added" column is received, the prompt message being used to prompt the installation of the application corresponding to the third target task.

[0037] In one possible implementation, the third interface also includes a second switch and a display unit, which is further configured to display a recommendation icon in the blank area of ​​the added column when a trigger operation for turning on the second switch is received.

[0038] In one possible implementation, the processing unit, specifically configured to respond to a first preset operation, when determining that the second switch is in the on state, determines a second task of the second application based on a recommendation algorithm, the recommendation algorithm being related to one or more of the following: time information, the geofence where the user is located, or user-related information in the user profile; and displays an embedded window on top of the first interface, the embedded window including the page corresponding to the second task of the second application.

[0039] In one possible implementation, the processing unit is specifically configured to: when it is determined based on the recommendation algorithm that a user will travel, determine the second task of the second application as a travel-related task; or when it is determined based on the recommendation algorithm that a user will check in, determine the second task of the second application as a check-in-related task; or when it is determined based on the recommendation algorithm that a user will make a payment, determine the second task of the second application as a payment-related task; or when it is determined based on the recommendation algorithm that a user will take a ride, determine the second task of the second application as a ride code-related task.

[0040] In one possible implementation, the first application includes an application that supports playing video or audio content, and the electronic device keeps the first application playing video or audio while the embedded window is displayed.

[0041] In one possible implementation, the processing unit is further configured to illuminate the display screen of the electronic device when the electronic device receives a first preset operation in a black screen or screen-off state; the display unit is further configured to display a lock screen interface, the lower layer of which includes an embedded window; and the display unit is further configured to display the embedded window when a correct unlock input is received in the lock screen interface.

[0042] In one possible implementation, the display unit is further configured to display a lock screen interface when the electronic device receives a first preset operation while the screen is on and locked, wherein the lower layer of the lock screen interface includes an embedded window; the display unit is further configured to display the embedded window when the correct unlock input is received in the lock screen interface.

[0043] In one possible implementation, the processing unit is further configured to create a new task for the second application in response to a first preset operation, and the display unit is further configured to display an embedded window on top of the first interface without interrupting the execution of the first task. The embedded window includes the page content corresponding to the second task of the second application.

[0044] In one possible implementation, the processing unit is specifically configured to receive a double-click operation on the back of the electronic device.

[0045] Thirdly, embodiments of this application provide an electronic device including a processor and a memory, the memory for storing code instructions, and the processor for running the code instructions to perform the methods described in the first aspect or any possible implementation of the first aspect.

[0046] Fourthly, embodiments of this application provide a computer-readable storage medium storing a computer program or instructions that, when executed on a computer, cause the computer to perform the methods described in the first aspect or any possible implementation thereof.

[0047] Fifthly, embodiments of this application provide a computer program product including a computer program, which, when run on a computer, causes the computer to perform the methods described in the first aspect or any possible implementation of the first aspect.

[0048] Sixthly, this application provides a chip or chip system including at least one processor and a communication interface. The communication interface and the at least one processor are interconnected via a circuit. The at least one processor is used to run computer programs or instructions to perform the methods described in the first aspect or any possible implementation thereof. The communication interface in the chip can be an input / output interface, pins, or circuits, etc.

[0049] In one possible implementation, the chip or chip system described above in this application further includes at least one memory storing instructions. The memory can be an internal storage unit of the chip, such as a register or cache, or it can be a storage unit of the chip itself (e.g., read-only memory, random access memory, etc.).

[0050] It should be understood that the second to sixth aspects of this application correspond to the technical solutions of the first aspect of this application, and the beneficial effects achieved by each aspect and the corresponding feasible implementation are similar, and will not be repeated here. Attached Figure Description

[0051] Figure 1 This is a schematic diagram of the structure of the electronic device 100 provided in the embodiments of this application;

[0052] Figure 2 A schematic diagram of the software structure of the electronic device 100 provided in the embodiments of this application;

[0053] Figure 3 This is a schematic diagram of the interface provided in an embodiment of this application;

[0054] Figure 4 A schematic diagram of the hardware and software framework provided in the embodiments of this application;

[0055] Figure 5 This is a schematic diagram of module interaction provided in an embodiment of this application;

[0056] Figure 6 A schematic diagram of an interface for setting up tasks provided in an embodiment of this application;

[0057] Figure 7 A schematic diagram of another interface for setting up tasks provided in an embodiment of this application;

[0058] Figure 8 A schematic diagram of an interface for adjusting the task order provided in an embodiment of this application;

[0059] Figure 9 A schematic diagram illustrating an interface transitioning from a black screen to the display of an embedded window, provided as an embodiment of this application;

[0060] Figure 10A schematic diagram of an interface from lock screen to display of embedded window provided for an embodiment of this application;

[0061] Figure 11 A schematic diagram of an interface from the desktop to the display of an embedded window provided for an embodiment of this application;

[0062] Figure 12 A schematic diagram of an interface from a video application screen to a display embedded window, provided for an embodiment of this application;

[0063] Figure 13 A schematic diagram of an interface from application A to the display of an embedded window is provided for an embodiment of this application;

[0064] Figure 14 A schematic diagram of an interface from a cold start or loading failure to the display of an embedded window, provided for an embodiment of this application;

[0065] Figure 15 A schematic diagram of an interface for several possible tasks of an embedded window display provided in an embodiment of this application;

[0066] Figure 16 A schematic diagram of an embedded window displaying payment tasks provided in an embodiment of this application;

[0067] Figure 17 A schematic diagram of another embedded window interface for displaying payment tasks provided in an embodiment of this application;

[0068] Figure 18 A schematic diagram of an embedded window display interface for line-type tasks provided in an embodiment of this application;

[0069] Figure 19 A schematic diagram of an interface receiving a notification message when an embedded window is displayed, provided as an embodiment of this application;

[0070] Figure 20 This application provides a schematic diagram of an interface for exiting an embedded window.

[0071] Figure 21 A schematic diagram of another interface for exiting an embedded window provided in an embodiment of this application;

[0072] Figure 22 This application provides a schematic diagram of a window display process.

[0073] Figure 23 This is a schematic diagram of the hardware structure of the chip provided in an embodiment of this application. Detailed Implementation

[0074] To facilitate a clear description of the technical solutions in the embodiments of this application, some terms and technologies involved in the embodiments of this application will be briefly introduced below:

[0075] 1. Launcher: Launcher can be understood as a desktop application (APP). It is the entry point for applications on electronic devices using the Android system. It can manage applications and provide functions such as windows.

[0076] 2. SystemUI: Also known as the system user interface, in the Android system, SystemUI runs as an application. It provides the basic display interface for the system. Examples include: the status bar at the top of the screen, the navigation bar at the bottom of the screen, the quick settings bar in the pull-down menu, the notification bar, the lock screen, the volume control dialog, and the screenshot display interface.

[0077] 3. Quick Task Cards: These can be understood as pages displaying specific functions of an application within a window. When a window supports switching between multiple application function pages, it can be said that the window supports switching between multiple quick task cards. The display of quick task cards can be managed by the Launcher, while the specific services provided by the SystemUI can be handled by the quick task cards.

[0078] It should be noted that the quick task card in this application embodiment is not limited to the same meaning as the card in the negative one screen or the main interface, but can be understood as a custom name for ease of description. In possible implementations, the quick task card may also be called any of the following: quick service card, quick function card, task card, quick card, card, quick function page, quick function interface, function page, function interface, etc. This application embodiment does not make specific limitations.

[0079] 4. Other terms

[0080] In the embodiments of this application, terms such as "first" and "second" are used to distinguish identical or similar items with substantially the same function and purpose. For example, "first chip" and "second chip" are used only to distinguish different chips and do not limit their order of execution. Those skilled in the art will understand that terms such as "first" and "second" do not limit the quantity or execution order, and that "first" and "second" do not necessarily imply that they are different.

[0081] It should be noted that, in the embodiments of this application, the terms "exemplary" or "for example" are used to indicate examples, illustrations, or descriptions. Any embodiment or design scheme described as "exemplary" or "for example" in 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 the relevant concepts in a specific manner.

[0082] In this application embodiment, "at least one" refers to one or more, and "more than one" refers to two or more. "And / or" describes 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, or B alone, where A and B can be singular or plural. The character " / " generally indicates that the preceding and following related objects are in an "or" relationship. "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, a--c, bc, or abc, where a, b, and c can be single or multiple.

[0083] 5. Electronic equipment

[0084] The electronic devices in this application embodiment may include handheld devices with image processing functions, vehicle-mounted devices, etc. For example, some electronic devices include: mobile phones, tablets, PDAs, laptops, mobile internet devices (MIDs), wearable devices, virtual reality (VR) devices, augmented reality (AR) devices, wireless terminals in industrial control, wireless terminals in self-driving, wireless terminals in remote medical surgery, wireless terminals in smart grids, wireless terminals in transportation safety, wireless terminals in smart cities, wireless terminals in smart homes, cellular phones, cordless phones, session initiation protocol (SIP) phones, wireless local loop (WLL) stations, personal digital assistants (PDAs), handheld devices with wireless communication capabilities, computing devices or other processing devices connected to wireless modems, in-vehicle devices, terminal devices in 5G networks, or future evolution of public land mobile communication networks. Terminal devices in a mobile network (PLMN), etc., are not limited to this in the embodiments of this application.

[0085] By way of example and not limitation, in this embodiment, the electronic device can also be a wearable device. Wearable devices, also known as wearable smart devices, are a general term for devices that utilize wearable technology to intelligently design and develop everyday wearables, such as glasses, gloves, watches, clothing, and shoes. Wearable devices are portable devices that are worn directly on the body or integrated into the user's clothing or accessories. Wearable devices are not merely hardware devices, but also achieve powerful functions through software support, data interaction, and cloud interaction. Broadly speaking, wearable smart devices include those that are feature-rich, large in size, and can achieve complete or partial functions without relying on a smartphone, such as smartwatches or smart glasses, as well as those that focus on a specific type of application function and require the use of other devices such as smartphones, such as various smart bracelets and smart jewelry for vital sign monitoring.

[0086] Furthermore, in this embodiment of the application, the electronic device can also be a terminal device in the Internet of Things (IoT) system. IoT is an important part of the future development of information technology. Its main technical feature is to connect objects to the network through communication technology, thereby realizing an intelligent network of human-machine interconnection and object-to-object interconnection.

[0087] The electronic devices in the embodiments of this application may also be referred to as: terminal equipment, user equipment (UE), mobile station (MS), mobile terminal (MT), access terminal, user unit, user station, mobile station, remote station, remote terminal, mobile device, user terminal, terminal, wireless communication equipment, user agent, or user device, etc.

[0088] In this embodiment, the electronic device or various network devices include a hardware layer, an operating system layer running on top of the hardware layer, and an application layer running on top of the operating system layer. The hardware layer includes hardware such as a central processing unit (CPU), a memory management unit (MMU), and memory (also called main memory). The operating system can be any one or more computer operating systems that implement business processing through processes, such as Linux, Unix, Android, iOS, or Windows. The application layer includes applications such as browsers, address books, word processing software, and instant messaging software.

[0089] In some implementations, for applications loaded on electronic devices, if a user wants to use a specific function of the application, they need to click the application icon on the electronic device. After the application is launched, the user has to navigate through various levels of the application's pages to find the function before they can use it. However, this implementation is cumbersome for users, negatively impacting the user experience.

[0090] Alternatively, in some implementations, users can quickly open applications by tapping their electronic devices, first displaying the application's homepage, and then showing a page for a specific function within that application. However, in this implementation, a single tap can only open one function of one application, and the display process causes changes to the application's page, impacting the user experience. Furthermore, if the user wants to open a function in another application, they need to perform another tap or similar operation, or they need to open another application and search for the function within that application's page, making the process cumbersome and negatively affecting the user experience.

[0091] In view of this, embodiments of this application provide a window display method. After receiving a user's preset operation, an electronic device can display an independent window. The window may include the function page of an application, allowing the user to conveniently use the application's functions. The window may also provide identifiers of one or more other functions of the application, and / or identifiers of one or more functions of other applications. Thus, based on the identifiers of each function in the window, the user can flexibly switch between different functions of different applications.

[0092] In this context, an independent window can be understood as follows: This window is not part of any application opened by the user, but rather a system-provided window for the electronic device. This independent window can overlay any application page displayed on the electronic device. It can embed task entry points for one or more applications. When a task is executed within this independent window, a new task can be created for the corresponding application, making the execution of this task independent of other running tasks within the application. This ensures that triggering a task within the embedded window does not interrupt the operation of any application displayed on the electronic device. In this way, the window's invocation does not affect the user's current operation, improving the user experience. For example, if a user is watching a video or playing a game on their electronic device, and the user triggers the display of this window, the video or game can continue uninterrupted.

[0093] An independent window can also be called a window, an embedded window, a quick card pop-up, a pop-up, a card application window, a quick card window, a quick function window, a quick function pop-up, etc., and this application does not specifically limit it.

[0094] To better understand the embodiments of this application, the structure of the electronic device of this application is described below:

[0095] Figure 1A schematic diagram of the structure of electronic device 100 is shown. 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, antenna 1, antenna 2, a mobile communication module 150, a wireless communication module 160, an audio module 170, a speaker 170A, a receiver 170B, a microphone 170C, a headphone jack 170D, a sensor module 180, buttons 190, a motor 191, an indicator 192, a camera 193, a display screen 194, and a subscriber identification module (SIM) card interface 195, etc. The sensor module 180 may include a pressure sensor 180A, a gyroscope sensor 180B, a barometric pressure sensor 180C, a magnetic sensor 180D, an accelerometer sensor 180E, a distance sensor 180F, a proximity sensor 180G, a fingerprint sensor 180H, a temperature sensor 180J, a touch sensor 180K, an ambient light sensor 180L, a bone conduction sensor 180M, etc.

[0096] 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. The illustrated components may be implemented in hardware, software, or a combination of software and hardware.

[0097] Processor 110 may include one or more processing units, such as application processors (APs), modem processors, graphics processing units (GPUs), image signal processors (ISPs), controllers, video codecs, digital signal processors (DSPs), baseband processors, and / or neural network processing units (NPUs). These different processing units may be independent devices or integrated into one or more processors.

[0098] The controller can generate operation control signals based on the instruction opcode and timing signals to complete the control of instruction fetching and execution.

[0099] The processor 110 may also include a memory for storing instructions and data. In some embodiments, the memory in the processor 110 is a cache memory. This memory can store instructions or data that the processor 110 has just used or that are used repeatedly. If the processor 110 needs to use the instruction or data again, it can retrieve it from the memory. This avoids repeated accesses, reduces the waiting time of the processor 110, and thus improves the efficiency of the system.

[0100] In some embodiments, the processor 110 may include one or more interfaces. Interfaces may include an inter-integrated circuit (I2C) interface, an inter-integrated circuit sound (I2S) interface, a pulse code modulation (PCM) interface, a universal asynchronous receiver / transmitter (UART) interface, a mobile industry processor interface (MIPI), a general-purpose input / output (GPIO) interface, a subscriber identity module (SIM) interface, and / or a universal serial bus (USB) interface, etc.

[0101] 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.

[0102] 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, connected to the display screen 194 and the application processor. The GPU is used to perform mathematical and geometric calculations and for graphics rendering. Processor 110 may include one or more GPUs, which execute program instructions to generate or modify display information.

[0103] Display screen 194 is used to display images, videos, etc. Display screen 194 includes a display panel. The display panel may be a liquid crystal display (LCD), an organic light-emitting diode (OLED), an active-matrix organic light-emitting diode (AMOLED), a flexible light-emitting diode (FLED), a miniature LED, a microLED, a quantum dot light-emitting diode (QLED), etc. In some embodiments, electronic device 100 may include one or N displays 194, where N is a positive integer greater than 1.

[0104] Pressure sensor 180A is used to sense pressure signals and convert them into electrical signals. In some embodiments, pressure sensor 180A can be disposed on display screen 194. There are many types of pressure sensors 180A, such as resistive pressure sensors, inductive pressure sensors, and capacitive pressure sensors. A capacitive pressure sensor may include at least two parallel plates with conductive material. When force is applied to pressure sensor 180A, the capacitance between the electrodes changes. Electronic device 100 determines the pressure intensity based on the change in capacitance. When a touch operation is applied to display screen 194, electronic device 100 detects the touch operation intensity based on pressure sensor 180A. Electronic device 100 can also calculate the touch position based on the detection signal from pressure sensor 180A. In some embodiments, touch operations applied to the same touch position but with different touch operation intensities can correspond to different operation commands.

[0105] The gyroscope sensor 180B can be used to determine the motion attitude of the electronic device 100. In some embodiments, the gyroscope sensor 180B can determine the angular velocity of the electronic device 100 about three axes (i.e., the x, y, and z axes). The gyroscope sensor 180B can be used for image stabilization. For example, when the shutter is pressed, the gyroscope sensor 180B detects the angle of the shake of the electronic device 100, calculates the distance that the lens module needs to compensate based on the angle, and allows the lens to counteract the shake of the electronic device 100 by moving in the opposite direction, thus achieving image stabilization. The gyroscope sensor 180B can also be used in navigation and motion-sensing game scenarios.

[0106] The 180E accelerometer sensor can detect the magnitude of acceleration of electronic device 100 in various directions (typically three axes). When electronic device 100 is stationary, it can detect the magnitude and direction of gravity. It can also be used to identify the posture of terminal devices and applied to applications such as screen orientation switching and pedometers.

[0107] Touch sensor 180K, also known as a "touch device," can be located on display screen 194. The touch sensor 180K and display screen 194 together form a touchscreen, also known as a "touchscreen." Touch sensor 180K detects touch operations applied to or near it. The touch sensor can transmit the detected touch operation to the application processor to determine the type of touch event. Visual output related to the touch operation can be provided through display screen 194. In other embodiments, touch sensor 180K may also be located on the surface of electronic device 100, in a different position than display screen 194.

[0108] The software system of electronic device 100 can adopt a layered architecture, event-driven architecture, microkernel architecture, microservice architecture, or cloud architecture, etc. This application embodiment uses the layered architecture Android system as an example to exemplify the software structure of electronic device 100.

[0109] Figure 2 This is a software structure block diagram of the electronic device 100 according to an embodiment of this application.

[0110] A layered architecture divides software into several layers, each with a clear role and function. Layers communicate with each other through software interfaces. In some embodiments, the Android system is divided into four layers, from top to bottom: the application layer, the application framework layer, the Android runtime and system libraries, and the kernel layer.

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

[0112] like Figure 2 As shown, the application package can include applications such as camera, system UI, phone, map, music, settings, launcher, video, and social media.

[0113] 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.

[0114] like Figure 2As shown, the application framework layer may include a window manager service (WMS), an activity manager service (AMS), a content provider, a resource manager, a view system, a notification manager, etc.

[0115] The window manager is used to manage windowed applications. It can obtain the screen size, determine if a status bar is present, lock the screen, allow screen touch, drag the screen, and capture the screen, among other things.

[0116] AMS is used to manage the lifecycle of applications, start or kill application processes, schedule tasks, etc.

[0117] Content providers are used to store and retrieve data, making that data accessible to applications. This data can include videos, images, audio, phone calls made and received, browsing history and bookmarks, phone books, and more.

[0118] 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 message notification icon can include a view for displaying text and a view for displaying images. The view system in embodiments of this application can include a View or a Surface View.

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

[0120] The notification manager allows applications to display notifications in the status bar. These notifications can be used to deliver informational messages and can disappear automatically after a short pause, requiring no user interaction. For example, the notification manager can be used to notify users of download completion or message alerts. The notification manager can also display notifications as icons or scrolling text in the top status bar, such as notifications from background applications, or as dialog boxes on the screen. Examples include displaying text messages in the status bar, emitting sounds, vibrating the device, and flashing indicator lights.

[0121] The Android runtime consists of core libraries and a virtual machine. The Android runtime is responsible for scheduling and managing the Android system.

[0122] The core library consists of two parts: one part is the functionalities that need to be called by the Java language, and the other part is the Android core library.

[0123] The application layer and application framework layer run in a virtual machine. The virtual machine executes the Java files of the application layer and application framework layer as binary files. The virtual machine is used to perform functions such as object lifecycle management, stack management, thread management, security and exception management, and garbage collection.

[0124] System libraries 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), etc.

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

[0126] 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, AMR, JPG, and PNG.

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

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

[0129] 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.

[0130] For example, in combination Figure 2 , Figure 3 Some interfaces between the application layer and the application framework layer in this embodiment are shown.

[0131] like Figure 3 As shown, the application layer may include an embedded window component package, which can be part of the launcher. This embedded window component package can interact with the AMS, WMS, view, and input manager service (inputMS) of the application framework layer.

[0132] For example, an embedded window component package may include a startup control module, a task management and state synchronization module, a view embedding and display control module, an interaction control module, and a proxy service module.

[0133] The launch control module can interact with AMS based on the activity launch and exit interface, enabling AMS to manage the launch of embedded windows and the lifecycle of activities based on the activity launch and exit interface.

[0134] The Task management and state synchronization module can interact with WMS based on the Task management and state synchronization interface, and the interaction control module can interact with WMS based on the interface interaction and event passing interface. This allows WMS to implement one or more of the following management functions based on the Task management and state synchronization interface and the interface interaction and event passing interface: task stack management, activity jump control, focus switching control, window visibility management, window hierarchy management, configuration update and compatibility management, insert window management, and input method window management.

[0135] The View's embedded and display control module can interact with the View based on the surface control interface, enabling the View to implement surface display control based on the surface control interface.

[0136] The proxy service can correspond to the embedded window capability access interface (or task access interface).

[0137] InputMS can be used to dispatch events when a user triggers an event in an embedded window.

[0138] based on Figure 3 The various functional modules of the application layer and application framework layer enable electronic devices to display embedded windows across tasks, thus without interrupting the user's current scene.

[0139] For example, when an electronic device receives a user trigger and needs to display an embedded window, the startup control module can call AMS to manage the activity startup and lifecycle of the embedded window based on the activity startup and exit interface. The task management and state synchronization module can call WMS to manage the task stack based on the task management and state synchronization interface, enabling the creation of new tasks or stacks. The interaction control module can call WMS's activity jump control based on the interface interaction and event passing interface, enabling the retrieval of the page content to be displayed in the embedded window from the application accessed by the proxy service. The view embedding and display control module can call the surface view obtained by converting the page content to be displayed in the View based on the surface control interface, enabling the display of the embedded window. When the embedded window is displayed, WMS can configure the basic parameters of the embedded window based on configuration update and compatibility management. WMS can also manage the status bar (e.g., WiFi icon, carrier icon, etc.) and navigation bar (e.g., virtual buttons) on the display screen other than the embedded window based on insert window management, so that the status bar and navigation bar do not affect the display of the embedded window.

[0140] During the display of an embedded window, the embedded window may receive trigger operations, generating trigger events. InputMS can dispatch these events, which are then responded to and processed by the corresponding modules of WMS. For example, when the embedded window receives a task switching operation, WMS's focus switching control can control the focus switching; when the embedded window receives an operation to enter a lower or higher level page, WMS's window hierarchy management can control the change in window hierarchy; when the embedded window receives an input operation, WMS's input method window management can manage the input method; and when the embedded window receives an operation to cancel its display, WMS's window visibility management can control the cancellation of the embedded window's display.

[0141] In this embodiment of the application, when displaying the embedded window, a new task or a new stack is created so that the running task in the embedded window is independent of the running task of the application, thereby not interrupting the task running by the application.

[0142] It is understood that implementing the window display method of this application requires both software logic and some hardware within the electronic device. For example, Figure 4 A schematic diagram of the hardware and software architecture for implementing the method of the embodiments of this application is shown.

[0143] In possible implementations, Figure 4System applications, artificial intelligence (AI) platforms, and infrastructure can all be applications running at the application layer. Chip platforms and chip algorithms can run at the kernel layer or the application framework layer; this application does not impose specific limitations on these aspects.

[0144] The following example illustrates the workflow of the software and hardware of the electronic device 100, using a scenario where a user taps the back of the phone to trigger the window display method of this application embodiment.

[0145] When the accelerometer and / or gyroscope detects a tap, a corresponding hardware interrupt is sent to the kernel layer. The kernel layer processes the tap into a raw input event, which may include values ​​acquired by the accelerometer, values ​​acquired by the gyroscope, audio signals, and / or touch panel (TP) signals. The raw input event is stored in the kernel layer. The chip algorithm can identify whether the original input event is a tap on the back of the phone based on the phone's back tap recognition algorithm. Here, a tap can refer to multiple consecutive taps or a single tap. The phone's back tap recognition algorithm can include pre-judgment of information in the original input event, feature extraction, neural network recognition, and result output. The values ​​collected by the accelerometer and gyroscope in the original input event can be core features, while audio signals and TP signals can be auxiliary features. The neural network can be a model trained based on machine learning or deep learning to recognize phone back taps. After recognizing the phone's back tap event, the chip platform can adapt the software channel interface at the application framework layer based on the back tap software channel adaptation. The application framework layer can encapsulate the event on the software channel side into an interface that can be called by the system application. The application layer can call the interface encapsulated by the application framework layer to launch an embedded pop-up window. The content to be displayed in the embedded pop-up window can include the function pages of one or more applications configured by the user locally on the phone, and / or the function pages of one or more applications configured in the cloud. In a possible implementation, the AI ​​platform can identify the user's current scenario. The scenario may be related to the user's usage habits, the user's time, the user's location, and / or the user's property ownership. Based on the user's current scenario, the AI ​​platform can determine the shortcut task card to be displayed in the embedded window from the content to be displayed, and the electronic device can then display the shortcut task card.

[0146] Corresponding to Figure 4 , Figure 5 An exemplary schematic diagram of the interaction flow between modules in an embodiment of this application is shown.

[0147] The window display method implemented in this application embodiment may include a setting phase and a usage phase. The setting phase may refer to the phase of setting the shortcut task cards in the window for subsequent window display. The usage phase may refer to the phase of the electronic device displaying the window after receiving a user trigger.

[0148] For example, such as Figure 5 As shown, during the setup phase: the electronic device can provide accessibility functions in the settings application. These accessibility functions include a switch to control the quick task card function to be on or off, and configurable quick task card icons. When the switch to control the quick task card function to be on or off is in the on state, the electronic device can receive one or more quick task card icons selected by the user on the accessibility function page, and / or one or more quick task card icons recommended by the cloud. The settings application can then obtain the new quick task card icons for this setup. The settings application can also retrieve previously set quick task card icons from the desktop application's database, thus obtaining a new task list result including the new quick task card icons for this setup and the previously set quick task card icons. It is understood that the desktop application's database may or may not contain previously set quick task card icons. The task list result can also be called a task list, service list result, or service list, etc., and this embodiment does not specifically limit the terminology.

[0149] The settings application can further write the status of the switch and the new task list results to the desktop application's database, thereby updating the desktop application's database.

[0150] During the usage phase: When an electronic device receives a double-tap operation on the back, this operation can be processed into a double-tap event. A software pathway based on the chip algorithm transmits this event to the chip platform. The application framework layer can encapsulate the double-tap event from the chip platform into an interface. The desktop application performs an interface callback to the encapsulated interface in the application framework layer. The desktop application loads the task list results from its database and retrieves scene services from the AI ​​platform. When the AI ​​returns the current scene service, the desktop application can determine the corresponding shortcut task card from the task list results based on the current scene service and prioritize displaying the shortcut task card corresponding to the current scene service. For example, if the current scene service indicates the user is at a subway entrance, the priority displayed shortcut task card would be the shortcut task card corresponding to the transit code function.

[0151] When displaying quick task cards, the desktop application can open a window that includes the quick task cards and retrieve the service content of the quick task cards from the systemUI. The systemUI can further retrieve the service content from the application framework layer and return a surface view to the desktop application. The desktop application can then control the display of the quick task cards based on the surface view.

[0152] above Figures 3-5 This document describes the internal logic of an electronic device, illustrating how a user taps the back of the device twice consecutively to bring up a quick task card window. The following section details the possible user interface interactions during window display in this embodiment. Subsequent user interface diagrams will be provided separately for the quick task card setting stage, quick task card usage stage, and quick task card closing stage. The quick task card setting stage can correspond to... Figure 6-8 The usage stage of a quick task card can correspond to... Figure 9-19 The quick task card closing phase can correspond to Figure 20-21 .

[0153] It is understandable that the above Figures 3-5 The double-tap operation on the back can also be replaced by any of the following: N taps on the back, N taps on a function key (e.g., volume key, power key, etc.), N taps on any area of ​​the electronic device (e.g., front, back, side, etc.), specific gesture operations, specific swipe touch operations, voice control, etc. This application embodiment does not limit the specific operation for triggering the embedded window display; it only needs to achieve the quick display of the embedded window based on a single operation. N is a natural number. For ease of description, the following user interface will use double-tapping the back to trigger the display of the phone's embedded window as an example, and the corresponding prompts will also use double-tapping the back to achieve a quick task. This example does not constitute a limitation on the operation for triggering the embedded window display or the prompts.

[0154] like Figure 6 As shown in (a), the electronic device can provide an interface for setting shortcut function cards, which may include a master switch 601 for turning shortcut task cards on or off. The state of the master switch 601 can be on or off. In... Figure 6 In the interface shown in (a), the main switch 601 is in the off state, as... Figure 6 The interface shown in (a) can display a prompt message that says "Tap the back of the phone twice to enable a quick task", but does not display any quick tasks that can be added.

[0155] Among them, entering this... Figure 6The interface shown in (a) can be accessed in at least the following ways: Method 1: In the Settings app, trigger the menu sequentially in the order of "Settings - Accessibility - Quick Launch & Gestures" to enter the interface shown in (a). Figure 6 The interface for setting up shortcut function cards is shown in (a). Method 2: When displayed in an embedded window, provide access to... Figure 6 The shortcut controls shown in (a) are for setting up shortcut function cards. The identifiers for these shortcut controls can be setting or editing identifiers, etc. These will be explained in conjunction with the illustrations later when discussing embedded window display; they will not be elaborated upon here. Of course, electronic devices can also provide other access methods such as... Figure 6 The method of setting up the shortcut function card shown in (a) is not specifically limited in this embodiment of the application.

[0156] When in such Figure 6 In the interface shown in (a), after receiving a trigger operation to turn on the main switch 601, one can enter the following... Figure 6 The interface shown in (b).

[0157] like Figure 6 As shown in (b) of the interface, the main switch is in the "on" state. Optionally, a smart recommendation switch 602 can be located below the main switch. The smart recommendation switch 602 can be in an "on" or "off" state. When the smart recommendation switch 602 is in the "on" state, the electronic device can recommend quick task cards displayed in the embedded window based on the user's current scenario. When the smart recommendation switch 602 is in the "off" state, the electronic device does not support recommending quick task cards displayed in the embedded window based on the user's current scenario, and the quick task cards displayed in the embedded window are either default or user-defined. Figure 6 In the interface shown in (b), the example is that the smart recommendation switch 602 is in the off state. The state of the smart recommendation switch 602 being on will be shown in [the diagram]. Figure 7 The details are explained in the text, and will not be repeated here.

[0158] like Figure 6 The interface shown in (b) also includes an "Added" column and a "Not Added" column. The "Added" column includes identifiers for M quick task cards that will be displayed in the embedded window pop-up. The "Not Added" column includes identifiers for L quick task cards provided by the electronic device that can support display in the embedded window pop-up. The quantities of M and L are not specifically limited in this embodiment. The identifiers of quick task cards in the "Not Added" column can be moved to the "Added" column based on the user's add operation, and the identifiers of quick task cards in the "Added" column can be moved to the "Not Added" column based on the user's remove operation.

[0159] For example, such as Figure 6As shown in (b), the identifier of any quick task card in the added column may include: the icon of the quick task, the name of the quick task, the name of the application to which the quick task is described, and a removal control 603 for removing the quick task. Here, a quick task can be understood as any function, task, or service in an application. For example, quick tasks may include payment services and scan-to-pay services in various payment applications, travel services in various travel applications, and attendance services in various office applications. In some implementations, functions that support scheme and ShortCut can also be used as quick tasks.

[0160] The identifier for any quick task card without an added bar may include: the icon of the quick task, the name of the quick task, the name of the application to which the quick task is described, and an add control 604 for adding the quick task.

[0161] It should be noted that the identifiers of the shortcut task cards included in the "Added" and "Not Added" columns can belong to tasks within a single application or tasks within multiple applications. The identifiers of shortcut task cards included in the "Added" column belong to tasks within applications installed on the electronic device. The identifiers of shortcut task cards included in the "Not Added" column can belong to tasks within either installed or uninstalled applications on the electronic device. For example, tasks a and b belong to application A, tasks c, d, and e belong to application B, and task f belongs to application C. Applications A and B are installed applications on the electronic device, while application C is an uninstalled application. The identifier of the shortcut task card corresponding to the uninstalled application C can be distinguished from the installed applications A and B by color, size, etc.

[0162] When Figure 6 When the add control for task d (without a column) shown in (b) receives a user trigger, it can enter as follows: Figure 6 The interface shown in (c) is as follows: Figure 6 As shown in (c), task d is added to the added column, and task d disappears from the corresponding unadded column.

[0163] When Figure 6 When the add control for task f (as shown in (c)) without an added column receives a user trigger, because the application C to which task f belongs is not installed on the electronic device, it can enter as follows: Figure 6 The interface shown in (d) is as follows: Figure 6As shown in (d), a prompt box can be displayed indicating that application C is not installed and needs to be installed before use. It also provides controls to proceed to the download page and to cancel the download. When the electronic device receives a trigger on the download control, it can navigate to the download interface. After the download and installation of application C are complete, the user can then proceed to the next screen. Figure 6 As shown in (c), this embodiment of the application does not limit the implementation of download, installation and redirection.

[0164] When the electronic device receives a trigger on the control to cancel the download, it can enter as follows: Figure 6 The interface shown in (e) can be used with Figure 6 The (c) is the same, so I will not elaborate further.

[0165] Users can continue to add content to the added column until the column reaches its maximum allowed limit. For example, when... Figure 6 When the addition control for task e (as shown in (e)) without an added column receives a user trigger, it can enter as follows: Figure 6 The interface shown in (f) is as follows: Figure 6 As shown in (f), task e is added to the added column, task e disappears from the unadded column, and the number of tasks in the added column reaches the limit.

[0166] Understandable Figure 6 In any of the interfaces shown in (b)-(e), if a user's operation to turn off the main switch is received, the user can return to the interface shown in (b)-(e). Figure 6 The interface shown in (a) is as follows. Figure 6 In any of the interfaces shown in (b)-(e), if an operation is received on the remove control corresponding to any task in the added column, the arbitrary task can be removed from the added column and displayed in the unadded column (not shown in the figure).

[0167] Figure 6 The following example illustrates the interface for user-defined quick task cards, with the smart recommendation switch set to the off state. Figure 7 The example uses the Smart Recommendation switch as an example to illustrate the interface for setting up quick task cards.

[0168] For example, when Figure 6 When the smart recommendation switch shown in (f) receives a user trigger, it can enter as follows: Figure 7 The interface shown in (a). Figure 7As shown in (a), the Smart Recommendation switch is on, and the Added column contains 5 user-defined tasks. So when the user triggers the display of the embedded window, because Smart Recommendation is enabled, the first task displayed in the embedded window by the electronic device may not be the first task (a) of the 5 user-defined tasks. Instead, it can select the task that best matches the user's scenario from the 5 tasks and any tasks provided by the application installed on the electronic device to display a quick task card.

[0169] In other words, when the smart recommendation switch is turned on, the electronic device can select one or more tasks that match the device's current scenario from all the services provided by the applications installed on the device, and display them in the quick task card.

[0170] When Figure 7 When the removal control for task e shown in (a) receives a user trigger, it can enter as follows: Figure 7 The interface shown in (b) is as follows: Figure 7 As shown in (b), task e is displayed in the unadded column, and task e disappears from the corresponding added column. At the same time, a dotted frame indicator for recommendation is displayed in the added column after the task. In this way, when the user triggers the display of the embedded window and the electronic device displays the first task in the embedded window, it can select the task that best matches the user's current scenario from any tasks provided by the applications installed on the electronic device and display a quick task card.

[0171] When Figure 7 When the removal control of task d shown in (b) receives a user trigger, it can enter as follows: Figure 7 The interface shown in (c) is as follows: Figure 7 As shown in (c), task d is displayed in the "Not Added" column, and disappears from the "Added" column. Simultaneously, two dotted borders indicating recommendations appear after the task in the "Added" column. This allows the user to trigger the embedded window, and when the electronic device displays the first task within it, it can select the task most relevant to the user's current scenario from any available task provided by the installed applications on the device, displaying a quick task card. The specific recommendation method will be explained in the subsequent quick task card usage section and will not be elaborated upon here.

[0172] Understandably, users can turn off the smart recommendation switch at any time, for example, when... Figure 7 When the smart recommendation switch shown in (c) receives a user trigger, it can enter the following state: Figure 7 In the interface shown in (d), the Smart Recommendation switch is off, and the dotted frame indicator for prompting recommendations is not displayed in the Added column.

[0173] Users can also continue to remove tasks from the added column, for example, in Figure 7 Based on the interface shown in (c), the electronic device can continue to receive the user's removal operation, remove all tasks added to the taskbar, and enter the interface shown in (c). Figure 7 In the interface shown in (e), all added sections are displayed as dashed borders for highlighting recommendations. In a possible implementation, the electronic device could also... Figure 7 The interface provides a control (not shown in the figure) for removing all tasks in the added taskbar with one click, so as to make it easy to remove tasks in the added taskbar.

[0174] When Figure 7 When the smart recommendation switch shown in (e) receives a user trigger, it can enter the following... Figure 7 The interface shown in (f) can automatically populate the 5 default tasks in the Added section, which are the applications already installed on the electronic device.

[0175] Figure 6 and Figure 7 In this system, the master switch, smart recommendation switch, and added taskbar can all have certain features. For example, the master switch can be on or off by default, and the electronic device can also remember user actions; the next time an interface including the master switch is displayed, its state will be the previously remembered user settings. Similarly, the smart recommendation switch can be on or off by default, and the electronic device can also remember user actions; the next time an interface including the smart recommendation switch is displayed, its state will be the previously remembered user settings. The added taskbar can support long-press dragging to adjust the task order.

[0176] For example, Figure 8 This diagram illustrates the interface for adjusting the task order in the added task bar.

[0177] In such Figure 8 In the interface shown in (a), the Smart Recommendation switch is off, and the dotted frame indicating recommendations is not displayed in the added task bar. When the icon of task a receives a long press and moves towards the position of task c, it can enter the following... Figure 8 The interface shown in (b) is as follows: Figure 8 As shown in (b), the positions of tasks a and c in the added task bar have changed. This way, when the user subsequently triggers the display of the embedded window, the task card corresponding to the task located in the first position of the added bar can be displayed first by default.

[0178] In such Figure 8 In the interface shown in (a), if the smart recommendation switch receives a user trigger, it can enter the following... Figure 8In the interface shown in (c), the Smart Recommendation switch is turned on, and a dotted frame indicating recommended features is displayed in the taskbar. Figure 8 When the icon of task a in the interface shown in (c) receives a long press and moves to the position of task c, it can enter as follows: Figure 8 The interface shown in (d) is as follows: Figure 8 In the taskbar shown in (b), the positions of tasks a and c have changed, while the position of the dotted frame indicating recommendations remains unchanged. This way, when the user subsequently triggers the display of the embedded window, either the shortcut task card corresponding to the task located in the first position of the added taskbar can be displayed first, or a recommended shortcut task card corresponding to the user's current scenario can be displayed.

[0179] Understandably, in Figure 6 and Figure 7 In any interface that displays an "Added" section, adjustments to the tasks within that section are supported, similar to... Figure 8 The description is omitted.

[0180] Figure 6-8 The example illustrates the interfaces that may be involved in the quick task card setup phase. The following example illustrates the interfaces that may be involved when the electronic device displays the quick task card in an embedded window based on user triggering after the setup is completed.

[0181] When a user triggers the display of an embedded window, the electronic device may be in different states, such as a black screen (or off screen), a screen on and locked, the desktop being displayed, or the interface of any application being displayed. The way to quickly display the window may differ depending on the user's state. Figures 9-14 Several possible ways to trigger the display of an embedded window are shown below.

[0182] like Figure 9 This diagram illustrates the interface of an electronic device transitioning from a black screen to the display of an embedded window. (For example...) Figure 9 As shown in (a), the electronic device has a black screen. When the electronic device receives a double-tap operation on the back, the screen can be turned on to enter the following state: Figure 9 The interface shown in (b) can then be implemented in two possible ways: Implementation 1: If no password is set in the electronic device or the electronic device recognizes a face that can be unlocked, then the electronic device can unlock from, for example... Figure 9 The interface shown in (b) leads to the following: Figure 9 The interface shown in (d). Implementation 2: If the electronic device needs to unlock based on a user-inputted password, then the electronic device can unlock from, for example... Figure 9 The interface shown in (b) first enters as follows: Figure 9As shown in (c), the unlock interface has a layer below it that can display a scaled-down embedded window (e.g., scaled down to 90%). Figure 9 After receiving the correct password, the unlock screen shown in (c) will then proceed to the following... Figure 9 The interface shown in (d) displays an embedded window.

[0183] like Figure 9 The interface shown in (d) can be understood as an embedded window interface. The embedded window can be displayed on top of other applications on the electronic device. The embedded window can have a certain degree of transparency. The embedded window can include a details display area 901 and a taskbar 902.

[0184] The details display area 901 can display a quick task card for a task, and the content of the quick task card can be the detailed page of that task. The taskbar 902 can display icons for multiple tasks, which may include icons and / or text. The order of the multiple task icons can be the same as or different from the order in the previously added bars. The task displayed in the details display area 901 is one of the tasks in the taskbar 902. The icon of the task displayed in the details display area 901 can be distinguished from the icons of other tasks in the taskbar 902 based on color, shape, size, selection indicator, etc.

[0185] like Figure 9 The embedded window shown in (d) can also include an editing control, which allows the user to enter a window such as... Figure 6 The interface for setting up quick task cards shown will not be described in detail here.

[0186] In possible implementations, such as Figure 9 If the interface shown in (d) does not receive any user operation for a period of time, the embedded window can be exited and the electronic device will return to a black screen. This can save power consumption caused by the accidental triggering of the embedded window display.

[0187] like Figure 10 This diagram illustrates the interface of an electronic device transitioning from a lock screen to the display of an embedded window. For example... Figure 10 As shown in (a), the electronic device has its screen on and displays the lock screen interface. When the electronic device receives a double-tap operation on the back, there are two possible implementations: Implementation 1: The electronic device has no password set or the electronic device recognizes a face that can unlock it. In this case, the electronic device can unlock from the following position: Figure 10 The interface shown in (a) leads to the following: Figure 10 The interface shown in (c). Implementation 2: If the electronic device needs to unlock based on a user-inputted password, then the electronic device can unlock from, for example... Figure 10 The interface shown in (a) first enters as follows: Figure 10 The interface shown in (b) is as follows: Figure 10 After receiving the correct password, the interface shown in (b) will then proceed to the following... Figure 10 The interface shown in (c). Possible implementations include, for example... Figure 10 If the interface shown in (c) does not receive any user operation for a period of time, the embedded window can be exited and the electronic device can redisplay the lock screen interface, which can save power consumption caused by accidental triggering of the embedded window display.

[0188] like Figure 11 This diagram illustrates the interface of an electronic device, from the desktop to the display of an embedded window. (For example...) Figure 11 As shown in (a), the electronic device displays the desktop. When the electronic device receives a double-tap operation on the back, the electronic device can move from, as shown in (a). Figure 11 The interface shown in (a) leads to the following: Figure 11 The interface shown in (b). Possible implementations include, for example... Figure 11 If the interface shown in (b) does not receive any user interaction for a period of time, the embedded window can be exited and the electronic device can redisplay the desktop.

[0189] like Figure 12 This diagram illustrates the transition of an electronic device's interface from a video application to a display of an embedded window. (For example...) Figure 12 As shown in (a), the electronic device displays the interface of a video application. When the electronic device receives a double-tap operation on the back, the electronic device can... Figure 12 The interface shown in (a) leads to the following: Figure 12 The interface shown in (b). Wherein, the electronic device displays as... Figure 12 When the interface shown in (b) is used, the video application can continue to play without interruption. After the embedded window is closed, the electronic device continues to display the video being played, thus achieving continuous playback of the video application.

[0190] like Figure 13 This diagram illustrates the interface transition of an electronic device from interface a of application A to the display of an embedded window. (For example...) Figure 13 As shown in (a), the electronic device displays the interface of application A. When the electronic device receives a double-tap operation on the back, the electronic device can... Figure 13 The interface shown in (a) leads to the following: Figure 13 The interface shown in (b) Figure 13 The embedded window shown in (b) can also display other pages corresponding to task a of application A. After the embedded window exits, the electronic device continues to display interface a of application A, without affecting the operation of application A itself. In other words, the embedded window in this embodiment is independent of application A and will not interrupt the operation of application A.

[0191] It should be noted that the above... Figure 9 The interface shown in (d) Figure 10 The interface shown in (c) Figure 11 The interface shown in (b) Figure 12 The interface shown in (b), and Figure 13 The content of the embedded windows in the five interfaces shown in (b) is the same. The difference is that the interface covered by the embedded window is the interface before the embedded window is displayed. Therefore, the content of the embedded windows in the five interfaces can be referenced from each other, and will not be described in detail.

[0192] It is understandable that when an electronic device launches an embedded window, there may be a cold start or loading failure. In this case, after launching the embedded window, the content of the quick task card may not be displayed normally. Before the normal content of the quick task card is displayed, a cold start interface or loading interface may be displayed in the details display area.

[0193] For example, Figure 14 This diagram illustrates the possible interface when an electronic device experiences a cold start or loading failure. Figure 14 (b) can be Figure 9 The interface shown in (d) Figure 10 The interface shown in (c) Figure 11 The interface shown in (b) Figure 12 The interface shown in (b), or Figure 13 The interface shown in (b) is displayed. If the electronic device is cold-started, it will display... Figure 14 Before (b), you can also see, for example Figure 14 (a) shows the cold start interface displayed in the embedded window. If the electronic device fails to load the contents of the quick task card due to poor network or other reasons, the following is displayed: Figure 14 Before (b), you can also see, for example Figure 14 (c) shows an embedded window displaying a loading interface, which may include a loading control. When a trigger is received on the loading control, a process such as... Figure 14 The interface shown in (b).

[0194] It should be noted that, Figure 9 The interface shown in (d) Figure 10 The interface shown in (c) Figure 11 The interface shown in (b) Figure 12 The interface shown in (b) Figure 13 The interface shown in (b), and Figure 14 In the six interfaces shown in (b), the example is the display of the shortcut task card corresponding to task a of application A in the embedded window.

[0195] In a possible implementation, the embedded windows of these six interfaces can also be replaced with any of the following: such as Figure 15 (a) shows the shortcut task card corresponding to task b of application A, such as Figure 15 (b) shows the shortcut task card corresponding to task c of application B, such as Figure 15 (c) shows the shortcut task card corresponding to task d of application B, such as Figure 15 The shortcut task card corresponding to task e of application B is shown in (d).

[0196] When the embedded window of these six interfaces pops up, the first shortcut task card that is displayed may be related to whether the smart switch is turned on or off.

[0197] For example, when the smart recommendation switch is off, the first quick task card displayed when the embedded window pops up can be: the quick task card corresponding to the first task in the added column, or the quick task card corresponding to the task last used by the user, or the quick task card corresponding to any task in the added column.

[0198] When the smart recommendation switch is turned on, the first quick task card displayed when the embedded window pops up can be a quick task card corresponding to a task calculated based on the recommendation algorithm. The recommendation algorithm can be related to the user's travel patterns, current time, geofence, usage habits, and occupation. In a possible implementation, the user's travel patterns, usage habits, and occupation can be obtained from the user profile based on the user's authorization.

[0199] For example, when an electronic device detects that a user is about to depart for another destination based on their travel information, and after detecting a double-tap operation on the back, the first shortcut task card displayed when the embedded window pops up can be the shortcut task card corresponding to the travel task. Figure 15 The shortcut task card corresponding to task e of application B is shown in (d).

[0200] For example, when an electronic device detects that a user needs to clock in based on the current time, and detects a double-click operation on the back, the first shortcut task card displayed when the embedded window pops up can be the shortcut task card corresponding to the clock-in task (not shown in the figure).

[0201] For example, when an electronic device detects a user's upcoming payment based on their current geofence, and detects a double-click on the back of the device, the first shortcut card displayed in the pop-up embedded window could be a shortcut card corresponding to a payment-related task. Figure 14(b) shows the shortcut task card corresponding to task a in application A, or Figure 15 (b) shows the shortcut task card corresponding to task c of application B. Whether it's the shortcut task card corresponding to task a of application A or the shortcut task card corresponding to task c of application B can be determined based on user habits. For example, if a user uses the shortcut task card corresponding to task a of application A more frequently, that shortcut task card can be displayed first; similarly, if a user uses the shortcut task card corresponding to task c of application B more frequently, that shortcut task card can be displayed first.

[0202] For example, when an electronic device detects that a user is about to take the subway or bus based on their current geofence, and detects a double-click on the back of the device, the first shortcut card displayed in the pop-up embedded window can be the shortcut card corresponding to the subway or bus ride code (not shown in the figure). Of course, if the user's occupation is listed as subway worker and they frequently visit subway stations, then the first shortcut card displayed when the user is at the subway station may not be the one corresponding to the subway or bus ride code.

[0203] For example, when an electronic device detects a user's location based on a geofence (such as a parcel locker fence) and detects a double-tap operation on the back of the device, the first shortcut task card displayed in the embedded window can be the shortcut task card corresponding to the scanning task. For example... Figure 15 The shortcut task card corresponding to task b of application A shown in (a), or Figure 15 (c) shows the shortcut task card corresponding to task d of application B. Whether it's the shortcut task card corresponding to task b of application A or the shortcut task card corresponding to task d of application B can be determined based on user habits. For example, if a user uses the shortcut task card corresponding to task b of application A more frequently, it can be displayed first; similarly, if a user uses the shortcut task card corresponding to task d of application B more frequently, it can be displayed first.

[0204] Recommendation algorithms can, of course, be implemented in other ways depending on the specific circumstances, and the embodiments in this application do not impose specific limitations. It should be noted that the acquisition of any data in the embodiments of this application is authorized and compliant.

[0205] After the electronic device displays the first shortcut task card in the embedded window, the embedded window allows the user to switch between shortcut task cards for various tasks.

[0206] In one possible implementation, users can swipe left and right or up and down in the embedded window to switch between quick task cards for adjacent tasks. For example, in Figure 15 When the shortcut task card corresponding to task b of application A shown in (a) receives a right swipe operation, it can enter as follows: Figure 15 (b) shows the shortcut task card corresponding to task c of application B. In such a case... Figure 15 When the shortcut card corresponding to task c in application B shown in (b) receives a right swipe gesture, it can enter, as shown in the image. Figure 15 (c) shows the shortcut task card corresponding to task d of application B. Figure 15 When the shortcut task card corresponding to task d in application B shown in (c) receives a right swipe operation, it can enter as follows: Figure 15 The shortcut task card corresponding to task e of application B is shown in (d). Of course, if in... Figure 15 When the shortcut task card corresponding to task e of application B shown in (d) receives a left swipe operation, it can enter, as shown in the example. Figure 15 The shortcut task card corresponding to task d of application B shown in (c), etc.

[0207] In another possible implementation, the user can trigger any task icon in the taskbar of the embedded window, causing the shortcut task card displayed in the embedded window to switch to the shortcut task card corresponding to the task icon triggered by the user. For example, in Figure 15 When the task bar below the shortcut task card corresponding to task b of application A shown in (a) receives a trigger indicating task c, it can enter as follows: Figure 15 The shortcut task card corresponding to task c of application B shown in (b). Or, in Figure 15 When the task bar below the shortcut task card corresponding to task b of application A shown in (a) receives a trigger indicating task d, it can enter as follows: Figure 15 The shortcut task card corresponding to task d of application B shown in (c). Or, in Figure 15 When the task bar below the shortcut task card corresponding to task b of application A shown in (a) receives a trigger indicating task e, it can enter as follows: Figure 15 (d) shows the shortcut task card corresponding to task e of application B. The shortcut task card displayed in the embedded window can have various interface changes during use. For example, Figures 16-19 Several interface diagrams are shown when using quick task cards.

[0208] It is understood that each task in the embedded window can be associated with the interface of the application to which the task belongs. When a shortcut task card of a task is displayed in the embedded window, the embedded window can launch the task module in the application through the interface of the application associated with the task. Thus, based on the application, the embedded window can provide the specific content displayed on the shortcut task card, and when a trigger is received in the shortcut task card, the application's own execution logic can be used to implement further interface display after being triggered in the shortcut task card. The execution logic of the application itself is not specifically limited in this embodiment of the application.

[0209] Figure 16 This example illustrates the interface changes of a quick task card for payment-related tasks after payment is completed. Figure 16 As shown in (a), the embedded window can display a quick task card for the payment task a in application A, based on the content provided by the module in application A used to implement task a. The quick task card can include a barcode or QR code that can be used for payment or receipt. After the electronic device determines that the barcode or QR code has been scanned and payment or receipt has been completed, it can enter a window based on application A. Figure 16 As shown in (b), the quick task card area can display a notification message indicating payment completion. In one possible implementation, after displaying the notification message, the embedded window can exit, and the electronic device returns to the interface before the embedded window popped up. This allows the embedded window to be used and closed immediately, providing convenient operation without interrupting the user's use of the electronic device.

[0210] Optionally, the quick task card for payment tasks in application A can also include other payment methods and some hidden content, which can also be triggered by the user.

[0211] For example, Figure 17 This diagram illustrates the interface changes when the options in the quick task card for payment tasks are hidden. Figure 17 As shown in (a), the embedded window displays a quick task card for payment task a of application A. The quick task card also includes a barcode, a QR code, payment method a option, and some hidden options, such as... Figure 17 The shortcut task card for task a shown in (a) can also be understood as the root interface.

[0212] When in such Figure 17 When the user swipes up on the quick task card in the interface shown in (a), it can enter as follows: Figure 17 The interface shown in (b) is as follows: Figure 17As shown in (b), the barcode and QR code in the quick task card are moved up, and previously hidden options such as QR code payment, appreciation code and group payment are displayed in the quick task card.

[0213] When in such Figure 17 When the user triggers a group payment request in the interface shown in (b), it can enter the following... Figure 17 The interface shown in (c) is as follows: Figure 17 As shown in (c), the group payment interface is displayed in the quick task card, and the group payment interface can display controls for selecting chat groups.

[0214] When in such Figure 17 When the interface shown in (c) receives a user's trigger operation on the control for selecting a chat group, it can enter as follows: Figure 17 The interface shown in (d) is as follows: Figure 17 As shown in (d), the quick task card displays an interface for selecting chats. This interface can display one or more recently forwarded groups, as well as one or more recently chatted groups. Furthermore, users can... Figure 17 Select a group in the interface shown in (d) to initiate a group payment to the members of that group.

[0215] When in such Figure 17 When the user triggers the back button in the interface shown in (d), the quick task card can first return to, for example, Figure 17 The parent interface of the interface shown in (d), enter as follows Figure 17 The interface shown in (e) Figure 17 The interface shown in (e) can be used with Figure 17 The interface content shown in (c) is the same, so it will not be described again.

[0216] When in such Figure 17 When the user triggers the back button in the interface shown in (e), the quick task card can return to, for example, Figure 17 The parent interface of the interface shown in (e), enter as follows Figure 17 The interface shown in (f) Figure 17 The interface shown in (f) can be used with Figure 17 The interface content shown in (b) is the same, so it will not be described again.

[0217] Understandable Figure 17 The interface shown in (b) is the root interface of the shortcut task card for task a, therefore it does not support going back. Figure 17 If the user triggers the back button in the interface shown in (b), then shaking or other animation effects can be added to the embedded window to prompt the user that the back button can no longer be executed.

[0218] For example, Figure 18 This diagram illustrates the interface changes when the keyboard is displayed in the shortcut task card for travel-related tasks. For example... Figure 18 As shown in (a), the embedded window displays the quick task card for the travel-related task e of application B. The quick task card includes options such as ride QR code, ride mode (such as bus, subway, taxi and cycling), travel discounts, route planning and ride records.

[0219] When in such Figure 18 When a route planning trigger is received in the interface shown in (a), you can enter as follows: Figure 18 The interface shown in (b) is as follows: Figure 18 As shown in (b), the embedded card displays the route planning interface, which may include options such as setting the travel address and trip reminders.

[0220] When in such Figure 18 When the electronic device receives a trigger action from the address input field in the interface shown in (b), if the user has not previously set a travel address, the electronic device can enter the following... Figure 18 The interface shown in (c) is as follows: Figure 18 As shown in (c), the electronic device can pop up a keyboard, and the height of the quick task card can be reduced. The quick task card can also be moved to the top of the electronic device, allowing the user to input travel addresses and other relevant information using the keyboard. After the user finishes using the keyboard, the keyboard display can be further canceled, and the quick task card display can be restored (not shown in the figure), which will not be elaborated further. In this way, when the user triggers route planning again, a route planning interface with the travel address as the destination can be displayed based on the travel address that the user has already entered.

[0221] You may also receive notification messages when an embedded window is displayed. Figure 19 This diagram illustrates the interface changes when receiving notification messages while using quick task cards.

[0222] like Figure 19 As shown in (a), the embedded window displays a shortcut task card for payment task a of application A. If notification message 1 is received, one can access the following... Figure 19 The interface shown in (b) is as follows: Figure 19 The embedded window shown in (b) continues to be displayed, and message 1 can be displayed on top of the embedded window in the form of a banner or capsule.

[0223] In such Figure 19 In the interface shown in (b), if a trigger action to open message 1 is received (such as a pull-down notification or a click notification), one can enter the following... Figure 19 The interface shown in (c) is as follows: Figure 19 As shown in (c), the electronic device can cancel the display of the embedded window and enter the interface corresponding to message 1. Optionally, when returning to the previous page in the interface corresponding to message 1, it can return to the parent interface of message 1 in the application, and the embedded window will no longer be displayed. Of course, it can also return to, for example... Figure 19 The embedded window of (a) is not specifically limited in the embodiments of this application.

[0224] In such Figure 19 In the interface shown in (b), if message 1 is not triggered for a period of time, or if a trigger to close message 1 is received, message 1 can be canceled from display, and the electronic device will continue to display as shown. Figure 19 The interface shown in (a) includes an embedded window. In such... Figure 19 As shown in (a), if the user wants to view the notification messages again, the user can perform a pull-down operation from the top of the screen, etc., to enter the interface. Figure 19 The message notification interface shown in (d) can include multiple messages. An embedded window can also be displayed below the message notification interface. If the user swipes up to collapse the message notification interface, the electronic device can continue to display messages as shown in (d). Figure 19 The interface shown in (a) includes an embedded window. If a trigger action to open message 1 is received among multiple messages, it can also enter the interface shown in (a). Figure 19 The interface of message 1 shown in (c).

[0225] Understandably, if an electronic device receives an incoming call while the embedded window is displayed, the caller information, answer control, and hang-up control can also be displayed in a capsule format on top of the embedded window (not shown in the diagram). If the user triggers the hang-up control, the electronic device hangs up the call, and the embedded window remains displayed. If the user triggers the answer control, the electronic device answers the call, and the embedded window remains displayed, with the call interface displayed in a capsule format; alternatively, the embedded window can be de-displayed, and the electronic device displays the call interface.

[0226] It should be noted that the above examples describe the possible interfaces involved when using quick task cards. In actual applications, quick task cards can also support providing other user interaction interfaces and implementing other tasks, or use other interfaces to implement the above interactions. The above examples do not necessarily limit the use of quick task cards.

[0227] The following will provide examples illustrating the interfaces that may be involved in closing an embedded window.

[0228] In one possible implementation, when an electronic device displays an embedded window, if the electronic device detects that the embedded window has not received a trigger operation within a preset time, the electronic device can close the embedded window. The preset time can be set based on the actual application, for example, it can be set to a shorter time to reduce the interference of the embedded window on the application running on the electronic device.

[0229] The absence of a trigger operation within a preset time period can include: no trigger operation being received within a preset time period starting from when the embedded window first pops up, or no trigger operation being received within a preset time period after completing interactive processes such as scanning a code in the embedded window.

[0230] After the embedded window is closed, the electronic device can revert to the interface displayed before the embedded window popped up. The interface that the electronic device can display before the embedded window popped up can include: a black screen, a sleep screen, a lock screen, the desktop, or the interface of any application.

[0231] For example, Figure 20 This diagram illustrates an interface where an embedded window pops up from interface a of application A, performs a function related to task a of application A within the embedded window, and then closes the embedded window to return to interface a of application A.

[0232] like Figure 20 As shown in (a), the electronic device can display interface a of application A. If the electronic device detects a double-click operation on the back of the electronic device, it can enter... Figure 20 The interface shown in (b) is as follows: Figure 20 As shown in (b), the electronic device displays an embedded window overlaid on the interface a of application A. The embedded window includes a shortcut task card for payment task a of application A. The shortcut task card for task a may include a payment code. When the electronic device detects that the payment code has been scanned and payment has been completed, it may display the following: Figure 20 The interface shown in (c) is as follows: Figure 20 As shown in (c), if the quick task card for task a indicates that payment has been completed, the electronic device can close the embedded window after a preset time and enter the following... Figure 20 The interface shown in (d) restores the display of interface a of application A. Figure 20 The interface shown in (d) can be used with Figure 20 The interface content shown in (a) is the same. Of course, if the electronic device displays as shown in (a), the content is the same. Figure 20 After the interface shown in (b), if no trigger or scan is received in the embedded window after a preset time, the electronic device can also... Figure 20 The interface shown in (b) leads to the point where you can enter... Figure 20 The interface shown in (d) restores the display of interface a of application A.

[0233] In other words, in this embodiment, regardless of the type of interface interaction performed in task a of application A within the embedded window, the electronic device can restore the display of interface a of application A when the embedded window is closed. The embedded window in this embodiment is a newly created task and will not interrupt or affect the tasks of other applications.

[0234] In another possible implementation, the electronic device could also close the embedded window based on user triggering.

[0235] For example, when an electronic device displays an embedded window, if the device receives a user's swipe-up gesture from the bottom of the screen and holds the swipe, the device does not trigger the display of recent tasks but instead closes the embedded window. Alternatively, if the user swipes inward from the side of the screen and holds the swipe, the device does not trigger the sidebar but instead closes the embedded window.

[0236] Alternatively, an embedded window can provide a control for displaying recent tasks. When the user triggers this control, the embedded window can be closed and the recent tasks can be displayed.

[0237] like Figure 21 As shown in (a), the electronic device displays an embedded window, which includes a shortcut task card for task a of application A, and a control for displaying recent tasks. When the user triggers the control for displaying recent tasks, the embedded window can be closed, and access can be made as follows: Figure 21 The interface shown in (b).

[0238] like Figure 21 As shown in (b), a floating window can be displayed in the interface showing recently run tasks. Figure 21 The interface shown in (b) receives a trigger for the most recently run task 1, and can enter as follows: Figure 21 The interface for Task 1 is shown in (c).

[0239] Understandably, if there are no recently run tasks, electronic devices will... Figure 21 When the user triggers the control used to display recent tasks in the interface of (a), the embedded window can be closed and the desktop can be displayed.

[0240] Of course, in another possible implementation, the embedded window can also provide a control for closing the embedded window (not shown in the figure). When the user operates on the control in the embedded window to close the embedded window, the electronic device can restore the interface displayed before the embedded window popped up.

[0241] Alternatively, when an electronic device receives a preset operation such as a press, touch, or swipe on a certain area of ​​the embedded window, it can close the embedded window and restore the interface displayed before the embedded window popped up.

[0242] Alternatively, when an electronic device receives a tap, voice control, gesture control, or other action to close the embedded window, it can close the embedded window and restore the interface that was displayed before the embedded window popped up.

[0243] Alternatively, the electronic device may include functional or physical buttons such as a back button, a desktop button, and a lock screen button. When the electronic device receives a trigger on the back button, it closes the embedded window and restores the interface displayed before the embedded window popped up; when the electronic device receives a trigger on the desktop button, it closes the embedded window and displays the desktop; when the electronic device receives a trigger on the lock screen button, it closes the embedded window and displays the lock screen interface, and so on.

[0244] The embodiments of this application do not limit the specific implementation of closing the embedded window.

[0245] The following is a schematic description of the flowchart of the window display method provided in this application. It should be noted that the phrase "at...time" in this application's embodiments can refer to a moment when a certain situation occurs, or to a period of time after the occurrence of a certain situation; this application's embodiments do not specifically limit this. For example... Figure 22 As shown, the method includes:

[0246] S2201: Display the first interface, which includes the page content corresponding to the first task of the first application.

[0247] The first interface in this application embodiment can be the interface of any application displayed on an electronic device. For example, the first interface can correspond to... Figure 11 of (a) Figure 12 (a) or Figure 13 The interface shown in (a) is as follows.

[0248] The first application can be any application currently displayed on the electronic device, such as a desktop application, video application, or game application installed on the electronic device. The first task of the first application can be any task of the first application, and the page content corresponding to the first task can be provided by the first application. This application embodiment does not limit the specific content displayed on the first interface.

[0249] S2202: First preset operation received.

[0250] In one possible implementation, the first preset operation could be a double-click operation on the back of the electronic device, which is a convenient and easy-to-implement operation for users.

[0251] Of course, the first preset operation can also be any alternative to the double-click back operation described in the above embodiments, which will not be elaborated here.

[0252] S2203: In response to the first preset operation, an embedded window is displayed on the upper layer of the first interface without interrupting the execution of the first task. The embedded window includes the page content corresponding to the second task of the second application.

[0253] The embedded window in this application embodiment can be a system-provided window of the electronic device, independent of the first application and the second application. The function and possible names of the embedded window can be found in the description of the foregoing embodiments, and the specific content of the embedded window can be found in... Figure 9 of (d), Figure 10 (c) Figure 11 of (b) Figure 12 of (b) Figure 13 of (b) Figure 14 (b) or Figure 15 The interfaces shown in (a), (b), (c), and (d) are not described in detail here.

[0254] The operation of an embedded window can be performed without affecting the execution of the primary task. For example, when the primary application includes an application that supports playing video or audio content, the electronic device can continue playing video or audio while the embedded window is displayed, allowing the application that was originally running on the electronic device to continue running.

[0255] The second application can be the same as the first application or a different application. The second task of the second application can be any application within the second application. This application does not specifically limit the second application or the second task.

[0256] In one possible implementation, the electronic device can create a new task for the second application corresponding to the second task in the embedded window, so that the second application can provide the page content corresponding to the second task to the embedded window based on the newly created task, without the electronic device needing to jump to the second application.

[0257] It is understood that even if a second task of a second application is running in an embedded window, and the second application is also running in the background on the electronic device, based on the method of this application embodiment, when the electronic device exits the page displaying the second task of the second application in the embedded window, it can return to the interface remembered before the second application ran in the background, without interrupting the previous operation of the second application. In other words, the task executed by the second application in the embedded window can be independent of the task executed by the second application in the foreground or background of the electronic device.

[0258] S2204: Second preset operation received.

[0259] In this embodiment, the second preset operation can be any operation used to exit the embedded window. For example, refer to... Figure 20 , Figure 21 Or any of the operations described in the above embodiments for exiting the embedded window.

[0260] S2205: In response to the second preset operation, cancel the display of the embedded window and restore the display of the page content corresponding to the first task of the first application.

[0261] In this embodiment of the application, after the embedded window is canceled from display, the electronic device can restore the page content of the application before the embedded window popped up, so that the display of the embedded window does not interfere with the application that was originally running on the electronic device.

[0262] In summary, in this embodiment of the application, an embedded window can be displayed based on user-friendly operation. Some tasks can be provided to the user in the embedded window, so that the user can easily use the tasks in the embedded window. Moreover, the display of the embedded window does not interrupt the application already running on the electronic device, so that the application already running on the electronic device has good continuity, reduces the disturbance to the user's use of the application, and improves the user experience.

[0263] In one possible implementation, the page content corresponding to the second task of the second application is displayed in the first area of ​​the embedded window. The embedded window also includes a second area. Above the first interface, the second area of ​​the embedded window also displays: a first icon corresponding to the second task and a second icon corresponding to the third task; wherein the first icon is selected and the second icon is unselected.

[0264] In this embodiment, the first area can be understood as the area displaying quick task cards (i.e., the specific page content corresponding to the task), and the second area can be understood as the area displaying multiple task icons. These task icons can be user-defined, or they can be default or recommended by the electronic device. The task icon can be a task icon. The task currently displaying a quick task card can be in a selected state in the second area, while other task icons not displaying quick task cards can be in an unselected state. The selected task icon can be distinguished from the unselected icon by color, font, animation effects, etc.

[0265] The content displayed in the first and second areas of the embedded window can be referenced. Figure 9 of (d), Figure 10 (c) Figure 11 of (b) Figure 12 of (b) Figure 13 of (b) Figure 14 (b) or Figure 15 The interfaces shown in (a), (b), (c), and (d) are not described in detail here.

[0266] In one possible implementation, before receiving the second preset operation, the method further includes: receiving a third preset operation in the embedded window to switch the second task to the third task; in response to the third preset operation, displaying the interface content corresponding to the third task in a first area of ​​the embedded window, and displaying a first icon and a second icon in a second area of ​​the embedded window; wherein the first icon is in an unselected state and the second icon is in a selected state.

[0267] In this embodiment, the third task can be a task of the first application, a task of the second application, or a task of the third application. That is, the embedded window can display multiple tasks of one application, or multiple tasks of multiple applications. This allows users to utilize different tasks of different applications based on the embedded window, increasing the richness and convenience of use.

[0268] The third preset action for switching from the second task to the third task can be a swipe gesture or an action that triggers the task icon in the second area. See the attached document for details. Figure 15 The corresponding descriptions will not be elaborated here.

[0269] In one possible implementation, after displaying the interface content corresponding to the third task in the first area of ​​the embedded window, the method further includes: receiving an upward swipe operation in the first area of ​​the embedded window; responding to the upward swipe operation, displaying a first button in the first area of ​​the embedded window; and when a trigger operation is received on the first button, displaying the page content associated with the first button in the third task in the first area of ​​the embedded window.

[0270] In this embodiment, the embedded window can support displaying a portion of the task's page. Hidden content not displayed on the page can be revealed via an upward swipe. Buttons in the embedded window can also allow users to navigate to the next or multiple levels of pages, thus enriching the content of the embedded window and enabling users to access more services based on it. For details, please refer to... Figure 17 Based on the descriptions in (a) and (b), the first button can correspond to Figure 17 The "group payment" feature will not be elaborated upon here.

[0271] In one possible implementation, the first button includes a second button in the page content associated with the third task. The method further includes: when a trigger operation on the second button is received, restoring the display of the interface content corresponding to the first task in the first area of ​​the embedded window.

[0272] In this embodiment, the second button can refer to the back button. The embedded window can also support returning to the previous interface based on triggering the back button. For details, please refer to... Figure 17 The descriptions of (d), (e) and (f) will not be repeated here.

[0273] In one possible implementation, the page content corresponding to the second task of the second application includes a third button, and the method further includes: when a trigger is received on the third button, displaying an input box in an embedded window; when a trigger is received on the input box, displaying a keyboard; and displaying the input content received from the keyboard in the input box.

[0274] In this embodiment, the embedded window can support keyboard input, allowing users to input information conveniently when using the embedded window. See details for further information. Figure 18 Based on the descriptions in (a), (b), and (c), the third button can correspond to... Figure 18 The input boxes in the text will not be described in detail here.

[0275] In one possible implementation, after the embedded window is displayed on top of the first interface, the process further includes: receiving a notification message; continuing to display the embedded window, and displaying the notification message in the form of a capsule or banner on top of the embedded window.

[0276] In this embodiment, if a notification message is received while the embedded window is being displayed, the embedded window can continue to be displayed, and the notification message can be displayed on top of the embedded window in the form of a capsule or banner. This allows the user to see the notification message instantly while using the embedded window. For details, please refer to... Figure 19 The descriptions of (a), (b), (c) and (d) will not be repeated here.

[0277] In one possible implementation, the method further displays a second interface, which includes a first switch; when a trigger operation to turn on the first switch is received, a third interface is displayed, which includes an added column and a not added column. The added column includes identifiers of one or more user-defined tasks, and the not added column includes identifiers of one or more tasks provided by the electronic device that have not been added by the user; when an operation to delete a first target task from the added column is received, the display of the identifier of the first target task is canceled in the added column, and the identifier of the first target task is displayed in the not added column; or, when an operation to add a second target task from the not added column is received, the display of the identifier of the second target task is canceled in the not added column, and the identifier of the second target task is displayed in the added column.

[0278] The second interface can be a display of the main switch, for example, it can correspond to... Figure 6(a) The third interface can be a task setting interface, for example, it can correspond to... Figure 6 (b) The first target task can be any task in the "Added" column, and the second target task can be any application already installed on the electronic device in the "Not Added" column. For specific setup instructions, please refer to [link / reference]. Figure 6 or Figure 7 The description is omitted here. This allows users to easily customize the tasks they need.

[0279] In one possible implementation, the "Not Added" column includes an identifier for a third target task, the application corresponding to which the third target task is not installed on the electronic device. The method further includes: when an operation to add the third target task from the "Not Added" column is received, displaying a prompt message to prompt the user to install the application corresponding to the third target task.

[0280] In this embodiment, when a user selects a task for an application that is not installed on the electronic device, the electronic device can prompt the user to install the application. This allows the user to customize a wide range of tasks, not limited to the applications already installed on the electronic device. The third target task could, for example, correspond to... Figure 6 "Task f".

[0281] In one possible implementation, the third interface also includes a second switch, and the method further includes: when a trigger operation to turn on the second switch is received, displaying a recommendation icon in the blank area of ​​the added column.

[0282] The second switch in this embodiment can correspond to the smart recommendation switch in the above embodiment. When the smart recommendation switch is turned on, if the number of tasks in the added column has not reached the maximum number of tasks that can be displayed, a recommendation icon can be displayed in the added column. The recommendation icon can be a dotted frame and / or text, etc. For details, please refer to... Figure 7 The interface will not be described in detail here.

[0283] After the smart recommendation switch is turned on, if the user triggers the display of an embedded window on the electronic device, the task corresponding to the first quick task card displayed in the embedded window can be obtained based on the recommendation algorithm.

[0284] For example, in one possible implementation, an embedded window is displayed on top of the first interface. The embedded window includes page content corresponding to the second task of the second application, including: in response to a first preset operation, when it is determined that the second switch is in the on state, determining the second task of the second application based on a recommendation algorithm, wherein the recommendation algorithm is related to one or more of the following: time information, the geofence where the user is located, or user-related information in the user profile; and displaying the embedded window on top of the first interface, the embedded window including the page corresponding to the second task of the second application.

[0285] For example, determining the second task of a second application based on a recommendation algorithm includes: when the recommendation algorithm determines that a user will travel, determining the second task of the second application as a travel-related task; or, when the recommendation algorithm determines that a user will check in, determining the second task of the second application as a check-in-related task; or, when the recommendation algorithm determines that a user will make a payment, determining the second task of the second application as a payment-related task; or, when the recommendation algorithm determines that a user will take a ride, determining the second task of the second application as a ride code-related task.

[0286] The recommendation algorithm described in this application can be found in the foregoing embodiments and will not be repeated here. In this way, electronic devices can recommend suitable quick task cards to users based on the user's current scenario, thereby improving the user experience.

[0287] In one possible implementation, when the electronic device receives a first preset operation while the screen is off or in a black screen state, the display of the electronic device is turned on; a lock screen interface is displayed, the lower layer of which includes an embedded window; when the correct unlock input is received in the lock screen interface, the embedded window is displayed.

[0288] In this embodiment, the electronic device can display an embedded window from a black screen or screen-off state based on a simple user trigger. For details, please refer to... Figure 9 The description of that is omitted here.

[0289] In one possible implementation, the method further includes: when the electronic device receives a first preset operation while the screen is on and locked, displaying a lock screen interface, the lower layer of which includes an embedded window; and when the correct unlock input is received in the lock screen interface, displaying the embedded window.

[0290] In this embodiment, the electronic device can display an embedded window from a screen-on / screen-locked state based on a simple user trigger. For details, please refer to... Figure 10 The description of that is omitted here.

[0291] The window display method of the present application embodiments has been described above. The apparatus for performing the above window display method provided in the present application embodiments will now be described. Those skilled in the art will understand that the methods and apparatus can be combined with and referenced by each other, and the related apparatus provided in the present application embodiments can perform the steps in the above window display method.

[0292] To achieve the above functions, the device for displaying the window includes hardware structures and / or software modules corresponding to the execution of each function. Those skilled in the art will readily recognize that, based on the method steps of the examples described in conjunction with the embodiments disclosed herein, this application can be implemented in hardware or a combination of hardware and computer software. Whether a function is executed in hardware or by computer software driving hardware depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of this application.

[0293] This application embodiment can divide the apparatus for implementing the window display method into functional modules based on the above method example. For example, each function can be divided into its own functional module, or two or more functions can be integrated into one processing module. The integrated module can be implemented in hardware or as a software functional module. It should be noted that the module division in this application embodiment is illustrative and only represents one logical functional division; other division methods may be used in actual implementation.

[0294] like Figure 23 This is a schematic diagram of a chip structure provided in an embodiment of this application. The chip 2300 includes one or more processors 2301, communication lines 2302, communication interfaces 2303, and memory 2304.

[0295] In some implementations, memory 2304 stores elements such as executable modules or data structures, or subsets thereof, or extended sets thereof.

[0296] The methods described in the embodiments of this application can be applied to, or implemented by, processor 2301. Processor 2301 may be an integrated circuit chip with signal processing capabilities. During implementation, each step of the above methods can be completed by integrated logic circuits in the hardware of processor 2301 or by instructions in software form. Processor 2301 may be a general-purpose processor (e.g., a microprocessor or conventional processor), a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA), or other programmable logic devices, discrete gates, transistor logic devices, or discrete hardware components. Processor 2301 can implement or execute the various processing-related methods, steps, and logic block diagrams disclosed in the embodiments of this application.

[0297] The steps of the method disclosed in the embodiments of this application can be directly implemented by a hardware decoding processor, or implemented by a combination of hardware and software modules in the decoding processor. The software modules can be located in mature storage media in the art, such as random access memory, read-only memory, programmable read-only memory, or electrically erasable programmable read-only memory (EEPROM). This storage medium is located in memory 2304, and processor 2301 reads information from memory 2304 and, in conjunction with its hardware, completes the steps of the above method.

[0298] The processor 2301, memory 2304 and communication interface 2303 can communicate with each other through communication line 2302.

[0299] In the above embodiments, the instructions stored in the memory for execution by the processor can be implemented in the form of a computer program product. This computer program product can be pre-written into the memory, or it can be downloaded and installed into the memory as software.

[0300] This application also provides a computer program product including one or more computer instructions. When the computer program instructions are loaded and executed on a computer, all or part of the flow or function according to the embodiments of this application is generated. The computer may be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer instructions may be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another. For example, computer instructions may be transmitted from one website, computer, server, or data center to another website, computer, server, or data center via wired (e.g., coaxial cable, fiber optic, digital subscriber line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) means. The computer-readable storage medium may be any available medium that a computer can store or a data storage device such as a server or data center that integrates one or more available media. For example, available media may include magnetic media (e.g., floppy disk, hard disk, or magnetic tape), optical media (e.g., digital versatile disc (DVD)), or semiconductor media (e.g., solid-state disk (SSD)).

[0301] This application also provides a computer-readable storage medium. The methods described in the above embodiments can be implemented, in whole or in part, by software, hardware, firmware, or any combination thereof. The computer-readable medium may include computer storage media and communication media, and may also include any medium capable of transferring a computer program from one place to another. The storage medium can be any target medium accessible by a computer.

[0302] As one possible design, computer-readable media may include compact disc read-only memory (CD-ROM), RAM, ROM, EEPROM, or other optical disc storage; computer-readable media may also include disk storage or other disk storage devices. Furthermore, any connecting cable may also be appropriately referred to as computer-readable media. For example, if software is transmitted from a website, server, or other remote source using coaxial cable, fiber optic cable, twisted pair, DSL, or wireless technologies such as infrared, radio, and microwave, then coaxial cable, fiber optic cable, twisted pair, DSL, or wireless technologies such as infrared, radio, and microwave are included in the definition of media. As used herein, disks and optical discs include optical discs (CD), laser discs, optical discs, digital versatile discs (DVD), floppy disks, and Blu-ray discs, where disks typically reproduce data magnetically, while optical discs optically reproduce data using lasers.

[0303] This application describes embodiments with reference to flowchart illustrations and / or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of this application. It should be understood that each block of the flowchart illustrations and / or block diagrams, and combinations of blocks in the flowchart illustrations and / or block diagrams, can be implemented by computer program instructions. These computer program instructions can be provided to a processing unit of a general-purpose computer, special-purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processing unit of the computer or other programmable data processing apparatus, generate instructions for implementing the flowchart illustrations. Figure 1 One or more processes and / or boxes Figure 1 A device that provides the functions specified in one or more boxes.

Claims

1. A window display method, applied to an electronic device, characterized in that, include: Display a first interface, which includes the page content corresponding to the first task of the first application; Received the first preset operation; In response to the first preset operation, a new task is created for the second application, and an embedded window is displayed on the upper layer of the first interface without interrupting the execution of the first task. The embedded window includes the page content corresponding to the second task of the second application. The embedded window is not a window of the second application. The embedded window is an independent window provided by the system of the electronic device. Received the second preset operation; In response to the second preset operation, the display of the embedded window is canceled, and the page content corresponding to the first task of the first application is restored. The first application includes applications that support playing video or audio content, and the electronic device keeps the first application playing video or audio while the embedded window is displayed on the electronic device.

2. The method according to claim 1, characterized in that, The page content corresponding to the second task of the second application is displayed in the first area of ​​the embedded window. The embedded window also includes a second area, which is above the first interface. The second area of ​​the embedded window also displays: a first icon corresponding to the second task and a second icon corresponding to the third task; wherein the first icon is selected and the second icon is unselected.

3. The method according to claim 2, characterized in that, Before receiving the second preset operation, the method further includes: A third preset operation for switching the second task to the third task is received in the embedded window; In response to the third preset operation, the page content corresponding to the third task is displayed in the first area of ​​the embedded window, and the first icon and the second icon are displayed in the second area of ​​the embedded window; wherein the first icon is in an unselected state, and the second icon is in a selected state.

4. The method according to claim 3, characterized in that, After displaying the page content corresponding to the third task in the first area of ​​the embedded window, the method further includes: An upward swipe operation is received in the first area of ​​the embedded window; In response to the swipe-up operation, a first button is displayed in the first area of ​​the embedded window; When a trigger operation is received for the first button, the page content associated with the first button in the third task is displayed in the first area of ​​the embedded window.

5. The method according to claim 4, characterized in that, The first button includes a second button in the page content associated with the third task, and the method further includes: When a trigger operation is received on the second button, the page content corresponding to the first task is restored to be displayed in the first area of ​​the embedded window.

6. The method according to any one of claims 2-5, characterized in that, The third task is either the task of the first application, the task of the second application, or the task of the third application.

7. The method according to any one of claims 1-5, characterized in that, The second task of the second application includes a third button in the page content, and the method further includes: When a trigger is received on the third button, an input box is displayed in the embedded window; When a trigger is received on the input box, the keyboard is displayed; The input received from the keyboard is displayed in the input box.

8. The method according to any one of claims 1-5, characterized in that, After displaying the embedded window on top of the first interface, it also includes: Received notification message; The embedded window continues to be displayed, and the notification message is displayed on top of the embedded window in the form of a capsule or banner.

9. The method according to any one of claims 1-5, characterized in that, The method further includes: The second interface is displayed, and the second interface includes the first switch; When a trigger operation to turn on the first switch is received, a third interface is displayed. The third interface includes an added column and an unadded column. The added column includes identifiers of one or more tasks added by the user. The unadded column includes identifiers of one or more tasks provided by the electronic device that have not been added by the user. When an operation to delete the first target task in the added column is received, the display of the first target task's identifier is removed from the added column, and the identifier of the first target task is displayed in the unadded column; Alternatively, when an operation to add a second target task to the unadded column is received, the display of the identifier of the second target task in the unadded column is canceled, and the identifier of the second target task is displayed in the added column.

10. The method according to claim 9, characterized in that, The "not added" field includes an identifier for a third target task, the application corresponding to which the third target task is not installed on the electronic device, and the method further includes: When an operation to add a third target task from the "not added" column is received, a prompt message is displayed, which prompts the user to install the application corresponding to the third target task.

11. The method according to claim 9, characterized in that, The third interface further includes a second switch, and the method further includes: When a trigger operation to turn on the second switch is received, a recommendation icon is displayed in the blank area of ​​the added column.

12. The method according to claim 11, characterized in that, In response to the first preset operation, an embedded window is displayed on top of the first interface. The embedded window includes page content corresponding to the second task of the second application, including: In response to the first preset operation, when it is determined that the second switch is in the on state, the second task of the second application is determined based on the recommendation algorithm, wherein the recommendation algorithm is related to one or more of the following: time information, geofence where the user is located, or user-related information in the user profile; An embedded window is displayed on top of the first interface, and the embedded window includes the page corresponding to the second task of the second application.

13. The method according to claim 12, characterized in that, The second task of the second application is determined based on the recommendation algorithm, including: When it is determined based on the recommendation algorithm that a user will travel, the second task of the second application is determined to be a travel-related task. Alternatively, when it is determined based on the recommendation algorithm that a user will check in, the second task of the second application is determined to be a check-in type task; Alternatively, when it is determined based on the recommendation algorithm that a user will make a payment, the second task of the second application is determined to be a payment-related task; Alternatively, when it is determined based on the recommendation algorithm that a user will take a ride, the second task of the second application is determined to be a ride code-type task.

14. The method according to any one of claims 1-5 and 10-13, characterized in that, The method further includes: When the electronic device receives the first preset operation while the screen is off or in a black-screen or screen-off state, the display screen of the electronic device is turned on; Display a lock screen interface, the lower layer of which includes the embedded window; When the correct unlock input is received in the lock screen interface, the embedded window is displayed.

15. The method according to any one of claims 1-5 and 10-13, characterized in that, The method further includes: When the electronic device receives the first preset operation while the screen is on and locked, it displays the lock screen interface, the lower layer of which includes the embedded window; When the correct unlock input is received in the lock screen interface, the embedded window is displayed.

16. The method according to any one of claims 1-5 and 10-13, characterized in that, The receipt of the first preset operation includes: A double-click operation on the back of the electronic device was received.

17. An electronic device, characterized in that, include: A memory and a processor, the memory for storing a computer program and the processor for executing the computer program to perform the method as claimed in any one of claims 1-16.

18. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores instructions that, when executed, cause a computer to perform the method as described in any one of claims 1-16.

19. A computer program product, characterized in that, Includes a computer program that, when run, causes an electronic device to perform the method as described in any one of claims 1-16.

Images