Display method and electronic device

Abstract

A display method and an electronic device, relating to the technical field of terminals. The method comprises: displaying a first interface, the first interface comprising an icon of a first application and a first button; in response to a first operation, displaying a second interface, the second interface comprising the icon of the first application, a second button and a third button; in response to a second operation, displaying a third interface, the third interface comprising a first window of the first application; in response to a third operation, displaying a fourth interface, the fourth interface comprising the first window and an icon of at least one recommended task group; and in response to a fourth operation, displaying a fifth interface, wherein the fifth interface comprises the first window and a second window of a second application, an icon of a first recommended task group comprises an identifier of the first application and an identifier of the second application, and the position of the first window in the fifth interface is different from the position of the first window in the third interface. In this way, a plurality of applications can be quickly started and laid out, thereby improving the human-computer interaction efficiency.

Description

A display method and an electronic device Technical Field

[0001] This application relates to the field of terminal technology, and in particular to a display method and an electronic device. Background Technology

[0002] When using electronic devices such as mobile phones and tablets, there may be a need to run multiple tasks simultaneously. For example, when playing a game and chatting with a friend at the same time, the electronic device needs to run the game application and the social chat application in the foreground in parallel.

[0003] In existing technologies, the user operations required to run multiple tasks are complex and the human-computer interaction efficiency is low. For example, when using the split-screen function to run multiple tasks, the user must first find and launch one application to start one task, then find and launch another application to start another task. After starting two tasks, the user must also manually adjust the position and size of each task window to achieve a suitable layout. Summary of the Invention

[0004] This application provides a display method and electronic device that can display recommended task groups. When a user selects a recommended task group, it is equivalent to selecting multiple tasks and a display layout for multiple tasks, thereby enabling the rapid launch and layout of multiple tasks and improving human-computer interaction efficiency.

[0005] To achieve the above objectives, this application adopts the following technical solution:

[0006] Firstly, a display method is provided, the method comprising:

[0007] A first interface is displayed, including a first taskbar containing an icon for a first application and a first button. In response to a first operation, a second interface is displayed, including a second taskbar containing an icon for the first application, a second button, and a third button. The first operation includes an operation on the first button. The first and second taskbars can be different taskbars or two different states of the same taskbar. The first and second buttons can be different buttons or different states of the same button. In response to a second operation, a third interface is displayed, including a first window of the first application and a second taskbar. The window size of the first window is smaller than the window size of the full-screen display window of the first application. The second operation includes an operation on the icon of the first application. In response to a third operation, a fourth interface is displayed, including a first window, icons for at least one recommended task group, and a second taskbar. Each recommended task group icon includes the identifiers of at least two applications, and each recommended task group icon includes the identifier of the first application. The third operation includes an operation on the third button. In response to the fourth operation, a fifth interface is displayed. The fifth interface includes a first window and a second window of the second application. The fourth operation includes an operation on the icon of the first recommended task group. The icon of the first recommended task group includes the identifier of the first application and the identifier of the second application. The position of the first window in the fifth interface is different from the position of the first window in the third interface.

[0008] The first button mentioned above can also be called the mode switch button for the first state, the second button can also be called the mode switch button for the second state, and the third button can also be called the layout button. The full-screen window can also be called the full-screen interface or the maximized window.

[0009] For example, the first interface is interface 101 as shown in Figure 1 below, the first taskbar is the bottom taskbar of interface 101, the icon of the first application in the first taskbar is icon 1013 of APP-1 in interface 101, and the first button is button 1011 in interface 101. The first operation includes operating on button 1011. The second interface is interface 301 as shown in Figure 3 below, the second taskbar is taskbar 3013 in interface 301, the icon of the first application in the second taskbar can be icon 3012 of APP-1 in interface 301, the second button is button 1012 in interface 301, and the third button is button 3011 in interface 301. The second operation includes operating on icon 3012 in interface 301. The third interface can be interface 401 as shown in Figure 4 below, the first window is floating window 4011 in interface 401. The third operation includes operating on button 3011 in interface 401. The fourth interface can be an interface including a task group list, such as interface 2001 shown in Figure 20A, interface 2011 shown in Figure 20B, interface 2201 shown in Figure 22A, and interface 2211 shown in Figure 22B. Taking interface 2001 shown in Figure 20A as an example, the icon of at least one recommended task group can be multiple icons such as recommended task group 20011a, recommended task group 20011d, and recommended task group 20011b in the task group list 20011. The fourth operation can include operations on the icon of any recommended task group in the recommended task group list 20011. Taking recommended task group 20011b as an example, the fifth interface can be interface 1101 shown in Figure 11 below, and the window of the second application can be window 5011 or window 5012 in interface 1101. Taking any recommended task group icon as recommended task group 20011a as an example, the fifth interface can be interface 2301 as shown in Figure 23A below, and the window of the second application can be window 5012 in interface 2301.

[0010] Using the solution of this application, after the first operation, the display mode of the electronic device can be switched from the second mode (also known as the non-free screen mode) to the first mode (also known as the free screen mode). In the first mode, the electronic device can display the application interface of the launched application in a non-full-screen format (such as the first window format). Furthermore, in the first mode, the electronic device can also display icons for recommended task groups. In response to the user's selection of any recommended task group icon, the electronic device can quickly arrange at least two applications, including the currently displayed application. This eliminates the need for the user to search for and launch applications, or adjust the layout of multiple application interfaces, allowing for efficient launch and arrangement of multiple application interfaces, thus improving human-computer interaction efficiency.

[0011] It should be noted that the first interface includes a first taskbar, which can mean that the first taskbar is displayed within the first interface; it can also mean that the first taskbar is displayed in response to a user's operation on the first interface (such as a pull-down operation from the top of the interface); or it can mean that part of the content of the first taskbar is displayed within the first interface, such as the icon of the first application being displayed on the first interface, while other content, such as the first button, is displayed only after the user's operation on the first interface. The same applies to the second and third interfaces including a second taskbar; it can mean that the second taskbar is displayed within the second and third interfaces; it can also mean that the second taskbar is displayed in response to a user's operation on the second and third interfaces; or it can mean that part of the content of the second taskbar is displayed within the second and third interfaces, such as the icon of the first application being displayed on the second and third interfaces, while other content, such as the second button and the third button, is displayed only after the user's operation on the second and third interfaces. This application does not impose specific limitations on this.

[0012] In one possible design approach of the first aspect, the layout of the first window and the second window in the fifth interface is the same as the layout of the icons of the first application and the second application in the first recommended task group. Specifically, "the same layout" means that the position of the first window relative to the screen is the same as the position of the first application icon relative to the first recommended task group icon, and the position of the second window relative to the screen is the same as the position of the second application icon relative to the first recommended task group icon.

[0013] Using this design approach, electronic devices can display a window layout consistent with the application icons in the recommended task group. This allows users to clearly see the application layout through the icons in the recommended task group, providing a WYSIWYG experience and facilitating accurate selection of the desired application and layout, further improving interaction efficiency.

[0014] In one possible design approach of the first aspect, the second interface includes an icon and wallpaper image for the third application, with the third application's icon displayed outside the second taskbar. The third interface includes the wallpaper image but does not include the third application's icon.

[0015] For example, the second interface can be interface 301 as shown in Figure 3 below, the second taskbar can be taskbar 3013 in interface 301, the icons of the third application can be browser icon 3014, email icon 3015, etc. in interface 301, and the wallpaper image can be the diagonal stripes in interface 301. The third interface can be interface 401 as shown in Figure 4 below. Interface 401 also includes diagonal stripes, but the area outside the second taskbar does not include browser or email icons.

[0016] Using this design approach, in the first mode, before displaying the first window (which can also be understood as before displaying a non-full-screen window of an application), the electronic device can display application icons in an area outside the second taskbar so that the user can trigger the launch of the corresponding application. The electronic device can also display a wallpaper image. After displaying a non-full-screen window of an application, the electronic device does not display icons in the area outside the second taskbar, which reduces the power consumption of the electronic device. However, the electronic device still displays the wallpaper image to clearly indicate that it is still on the desktop.

[0017] In one possible design approach of the first aspect, the fifth interface includes a second taskbar. After displaying the fifth interface, the method further includes: in response to a fifth operation, displaying a sixth interface, the sixth interface including a first taskbar, and the sixth interface also including a full-screen window of the first application or a full-screen window of the second application, the fifth operation including an operation on a second button.

[0018] For example, the fifth interface can be an interface including at least two windows, such as interface 2301 shown in Figure 23A, interface 1101 shown in Figure 11, interface 501 shown in Figure 5, and interface 711 shown in Figure 7B. These at least two windows can be obtained by the electronic device according to any recommended task group layout. Taking interface 501 as an example, the second taskbar can be the bottom taskbar of interface 501. The fifth operation includes operating on button 1012 in the bottom taskbar of interface 501. The sixth interface can be interface 801 shown in Figure 8 or interface 601 shown in Figure 6A. Taking interface 801 as an example, the full-screen display window of the first application can be the full-screen display window of APP-3 in interface 801. Taking interface 601 as an example, the full-screen display window of the first application can be the full-screen display window of APP-1 in interface 601.

[0019] Using this design, after the fifth operation, the electronic device's display mode can switch from the first mode to the second mode. When multiple applications are displayed in non-full-screen windows in the first mode, switching to the second mode allows the electronic device to display the full-screen interface of one of the applications. This makes it convenient for the user to operate one application after switching to the second mode.

[0020] Additionally, after switching to the second mode, users can view and launch other applications that are not displaying full-screen windows through the multitasking management interface. This allows users to quickly launch all applications launched in the first mode.

[0021] In one possible design approach in the first aspect, the sixth interface does not include wallpaper images.

[0022] For example, the sixth interface can be interface 801 as shown in Figure 8 below or interface 601 as shown in Figure 6A. Neither interface 801 nor interface 601 includes a wallpaper image, such as a diagonal stripe.

[0023] Using this design approach, in the sixth interface, the electronic device displays a full-screen interface of an application, and consequently, the wallpaper image cannot be displayed.

[0024] In one possible design of the first aspect, after displaying the sixth interface, the method further includes: in response to the sixth operation, displaying a seventh interface, the seventh interface including a second taskbar and a first window, the seventh interface not including the second window, and the sixth operation including an operation on a first button in the first taskbar.

[0025] For example, the sixth interface can be an interface including a full-screen display window in the second mode, such as interface 801 shown in Figure 8 below, interface 601 shown in Figure 6A below, etc., and this interface is the interface after switching from the first mode, which includes multiple non-full-screen windows (such as interface 501 shown in Figure 5, interface 711 shown in Figure 7B, interface 1101 shown in Figure 11, etc.), to the second mode. Taking interface 601 shown in Figure 6A as an example, the first taskbar can be the bottom taskbar 6011 in interface 601, and the sixth operation includes operating on button 1011 in the bottom taskbar 6011 of interface 601. The seventh interface can be interface 611 shown in Figure 6B below, the second taskbar can be the bottom taskbar 3013 in interface 611, and the first window can be window 6111 of APP-1 in interface 611.

[0026] Using this design, after the sixth operation, the electronic device's display mode can switch from the second mode to the first mode. When an application's full-screen window is displayed in the second mode, switching to the first mode allows the electronic device to display a non-full-screen window of that application. This allows for convenient simultaneous display of multiple applications' non-full-screen windows after switching to the first mode.

[0027] In one possible design approach of the first aspect, the fourth interface also includes an icon for at least one layout template, each layout template icon including at least two task areas.

[0028] For example, the fourth interface can be interface 2201 shown in Figure 22A and interface 2211 shown in Figure 22B. Taking interface 2211 as an example, interface 2211 includes both a task group list 22111b and a template list 22111a. The icons of each layout template in template list 22111a include at least two task areas, such as the icon of the first layout template including two vertical task areas, the icon of the second layout template including three vertical task areas, and so on.

[0029] Using this design approach, electronic devices can display layout template icons, allowing users to quickly arrange the currently displayed application interface. This eliminates the need for users to adjust each non-full-screen window individually, enabling rapid layout.

[0030] In one possible design approach of the first aspect, in response to a third operation, displaying a fourth interface includes: in response to an operation on a third button, displaying an eighth interface, the eighth interface including an icon of at least one layout template and a fourth button, each layout template icon including at least two task areas. The fourth button may also be referred to as a recommended task group label. In response to an operation on the fourth button, the fourth interface is displayed.

[0031] For example, the third interface can be interface 401 shown in Figure 4, interface 501 shown in Figure 5, interface 611 shown in Figure 6B, etc., which include at least one non-full-screen window in the first mode. Taking interface 401 as an example, the third button can be button 3011 in interface 401, and the eighth interface can be interface 1901 shown in Figure 19, which includes a template list 10011 but does not include a task group list. The icons of each layout template in the template list 10011 include at least two task areas, such as layout template 10011a including two vertical task areas, layout template 10011b including one vertical task area and two horizontal task areas, etc. The fourth button can be "Smart Recommendation" in interface 1901. The fourth interface can be interface 2201 shown in Figure 22A, interface 2211 shown in Figure 22B, etc.

[0032] Using this design approach, electronic devices can first display the icons of the layout template, and then, in response to the user's action on the fourth button, display the icons of the recommended task group. This reduces the amount of content displayed simultaneously on the interface, simplifying it. Furthermore, if the layout template cannot meet the user's layout needs, the user can further trigger the display of the recommended task group icons, making the interface design more user-friendly and hierarchical.

[0033] In one possible design of the first aspect, the second taskbar in the third interface includes an icon for the fourth application. After displaying the third interface, the method further includes: in response to a seventh operation, displaying a ninth interface, the ninth interface including the second taskbar, a first window, and a third window for the fourth application, the seventh operation including an operation on the icon of the fourth application. In response to an eighth operation, displaying a tenth interface, the tenth interface including the first window and the third window, the eighth operation including an operation on a third button in the second taskbar, the position of the first window in the ninth interface being different from the position of the first window in the tenth interface, and the position of the third window in the ninth interface being different from the position of the third window in the tenth interface.

[0034] For example, the third interface can be interface 401 as shown in Figure 4 below, the second taskbar can be the bottom taskbar in interface 401, and the icons of the second application can be the icons of APP-2 and APP-3 in the bottom taskbar. The ninth interface can be interface 501 as shown in Figure 5 below. The first window can be window 4011 in interface 501, and the third window of the fourth application can be windows 5011 and 5012 in interface 501. The third button can be button 3011 in interface 501. The tenth interface can be interface 1101 as shown in Figure 11 below and interface 2401 as shown in Figure 24A below.

[0035] Using this design approach, in the first mode, when multiple applications' non-full-screen windows are displayed, a rapid layout of these windows can be achieved after the eighth operation. This eliminates the need for users to adjust each application's interface individually or select a layout template, thus achieving efficient layout and improving human-computer interaction efficiency.

[0036] In one possible design approach of the first aspect, in response to an eighth operation, displaying a tenth interface includes: in response to an operation on a third button, displaying an eleventh interface, the eleventh interface including an icon for at least one layout template and a fifth button, each layout template icon including at least two task areas. The fifth button may also be referred to as a one-click layout button. In response to an operation on the fifth button, the tenth interface is displayed.

[0037] For example, the eleventh interface can be interface 1001 as shown in Figure 10 below, and the fifth button can be "One-click layout" in interface 1001.

[0038] Using this design approach, the electronic device can first display a layout template, and then, in response to the user's operation of the fifth button, arrange the non-full-screen windows of multiple applications. In this way, the electronic device can provide the user with a clear layout style by displaying the layout template. If the user finds it difficult to choose from the layout templates, the electronic device can intelligently complete the layout for the user by operating the fifth button, resulting in an interface design that better meets user needs.

[0039] In one possible design approach of the first aspect, after displaying the second interface, the method further includes: in response to a ninth operation, displaying a twelfth interface, the twelfth interface including an icon of at least one layout template, each layout template icon including at least two task areas, the ninth operation including an operation on a third button. In response to an operation on the icon of the first layout template, displaying a thirteenth interface, the thirteenth interface including a first display area and a second display area, each display area including at least two application icons.

[0040] For example, the second interface can be interface 301 as shown in Figure 3 below, or an interface that does not display a non-full-screen window in the first mode. The third button is button 3011 in interface 301. The twelfth interface can be interface 1401 as shown in Figure 14 below. The icon of the first layout template can be the icon of any layout template in interface 1401, such as layout template 10011a, layout template 10011b, etc. Taking layout template 10011b as an example, the thirteenth interface can be interface 1501 as shown in Figure 15 below. Interface 1501 includes display area 15011, display area 15012, and display area 15013, and each display area includes icons of at least two applications. For example, the first display area can be display area 15011, and the second display area can be display area 15012, display area 15013, etc.

[0041] Using this design approach, in response to a user's selection of a layout template, the electronic device can display at least two display areas corresponding to the task areas within that layout template, and show recommended applications in each task area. This allows users to view recommended applications in the various display areas corresponding to the selected layout template, enabling them to choose an application without needing to search for it, thus improving human-computer interaction efficiency.

[0042] In one possible design of the first aspect, after displaying the thirteenth interface (as shown in interface 1501 below), the method further includes: in response to the tenth operation, displaying the fourteenth interface (as shown in interface 1601 below), the fourteenth interface including a first display area and a second display area, the first display area (e.g., display area 15011 in interface 1601) including a fourth window of the fifth application (e.g., window 4011 in interface 1501), the first display area not including application icons, and the second display area (e.g., display area 15012, display area 15013 in interface 1601) including icons of at least two applications. The first display area may also be referred to as display area A2, and the second display area may also be referred to as display area A1. The icons of at least two applications in the second display area of ​​the fourteenth interface are different from the icons of at least two applications in the second display area of ​​the thirteenth interface. And / or, the order of the icons of at least two applications in the second display area of ​​the fourteenth interface is different from the order of the icons of at least two applications in the second display area of ​​the thirteenth interface.

[0043] Using this design, once an application is launched in one or more display areas, the recommended applications in other display areas will change. This allows the electronic device to dynamically adjust the recommended applications in each display area, ensuring that the recommended applications match the already launched applications and improving the accuracy of the recommendations.

[0044] In one possible design of the first aspect, after displaying the second interface (as shown in interface 301 below), the method further includes: in response to a third operation, displaying a fifteenth interface (as shown in interface 2101 below), the fifteenth interface including at least one icon of a recommended task group and a second taskbar, wherein the icon of at least one recommended task group in the fifteenth interface is different from the icon of at least one recommended task group in the fourth interface (such as interface 2001, interface 2011, etc.).

[0045] Using this design approach, in the first mode, the electronic device can also display recommended task groups even when non-full-screen windows are not displayed, allowing users to quickly launch multiple applications by selecting recommended task groups and display them according to the layout in the recommended task groups.

[0046] In one possible design of the first aspect, the second interface (as shown in interface 301 below) includes an icon for the sixth application. After displaying the second interface, the method further includes: in response to an eleventh operation, displaying a sixteenth interface (as shown in interface 401 below), the sixteenth interface including a fifth window of the sixth application and a second taskbar, the window size of the fifth window being smaller than the window size of the full-screen display window of the sixth application, the eleventh operation including an operation on the icon of the sixth application. In response to a third operation, displaying a seventeenth interface (as shown in interface 2021 below), the seventeenth interface including a fifth window and a second taskbar, the seventeenth interface also including a prompt message indicating "No recommendations available" (such as "No recommendations available" in task group list 20211 in interface 2021).

[0047] Using this design approach, in the first mode, the electronic device can also choose not to display recommended task groups when a non-full-screen window is displayed. This way, if there is no suitable recommended task group that includes the currently displayed application, the electronic device can avoid recommending anything, thus preventing the display of inappropriate recommended task groups and improving the rationality of the recommendations.

[0048] In one possible design approach of the first aspect, after displaying the fifth interface, the method further includes: displaying the eighteenth interface (as shown in interface 1211 below), the eighteenth interface including a sixth window (e.g., window 12111), a seventh window (e.g., window 12112), an eighth window (e.g., window 12113), and a ninth window (e.g., window 12114), the sixth, seventh, and eighth windows being portrait (also known as vertical) windows, and the ninth window being a landscape (also known as horizontal) window; the eighteenth interface also includes icons of the second layout template (e.g., layout template 10011b) and the third layout template The first layout template has three icons (e.g., layout template 10011d). The second layout template includes a first task area (e.g., the task area on the left), a second task area (e.g., the task area on the upper right), and a third task area (e.g., the task area on the lower right). The first task area is a vertical task area, while the second and third task areas are horizontal task areas. The third layout template includes a fourth task area (e.g., the task area on the left), a fifth task area (e.g., the task area in the middle), and a sixth task area (e.g., the task area on the right). The fourth, fifth, and sixth task areas are vertical task areas. In response to an operation on the icons of the second layout template, the nineteenth interface (e.g., interface 1221 below) is displayed. The nineteenth interface includes a sixth window, a ninth window, and a third display area (e.g., display area 12211). The third display area includes a seventh window and an eighth window. The positions of the sixth window, the ninth window, and the third display area relative to the screen display correspond one-to-one with the positions of the first, second, and third task areas relative to the icons of the second layout template. In response to the operation on the icon of the third layout template, the twentieth interface (as shown in interface 1231 below) is displayed. The twentieth interface includes the sixth window, the eighth window, and the fourth display area. The fourth display area includes the seventh window and the ninth window. The positions of the sixth window, the eighth window, and the fourth display area relative to the screen display correspond one-to-one with the positions of the fourth task area, the fifth task area, and the sixth task area relative to the icon of the third layout template.

[0049] In other words, this design can also be described as follows: An eighteenth interface is displayed, comprising the windows of a first application (as described in the seventh window above), a second application (as described in the eighth window above), a third application (as described in the ninth window above), and a fourth application (as described in the sixth window above). The first application window is a landscape window, while the second, third, and fourth application windows are portrait windows. In response to the twelfth operation, icons for at least one layout template are displayed. These icons include icons for a second and a third layout template. The second layout template icon includes a horizontal task area (as described in the second and third task areas above), while the third layout template icon does not include a horizontal task area (as described in the fourth, fifth, and sixth task areas above, all of which are portrait task areas). The twelfth operation includes an operation on a third button, such as clicking the third button. When an operation to select the second layout template is detected, the nineteenth interface is displayed. This second interface includes the windows of the first and second applications, and a third display area. The third display area includes the identifier of the third application (e.g., a window) and the identifier of the fourth application, but does not include the identifiers of the first and second applications. When an operation to select the second layout template is detected, the twentieth interface is displayed. This twentieth interface includes the windows of the second and fourth applications, and a fourth display area. The fourth display area includes the identifiers of the first and third applications, but does not include the identifiers of the second and third applications.

[0050] Using this design approach, in the first mode, even when the number of regions in the layout template selected by the user is less than the currently displayed non-full-screen windows, multiple application windows can still be laid out, with at least two application windows included in one of the display regions, ensuring that all application windows can be displayed on the screen. Furthermore, by selecting different layout templates, the floating windows within the same display region can be different, allowing the layout of multiple application windows to match the currently selected layout template, thus improving the rationality of the layout.

[0051] In one possible design of the first aspect, in response to a third operation, a fourth interface is displayed, including: in response to the third operation, querying first task group data (hereinafter also referred to as target task group data 3) for each layout template, the first task group data including an identifier of a layout template and an identifier of a first application. If there are multiple first task group data for any layout template, target first task group data for any layout template is selected from the multiple first task group data based on the number of times the first task group data is used and / or the last time it was used; if there is only one first task group data for any layout template, the first task group data is the target first task group data for any layout template. The fourth interface is displayed, the fourth interface including at least one recommended task group, the at least one recommended task group including the first task group in the target first task group data, the first task group including identifiers of at least two applications, and the first task group including the identifier of the first application.

[0052] Using this design approach, the first task group data corresponding to each layout template can be queried. The first task group data includes the identifier of the first application, indicating that the first task group data includes the layout of the first application's window. Subsequently, recommended task groups are displayed based on the data from the first task group. This allows for the display of recommended task groups for each layout template, and also for displaying recommended task groups based on the user's historical usage habits regarding the layout of the first application and other applications, thus satisfying user preferences.

[0053] In one possible design approach of the first aspect, in response to the eighth operation, a tenth interface is displayed, including: in response to the eighth operation, querying second task group data (hereinafter also referred to as candidate task group data 0), wherein the number of application identifiers in the task group of the second task group data is the same as the number of windows in the multiple windows of the ninth interface, the multiple windows including a first window and a third window. If second task group data is found and there are multiple second task group data, a target second task group data (hereinafter also referred to as target task group data 1) is selected from the multiple second task group data, the target second task group data being the task group data containing the most target application identifiers among the multiple second task group data, the target application identifier being the identifier of the application to which the multiple windows belong. If there is only one second task group data, the second task group data is the target second task group data. On the tenth interface, the multiple windows are laid out according to the task group and layout template identifiers in the target second task group data.

[0054] This design approach allows querying second task group data where the amount of application identifiers matches the number of currently displayed windows. The windows are then laid out according to the task group and layout template identifiers within this second task group data, ensuring the layout aligns with the user's historical layout habits for the same number of windows. Furthermore, if multiple second task group datasets exist, a target second task group dataset containing the largest number of target application identifiers can be selected. This ensures the highest overlap between the application identifiers in the target second task group and the application identifiers corresponding to the current windows. Laying out the windows according to the task group and layout template identifiers in the target second task group data yields a layout that accurately meets the user's needs.

[0055] In one possible design approach of the first aspect, the method further includes: if no data for the second task group is found, selecting a target layout template (hereinafter also referred to as target layout template 1), wherein the target layout template is the layout template with the highest matching degree with the landscape and portrait orientations of the multiple windows among layout templates where the number of task areas is the same as the number of windows in the multiple windows. The multiple windows are then laid out according to the target layout template on the tenth interface.

[0056] Using this design approach, even if no data for the second task group is found, a target layout template with a high degree of matching can be selected based on the current number of windows and their orientation (portrait or landscape). This allows for the layout of multiple windows according to the target template, satisfying the requirements for the number of windows and their orientation, thus achieving a reasonable arrangement of multiple windows.

[0057] In one possible design approach of the first aspect, in response to an operation on the icon of the first layout template, the thirteenth interface is displayed, including: in response to an operation on the icon of the first layout template, querying third task group data (hereinafter also referred to as target task group data 4), the third task group data including the identifier of the first layout template. Traversing each display area, counting the applications displayed in the current display area and their display counts in the third task group data, obtaining the first application sort (hereinafter also referred to as application sort 1) with the highest number of display counts in the current display area from high to low. The current display area is a horizontal display area, filtering out horizontal applications and applications in the first application sort from the number of times installed applications are launched, obtaining a second application sort (hereinafter also referred to as application sort 2); combining the first application sort and the second application sort, obtaining a first recommended sort (hereinafter also referred to as recommended application sort m1), and displaying the icons of the first number (hereinafter also referred to as number 1) of applications in the first recommended sort in the current display area of ​​the thirteenth interface. The current display area is a portrait display area. The portrait-oriented applications and the applications in the first application sort are filtered out from the number of times the installed applications are launched, resulting in a third application sort (hereinafter also referred to as application sort 3). The first application sort and the third application sort are combined to obtain the second recommended sort (hereinafter also referred to as recommended application sort m2). The icons of the first number of applications in the second recommended sort are displayed in the current display area of ​​the thirteenth interface.

[0058] Using this design approach, after selecting the identifier of the first layout template, for any display area, the system can combine the display frequency ranking of applications displayed in that display area from the third task group data, the horizontal and vertical orientation of that display area, and the launch frequency ranking of applications installed on the electronic device. This allows the system to display the identifiers of applications with the highest display frequency ranking in that display area, as well as the identifiers of applications with the highest launch frequency ranking that are suitable for display in either a horizontal (if the display area is horizontal) or a vertical (if the display area is vertical) display area, thereby improving the rationality of the recommendations.

[0059] In a second aspect, an electronic device is provided, comprising a memory and one or more processors. The memory is coupled to the processors. The memory stores computer program code, which includes instructions. When the instructions are executed by the processor, the electronic device performs the method as described in any one of the first aspects above.

[0060] Thirdly, a computer-readable storage medium is provided that stores instructions which, when executed on an electronic device, cause the electronic device to perform any of the methods described in the first aspect.

[0061] Fourthly, a computer program product containing instructions is provided, which, when run on an electronic device, enables the electronic device to perform the method described in any one of the first aspects.

[0062] Fifthly, embodiments of this application provide a chip, the chip including a processor, the processor being configured to invoke a computer program in memory to perform the method as described in the first aspect.

[0063] It is understood that the beneficial effects of the electronic device described in the second aspect, the computer-readable storage medium described in the third aspect, the computer program product described in the fourth aspect, and the chip described in the fifth aspect can be referred to the beneficial effects of the first aspect and any of its possible design embodiments, which will not be repeated here. Attached Figure Description

[0064] Figure 1 is a schematic diagram of the desktop in non-free screen mode provided in an embodiment of this application;

[0065] Figure 2 is a schematic diagram of the switching process from non-free screen mode to free screen mode provided in the embodiment of this application;

[0066] Figure 3 is a schematic diagram of the desktop in the free screen mode provided in an embodiment of this application;

[0067] Figure 4 is one of the schematic diagrams of a floating window displayed in the free screen mode provided in the embodiments of this application;

[0068] Figure 5 is a schematic diagram of three floating windows displayed in the free screen mode provided in the embodiment of this application;

[0069] Figure 6A is a schematic diagram of a full-screen display window of an application in non-free screen mode provided in an embodiment of this application;

[0070] Figure 6B is a second schematic diagram of a floating window displayed in the free screen mode provided in the embodiment of this application;

[0071] Figure 6C is a schematic diagram of a maximized window displayed in a non-free screen mode according to an embodiment of this application;

[0072] Figure 7A is a schematic diagram of two split-screen interfaces displayed in a non-free screen mode according to an embodiment of this application;

[0073] Figure 7B is one of the schematic diagrams showing two floating windows in the free screen mode provided in the embodiments of this application;

[0074] Figure 8 is a schematic diagram of a full-screen display window of another application in non-free screen mode provided in an embodiment of this application;

[0075] Figure 9A is a schematic diagram of the multi-task management interface in non-free screen mode provided in the embodiment of this application;

[0076] Figure 9B is a schematic diagram of the multi-task group management interface in the free screen mode provided in the embodiment of this application;

[0077] Figure 10 is one of the schematic diagrams of the display layout template in the free screen mode provided in the embodiments of this application;

[0078] Figure 11 is a schematic diagram of selecting a layout template in Figure 11 according to an embodiment of this application;

[0079] Figure 12A is a schematic diagram of selecting another layout template in Figure 11 according to an embodiment of this application;

[0080] Figure 12B is a second schematic diagram of the display layout template in the free screen mode provided in the embodiment of this application;

[0081] Figure 12C is a schematic diagram of selecting a layout template in Figure 12B according to an embodiment of this application;

[0082] Figure 12D is a schematic diagram of selecting another layout template in Figure 12B according to an embodiment of this application;

[0083] Figure 13 is a schematic diagram of selecting another layout template in Figure 11 according to an embodiment of this application;

[0084] Figure 14 is a third schematic diagram of the display layout template in the free screen mode provided in the embodiments of this application;

[0085] Figure 15 is a schematic diagram of selecting a layout template in Figure 14 according to an embodiment of this application;

[0086] Figure 16 is a schematic diagram showing the application launched in one of the display areas of Figure 15, according to an embodiment of this application.

[0087] Figure 17A is a schematic diagram of the application panel D1 provided in an embodiment of this application;

[0088] Figure 17B is a schematic diagram showing the application launched in another display area of ​​Figure 16 according to an embodiment of this application;

[0089] Figure 18 is a schematic diagram of the application panel D2 provided in an embodiment of this application;

[0090] Figure 19 is a fourth schematic diagram of the display layout template in the free screen mode provided in the embodiments of this application;

[0091] Figure 20A is one of the schematic diagrams showing the recommended task group in the free screen mode provided in the embodiment of this application;

[0092] Figure 20B is a second schematic diagram of the display of recommended task groups in the free screen mode provided in the embodiment of this application;

[0093] Figure 20C is a third schematic diagram of the display of recommended task groups in the free screen mode provided in the embodiments of this application;

[0094] Figure 21 is a fourth schematic diagram of the display of recommended task groups in the free screen mode provided in the embodiments of this application;

[0095] Figure 22A is the fifth schematic diagram of displaying recommended task groups in the free screen mode provided in the embodiment of this application;

[0096] Figure 22B is a sixth schematic diagram of the display of recommended task groups in the free screen mode provided in the embodiments of this application;

[0097] Figure 22C is the fifth schematic diagram of the display layout template in the free screen mode provided in the embodiment of this application;

[0098] Figure 23A is the seventh schematic diagram of the display of recommended task groups in the free screen mode provided in the embodiment of this application;

[0099] Figure 23B is a second schematic diagram of two floating windows displayed in the free screen mode provided in the embodiment of this application;

[0100] Figure 24A is one of the schematic diagrams showing the effect after clicking "One-Click Layout" according to an embodiment of this application;

[0101] Figure 24B is a second schematic diagram of the effect after clicking "One-Click Layout" according to an embodiment of this application;

[0102] Figure 25 is a flowchart of determining a one-click layout provided in an embodiment of this application;

[0103] Figure 26 is a flowchart of determining the recommended task group provided in an embodiment of this application;

[0104] Figure 27 is a flowchart of the process for determining recommended applications provided in an embodiment of this application;

[0105] Figure 28 is a flowchart illustrating the determination of the display area of ​​the floating window according to an embodiment of this application;

[0106] Figure 29 is a schematic diagram illustrating the principle of determining the order of multiple floating windows according to an embodiment of this application;

[0107] Figure 30 is a schematic diagram of the software architecture of a tablet provided in an embodiment of this application;

[0108] Figure 31 is a schematic diagram of the composition of a software module of a tablet provided in an embodiment of this application;

[0109] Figure 32 is a timing interaction diagram for determining recommended applications provided in an embodiment of this application;

[0110] Figure 33 is a timing interaction diagram of launching an application in a display application according to an embodiment of this application;

[0111] Figure 34 is a timing interaction diagram of the application panel D1 for displaying recommended applications according to an embodiment of this application;

[0112] Figure 35A is a timing interaction diagram of determining the recommended task group provided in an embodiment of this application;

[0113] Figure 35B is a timing interaction diagram of launching the application after selecting the recommended task group, provided in an embodiment of this application.

[0114] Figure 36 is a timing interaction diagram of one-click layout of multiple floating windows provided in an embodiment of this application. Detailed Implementation

[0115] The technical solutions of the embodiments of this application are described below with reference to the accompanying drawings. In the description of the embodiments of this application, the terminology used in the following embodiments is for the purpose of describing specific embodiments only and is not intended to limit the application. As used in the specification and appended claims of this application, the singular expressions "a," "the," "the," "the," and "this" are intended to also include expressions such as "one or more," unless the context clearly indicates otherwise. It should also be understood that in the following embodiments of this application, "at least one" and "one or more" refer to one or more (including two). The term "and / or" is used to describe 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.

[0116] References to "one embodiment" or "some embodiments" in this specification mean that one or more embodiments of this application include a specific feature, structure, or characteristic described in connection with that embodiment. Therefore, the phrases "in one embodiment," "in some embodiments," "in other embodiments," "in still other embodiments," etc., appearing in different parts of this specification do not necessarily refer to the same embodiment, but rather mean "one or more, but not all, embodiments," unless otherwise specifically emphasized. The terms "comprising," "including," "having," and variations thereof mean "including but not limited to," unless otherwise specifically emphasized. The term "connection" includes direct connections and indirect connections, unless otherwise stated. "First" and "second" are used for descriptive purposes only and should not be construed as indicating or implying relative importance or implicitly specifying the number of technical features indicated.

[0117] In the embodiments of this application, the words "exemplarily" or "for example" are used to indicate examples, illustrations, or explanations. Any embodiment or design described as "exemplarily" or "for example" in the embodiments of this application should not be construed as being more preferred or advantageous than other embodiments or design solutions. Specifically, the use of the words "exemplarily" or "for example" is intended to present the relevant concepts in a specific manner.

[0118] The display method and electronic device provided in this application can be applied to electronic devices.

[0119] For example, electronic devices can run game applications and social chat applications in the foreground to meet the need to play games and chat at the same time; electronic devices can run video players and note-taking applications in the foreground to meet the need to watch videos and take notes at the same time, etc.

[0120] It is understandable that electronic devices run multiple tasks in the foreground. These multiple tasks can be two tasks, or more than two tasks, such as three or four tasks.

[0121] In some implementations, electronic devices can provide split-screen functionality to meet the needs of running multiple tasks. However, using split-screen functionality requires users to first locate and launch multiple applications, and then adjust the position, size, and other layout information of each task window to make the layout of multiple task windows meet the requirements. The whole process is complicated for users and has low human-computer interaction efficiency.

[0122] Based on the above problems, this application provides a display method:

[0123] Electronic devices can recommend task groups (see Scenario 3 below), and can also display recommended applications within the task area of ​​a user-selected layout template (see Scenario 2 below). Users no longer need to search for and launch multiple applications one by one.

[0124] Electronic devices can also quickly arrange multiple tasks, such as providing layout templates for users to choose from (see Scenario 2 below), or performing one-click layout for multiple tasks (see Scenario 4 below). This eliminates the need for users to manually adjust the layout of each task window.

[0125] In summary, adopting the embodiments of this application is beneficial for efficiently realizing multi-tasking and improving human-computer interaction efficiency.

[0126] The electronic devices in the embodiments of this application may be mobile phones, smart TVs, wearable devices, tablets, computers with wireless transceiver capabilities, 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, or wireless terminals in smart homes, etc. The embodiments of this application do not limit the specific technologies or device forms used in the electronic devices.

[0127] The following description primarily uses a tablet as an example to illustrate the embodiments of this application. It should be noted that the implementation principle and steps remain the same when the electronic device is in other forms, and will not be repeated here.

[0128] The tablet can be set to a free screen mode, which can also be called a multi-tasking scheduling mode, a simultaneous screen multi-tasking mode, etc. This application does not specifically limit the name of this mode. For ease of explanation, the free screen mode can also be called the first mode, and the non-free screen mode can also be called the second mode.

[0129] The following section will provide a detailed introduction to the Free Screen Mode using specific scenarios.

[0130] Scenario 1: Entering and exiting free screen mode.

[0131] In non-free screen mode, the tablet can display a mode switching button for the first state. In response to a user's action on this button, such as a click, the tablet can then display a mode switching button for the second state. When the tablet displays the second-state mode switching button, it indicates that the current display mode is free screen mode.

[0132] Referring to Figures 1-3, in non-free screen mode, the tablet can display interface 101 as shown in Figure 1. Interface 101 includes button 1011, which is a mode switching button in the first state. In response to a user clicking button 1011, the tablet can display interface 201 as shown in Figure 2, which includes one frame of animation 2011. It is understood that animation 2011 can include multiple frames, and after the user clicks button 1011, the tablet can continuously display multiple frames of animation 2011. After animation 2011 is displayed, the tablet can display interface 301 as shown in Figure 3, which includes button 1012 and button 3011, with button 1012 being a mode switching button in the second state. Compared to the background of button 1011 in interface 101, the background grayscale value of button 1012 in interface 301 is larger. From the user's perspective, the darker background color of button 1012 indicates that the tablet's display mode is free screen mode. Optionally, the tablet can remind the user that the current display mode is free screen mode by displaying prompts, such as displaying "Entered free screen mode" at the top of the interface. This application does not specifically limit this. Button 3011 is a multi-tasking layout button. For details about this layout button, please refer to the relevant description below. It will not be described in detail here.

[0133] Of course, during the process of switching the tablet's display mode from non-freescreen mode to freescreen mode, the tablet may also choose not to display the switching animation, such as not displaying interface 201. The same principle applies to switching the tablet's display mode from freescreen mode to non-freescreen mode (i.e., exiting freescreen mode) in the following text.

[0134] The above-described method of entering FreeScreen mode via the mode switching button is only one possible implementation. Optionally, the tablet can also switch the display mode to FreeScreen mode in response to the user's thirteenth operation on the desktop (such as long press, swipe, etc.) or the user's first voice input (such as "switch to FreeScreen").

[0135] In FreeScreen mode, in response to user actions such as clicking on application icons on the display, the tablet can launch the corresponding application and display its interface as a floating window. Furthermore, when multiple applications are launched, the tablet can display multiple floating windows on the screen.

[0136] Taking multiple applications including APP-1, APP-2, and APP-3 as an example, as shown in Figures 3 and 4, interface 301 includes an icon 3012 for APP-1. In response to a user's click on icon 3012 in interface 301, the tablet can display interface 401, which includes a floating window 4011 containing the application interface of APP-1. Referring to Figure 5, after launching APP-1, APP-2, and APP-3, the tablet can display interface 501. Interface 501 includes floating windows 4011, 5012, and 5011. Floating window 5011 contains the application interface of APP-2, and floating window 5012 contains the application interface of APP-3.

[0137] In this embodiment, the size of an application's floating window (a non-full-screen window, such as floating window 4011) is smaller than the size of the application's full-screen display window (also called the full-screen display interface). For example, the window size of APP-1's floating window 4011 is smaller than the window size of APP-1's full-screen display window in interface 601 shown in Figure 6A below. It should be noted that a full-screen display window can also be understood as a maximized display window, such as the maximized display window of APP-1 in interface 621 shown in Figure 6C below. In one implementation, optionally, the floating window can be displayed on top of other applications. In another implementation, optionally, one floating window in this embodiment can also be obscured by another floating window; that is, the floating window is not necessarily the topmost window.

[0138] The display positions of the multiple floating windows in the interface 501 described above are merely illustrative. Optionally, the multiple floating windows may or may not obscure each other. Alternatively, the multiple floating windows may be arranged from left to right, from top to bottom, or randomly. This application does not impose any specific limitations on this arrangement.

[0139] During the response process shown in Figures 3-5 above, the launched APP-1 is located in the bottom taskbar 3013 of the desktop. The "bottom" of the bottom taskbar 3013 refers to the area away from the status bar, which includes information such as battery level, time, and network signal strength. It should be noted that this embodiment uses the taskbar at the bottom of the display area as an example, but this does not mean that the application is limited to this. In some implementations, the taskbar can be in the right-hand area of ​​the display area, or in the left-hand area, or the user can display a separate window / interface to show the taskbar through interactive operations. Optionally, in this embodiment, the taskbar can be opaque, or it can be semi-transparent. The taskbar shown in the accompanying drawings of this embodiment is semi-transparent, but this does not mean that the application is limited to this. Optionally, in response to the user's click on an application icon in an area outside the bottom taskbar on the desktop, the tablet can also display a floating window of the corresponding application. For example, neither the browser icon 3014 nor the email icon 3015 in interface 301 are in the bottom taskbar 3013: in response to the user clicking the browser icon 3014 in interface 301, the tablet can also display a floating browser window. In response to the user clicking the email icon 3015 in interface 301, the tablet can also display a floating email window.

[0140] It is understood that the bottom taskbar includes, but is not limited to, multiple application icons and / or folder icons, providing users with an entry point to access these applications and files. Optionally, the tablet may also display icons of frequently used applications (such as those ranked high in usage frequency or those used more than a preset threshold) in the bottom taskbar, such as the area 3016 in the taskbar 3013 of interface 301 which includes icons of frequently used applications.

[0141] In FreeScreen mode, when a floating window is displayed, the tablet can choose to show app icons outside the bottom taskbar area or not. Not showing app icons outside the bottom taskbar area prevents accidental app icon touches while operating one or more floating windows, and also optimizes the display effect, resulting in a cleaner interface. This article primarily uses this implementation method as an example.

[0142] For example, when the floating window is not displayed, the tablet's displayed interface 301 includes a wallpaper image (represented by gray diagonal lines in the figure, the same below), application icons in the bottom taskbar 3013, such as icon 3012, and application icons in the area outside the bottom taskbar 3013, such as icons 3014, 3015, etc. When the floating window is displayed, the tablet's displayed interface 401 includes a wallpaper image, a floating window 4011, and application icons in the bottom taskbar 3013, such as icon 3012, but does not include application icons in the area outside the bottom taskbar 3013.

[0143] In non-free screen mode, in response to a user's action on an application icon on the desktop, the tablet can display the application's full-screen interface. Then, in response to a user's action on the mode switch button (in the first state), the tablet can display the application's floating window. From the user's perspective, after switching the tablet's display mode from non-free screen mode to free screen mode, the application's interface changes from a full-screen display to a floating window.

[0144] Taking APP-1 as an example, referring to Figures 1, 6A, and 6B, in non-free screen mode, the tablet can display interface 101. In response to a user's click on the APP-1 icon 1013 in interface 101, the tablet can display interface 601. Interface 601 includes the full-screen application interface of APP-1, excluding the application icons outside the area of ​​the wallpaper image and the bottom taskbar 6011. From the user's perspective, the application icons outside the area of ​​the wallpaper image and the bottom taskbar 6011 are completely obscured. Optionally, the bottom 6011 of interface 601 can be shown or hidden. In response to a user's click on button 1011 in interface 601, the tablet can display interface 611. Interface 611 includes a floating window 6111, which contains the APP-1 application interface. Furthermore, the area outside the edge of the floating window 6111 in interface 611 includes a portion of the wallpaper image but excludes the application icons outside the area of ​​the bottom taskbar 3013. From the user's visual perspective, part of the wallpaper image is obscured.

[0145] In free-screen mode, after the tablet displays a floating window, in response to the user's triggering operation of the maximize button in the floating window, such as clicking it, the tablet can display the maximized window corresponding to that floating window. Referring to Figures 6B and 6C, the maximize button is button 6112 in the floating window 6111 of interface 611. In response to the user's clicking operation of button 6112 in the floating window 6111, the tablet can display interface 621, which includes the maximized window of APP-1. The window size of the maximized window of APP-1 is larger than the size of the floating window of APP-1 (such as floating window 4011).

[0146] In non-free screen mode, when the user uses the split-screen function, the tablet can display multiple application interfaces on the screen in split format, excluding wallpaper images. Optionally, there are no gaps between the display windows of the multiple application interfaces displayed in split-screen mode. In free screen mode, when the tablet displays multiple floating windows, there are gaps between the areas of the multiple floating windows, and a portion of the wallpaper image is included between the areas of the multiple floating windows.

[0147] Taking APP-1 and APP-2 as examples, refer to Figures 7A and 7B: In non-free screen mode, when the user uses the split-screen function, after launching APP-1 and APP-2, the tablet can display interface 701. Interface 701 includes application interface 7011 of APP-1 and application interface 7012 of APP-2. The area of ​​application interface 7011 is located on the left half of interface 701, and the area of ​​application interface 7012 is located on the right half of interface 701. There is no gap between the areas of interface 7011 and interface 7012, and interface 701 does not include wallpaper images. In response to the user's click operation on button 1011 in interface 701, the tablet can display interface 711. Interface 711 includes floating window 7111, floating window 7112 and a portion of wallpaper image. Floating window 7111 includes the application interface of APP-1, and floating window 7112 includes the application interface of APP-1. There is a gap between the areas of floating window 7111 and floating window 7112, and a portion of wallpaper image is included in the gap.

[0148] In free screen mode, the tablet can display a second-state mode switch button. In response to a user's action on this button (e.g., clicking), the tablet can then display the first-state mode switch button. Displaying the first-state mode switch button indicates that the tablet's display mode has switched to non-free screen mode.

[0149] Referring to Figures 4 and 6A, interface 401 includes button 1012, which is a mode switching button for the second state. In response to the user's click operation on button 1012 in interface 401, the tablet can display interface 601, which includes button 1011, which is a mode switching button for the first state.

[0150] In free screen mode, with the tablet displaying a floating window, in response to the user's triggering of the mode switching button in the second state, the tablet can display the full-screen interface of the application. Continuing with the response examples from interface 401 in Figure 4 to interface 601 in Figure 6A, interface 401 includes the floating window 4011 of APP-1, and interface 601 includes the full-screen display interface of APP-1.

[0151] In free-screen mode, when the tablet displays multiple floating windows, in response to the user's triggering of the mode switching button in the second state, the tablet can display the full-screen interface of the application in one of the floating windows. Optionally, a floating window can be the first floating window displayed in free-screen mode, or the floating window with focus. This application does not specifically limit this. Next, in response to the user's triggering operation on the full-screen display interface, such as a swipe-up operation from the bottom of the interface, the tablet can display a multi-task management interface, which includes multiple task cards, each task card including a task identifier corresponding to a floating window. For example, the task identifier can be a thumbnail, window, or view of the full-screen display window corresponding to the floating window, used to indicate a full-screen display window.

[0152] Referring to Figures 5, 8, and 9A, interface 501 includes floating windows 4011 for APP-1, 5011 for APP-2, and 5012 for APP-3. In response to a user's click on button 1012 in interface 501, the tablet can display interface 801. Interface 801 includes a full-screen display of APP-3. In response to a user's swipe-up action from the bottom of interface 801, the tablet can display interface 901, which is a multitasking management interface. Interface 901 includes task cards 9011, 9012, and 9013. Task card 9011 includes a thumbnail of the full-screen window corresponding to floating window 4011; task card 9012 includes a thumbnail of the full-screen window corresponding to floating window 5011; and task card 9013 includes a thumbnail of the full-screen window corresponding to floating window 5012.

[0153] In the multitasking management interface, in response to a user's action on any task card, such as a click, the tablet can display a full-screen window indicated by the task icon in that task card. This allows the tablet to quickly launch the full-screen window corresponding to the floating window displayed in free-screen mode after switching from free-screen mode to non-free-screen mode.

[0154] It is understandable that when the interface 711 shown in Figure 7B is displayed, the response process of the tablet to the user's click operation on the button 1012 in the interface 711 is the same, and will not be described in detail here.

[0155] Additionally, in FreeScreen mode, when the desktop is displayed, in response to user actions on the desktop, such as swiping up from the bottom of the screen, the tablet can display the task group management interface. This interface can include task group cards, each containing a task group identifier. For example, a task group identifier can include identifiers for one or more floating windows. These identifiers can be thumbnails, windows, or views corresponding to the floating window, and each floating window identifier within the task group can indicate its position within the task group.

[0156] Referring to Figures 5 and 9B, in response to a user swiping up from the bottom of interface 501, the tablet can display interface 911, which includes task group cards 9111, 9112, 9113, and 9114. Taking task group card 9114 as an example, task group card 9114 includes three floating windows: a floating window for APP-1, a floating window for APP-2, and a floating window for APP-3, as well as a layout thumbnail.

[0157] In the task group management interface, in response to a user's trigger action on any task group card, such as a click, the tablet can display a floating window for one or more tasks corresponding to that task group card. This allows the tablet to quickly display recently used task groups. For example, in response to a user's click on task group card 9114 in interface 911, the tablet can display interface 611. As another example, in response to a user's click on task group card 9113 in interface 911, the tablet can display interface 501.

[0158] Scenario 2, layout template.

[0159] In free screen mode, the tablet can display layout buttons, such as button 3011. In response to user triggering operation 1 on the layout button, such as a click operation, the tablet can display multiple layout templates.

[0160] Referring to Figures 5 and 10, in response to a user's click on button 3011 in interface 501, the tablet can display interface 1001. Interface 1001 includes a template list 10011. The template list 10011 includes six layout templates: layout template 10011a, layout template 10011b, layout template 10011c, layout template 10011d, layout template 10011e, and layout template 10011f.

[0161] It should be noted that the layout templates displayed on the mobile phone are essentially icons of layout templates. For example, layout template 10011a in interface 1001 is essentially an icon that includes two areas (hereinafter referred to as task areas) and a border. For the sake of simplicity, this article will directly use the term "layout template" to describe it, and will not elaborate further below.

[0162] One of multiple layout templates can be in a default selected state. The default selected template can be the first layout template in the template list, or it can be the layout template previously used by the user in the template list; this application does not specifically limit this. Referring to Figure 10, layout template 10011a in template list 10011 is in a selected state. Subsequently, after the user selects a layout template, that selected layout template will be set to a selected state. For example, if the task area in the layout template selected by the user is filled with a dark color, it indicates that it is in a selected state; this will not be repeated below.

[0163] Each layout template includes at least two task areas and their layout styles. The following description uses the layout template in template list 10011 of interface 1001 shown in Figure 10 as an example.

[0164] The layout template 10011a in the template list 10011 includes two vertical task areas, and the two vertical task areas are arranged horizontally.

[0165] The layout template 10011b in the template list 10011 includes one vertical task area and two horizontal task areas. The vertical task area is positioned on the left, and the one vertical task area and two horizontal task areas are arranged side by side, with the two horizontal task areas arranged vertically.

[0166] The layout template 10011c in template list 10011 includes 4 horizontal task areas, and the 4 horizontal task areas are arranged in a four-grid layout.

[0167] The task areas and layouts of other layout templates are similar, and will not be described in detail here.

[0168] In this embodiment, the vertical task area refers to a task area whose height is greater than its width, and the horizontal task area refers to a task area whose width is greater than its height. The height direction of the area is perpendicular to the length direction of the status bar, and the width direction of the area is the same as the length direction of the status bar.

[0169] In this embodiment, a left-right layout refers to a layout along the length of the status bar. A top-bottom layout refers to a layout perpendicular to the length of the status bar. A four-grid layout refers to a layout with two columns along the length of the status bar and two rows perpendicular to the length of the status bar.

[0170] The template list 10011 above contains 6 layout templates. Optionally, the number of layout templates can be more or less. For example, the number of layout templates could be 3, 4, 5, 6, 7, 8, 9, 10, etc. The layout styles of the layout templates in the template list 10011 above are also merely illustrative. Optionally, the layout styles can also be other.

[0171] The use of layout templates can be divided into the following situations.

[0172] Scenario 1: When multiple floating windows are displayed, the user selects layout template X where the number of task areas is equal to the number of floating windows.

[0173] That is, the number of floating windows is n1, n1≥2, n1 is an integer, and the number of task areas of the selected layout template X is also n1.

[0174] In response to the user's selection of layout template X, the tablet can display multiple floating windows on the screen. The positions of n1 floating windows relative to the screen correspond one-to-one with the positions of n1 task areas relative to layout template X. This can be understood as the position of a floating window relative to the display area on the screen being the same as or corresponding to the position of its corresponding task area relative to the layout template; or, conversely, the position of a floating window on the display area being the same as or corresponding to the position of its corresponding task area within the layout template.

[0175] Referring to Figures 10 and 11, interface 1001 includes three floating windows: floating window 4011, floating window 5011, and floating window 5012. Furthermore, layout template 10011b in template list 10011 of interface 1001 includes three task areas. The number of task areas in layout template 10011b is equal to the number of floating windows, both being three. In response to a user's selection of layout template 10011b in template list 10011 of interface 1001, the tablet can display interface 1101. In interface 1101, the position of floating window 4011 relative to the display screen is the same as the position of the vertical task area in layout template 10011b relative to layout template 10011b, both located on the left side; the position of floating window 5011 relative to the display screen is the same as the position of one horizontal task area in layout template 10011b relative to layout template 10011b, both located on the upper right side; the position of floating window 5012 relative to the display screen is the same as the position of the remaining horizontal task area in the vertical layout of layout template 10011b relative to layout template 10011b, both located on the lower right side.

[0176] Scenario 2: When multiple floating windows are displayed, select layout template Y with fewer task areas than floating windows.

[0177] That is, the number of floating windows is n2, n2≥3, n3 is an integer, and the number of task areas of the selected layout template Y is n3, n3<n2, n3 is also an integer.

[0178] In response to the user's selection of layout template Y, the tablet can display multiple floating windows and a display area on the screen. n2-(n3-1) of the floating windows are located within this display area, while the remaining n3-1 floating windows are located outside this display area. The positions of the n3-1 floating windows and this display area relative to the screen are the same as the positions of the n3 task areas relative to layout template Y.

[0179] Taking n2=3 and n3=2 as an example, referring to Figures 10 and 12A, interface 1001 includes three floating windows: floating window 4011, floating window 5011, and floating window 5012. Furthermore, the layout template 10011a in the template list 10011 of interface 1001 includes two task areas. Therefore, the number of task areas in layout template 10011a is less than the number of floating windows. In response to the user's selection of layout template 10011a in the template list 10011 of interface 1001, the tablet can display interface 1201. Interface 1201 includes floating window 4011 and display area 12011, which includes floating window 5011 and floating window 5012. The floating window 4011 is positioned relative to the display screen in the same way as one vertical task area in layout template 10011a is positioned relative to layout template 10011a, both being located on the left side; the display area 12011 is positioned relative to the display screen in the same way as the remaining vertical task area in layout template 10011b is positioned relative to layout template 10011a, both being located on the right side.

[0180] Optionally, the user can select different layout templates Y. The n2-(n3-1) floating windows within a single display area can be the same or different. The different scenarios are illustrated below with reference to Figures 12B-12D:

[0181] Referring to Figure 12B, in free screen mode, the tablet can display interface 1211. Interface 1211 includes four floating windows: floating window 12111 for APP-4, floating window 12112 for APP-5, floating window 12113 for APP-6, and floating window 12114 for APP-7. Interface 1211 also includes a template list 10011. Layout templates 10011d and 10011b in template list 10011 both include three task areas, which represents a situation where the number of task areas is less than the number of floating windows.

[0182] Referring to Figures 12B and 12C, in response to a user's selection of layout template 10011b in interface 1211, the tablet can display interface 1221. Interface 1221 includes floating window 12111, floating window 12114, and display area 12211, which includes floating window 12112 and floating window 12113. The position of floating window 12111 relative to the display screen is the same as the position of the vertical task area in layout template 10011b relative to layout template 10011b, both located on the left side; the position of floating window 12114 relative to the display screen is the same as the position of one horizontal task area in layout template 10011b relative to layout template 10011b, both located on the upper right side; the position of display area 12211 relative to the display screen is the same as the position of the remaining horizontal task area in layout template 10011b relative to layout template 10011b, both located on the lower right side.

[0183] Referring to Figures 12B and 12D, in response to a user's selection of layout template 10011d in interface 1211, the tablet can display interface 1231. Interface 1231 includes floating window 12111, floating window 12113, and display area 12311. Display area 12311 includes floating window 12112 and floating window 12114. The position of floating window 12111 relative to the display screen is the same as the position of one vertical task area in layout template 10011d relative to layout template 10011d, both located on the left. The position of floating window 12113 relative to the display screen is the same as the position of another vertical task area in layout template 10011d relative to layout template 10011d, both located in the middle area. The position of display area 12311 relative to the display screen is the same as the position of the remaining vertical task area in layout template 10011d relative to layout template 10011d, both located on the right.

[0184] In the interface 1221 described above, floating windows 12112 and 12113 are located in the same display area 12211. Similarly, in the interface 1231 described above, floating windows 12112 and 12114 are located in the same display area 12311. Clearly, selecting different layout templates Y results in different floating windows appearing in the same display area.

[0185] Optionally, the display area corresponding to the horizontal task area (also a horizontal display area) can be used to display floating windows that only support landscape mode and floating windows that support both landscape and portrait modes. The display area corresponding to the vertical task area (also a vertical display area) can be used to display floating windows that only support portrait mode and floating windows that support both landscape and portrait modes. Furthermore, floating windows 12111, 12112, and 12113 only support portrait mode display, while floating window 12114 only supports landscape mode display.

[0186] Based on this, in response to the user's selection operation of layout template 10011b in interface 1211, the tablet can sequentially determine the floating windows displayed in the display areas corresponding to the vertical task area on the left, the horizontal task area on the upper right, and the horizontal task area on the lower right in layout template 10011b. First, the display area corresponding to the vertical task area in layout template 10011b: floating windows 12111, 12112, and 12113, which only support portrait mode, can be displayed in the display area corresponding to the vertical task area. However, since there are three floating windows (12111, 12112, and 12113) and only one display area, the tablet can display the most recently used floating window 12111 in the display area corresponding to the vertical task area in layout template 10011b, such as the display area where floating window 12111 is located in interface 1221. Next, in layout template 10011b, the display area corresponding to the horizontal task area on the upper right is as follows: Floating window 12114 is a floating window that only supports portrait mode. The tablet can display floating window 12114 in the display area corresponding to the horizontal task area on the upper right of layout template 10011b, as shown in the display area where floating window 12114 is located in interface 1221. Finally, the tablet can display the remaining floating windows 12112 and 12113 in the display area corresponding to the task area on the lower right of layout template 10011b, as shown in display area 12211 in interface 1221.

[0187] Similarly, in response to the user's selection of layout template 10011d in interface 1211, the tablet can sequentially determine the floating windows displayed in the display areas corresponding to the three vertical task areas from left to right in layout template 10011d. First, the display areas corresponding to the vertical task areas on the left side of layout template 10011d: floating windows 12111, 12112, and 12113, which only support portrait mode, can be displayed in the display areas corresponding to the vertical task areas. However, since there are three floating windows (12111, 12112, and 12113) and only one display area, the tablet can display the most recently used floating window 12111 from among the three floating windows in the display area corresponding to the vertical task areas on the left side of layout template 10011d, such as the display area where floating window 12111 is located in interface 1231. Next, in the vertical task area corresponding to the center of layout template 10011d, the two remaining floating windows 12112 and 12113, which only support portrait mode, can be displayed in the vertical task area. However, since there are two floating windows (12112 and 12113) and only one display area, the tablet can display the most recently used floating window 12113 in the vertical task area corresponding to the center of layout template 10011d, as shown in the display area where floating window 12113 is located in interface 1231. Finally, the tablet can display the remaining floating windows 12112 and 12114 in the task area corresponding to the right side of layout template 10011d, as shown in display area 12311 in interface 1231.

[0188] In this way, the tablet can prioritize matching the display area based on the floating window's support for landscape and portrait modes. This means it can prioritize displaying floating windows that only support landscape mode in the horizontal display area and those that only support portrait mode in the vertical display area. Furthermore, if multiple floating windows have the same level of support for both landscape and portrait modes, the tablet can match the display area based on the most recently used window, prioritizing those that support the most recent usage.

[0189] Scenario 3: When at least one floating window is displayed, select layout template Z, which has a larger number of task areas than floating windows.

[0190] That is, the number of floating windows is n4 (n4≥1, n4 is an integer), and the number of task areas of the selected layout template Z is n5, n5>n4, and n5 is also an integer.

[0191] In response to a user's selection of layout template Z, the tablet can display at least one floating window and at least one remaining display area on the screen, wherein the at least one remaining display area does not include the floating window, and the positions of the at least one floating window and the at least one remaining display area relative to the screen are the same as the positions of multiple task areas in layout template Z relative to layout template Z.

[0192] Taking n4=1 and n5=2 as an example, referring to Figures 10 and 13, interface 1001 includes three floating windows: floating window 4011, floating window 5011, and floating window 5012. Furthermore, the layout template 10011c in the template list 10011 of interface 1001 includes four task areas. Therefore, the number of task areas in layout template 10011c is greater than the number of floating windows. In response to the user's selection of layout template 10011c in the template list 10011 of interface 1001, the tablet can display interface 1301. Interface 1301 includes floating windows 4011, 5011, and 5012, and a display area 13011. Floating windows 13011 do not include other floating windows; this is the remaining display area. The positions of floating windows 4011, 5011, and 5012 relative to the display screen correspond one-to-one with the positions of the three horizontal task areas in layout template 10011c relative to layout template 10011a, located on the upper left, lower left, and upper right sides respectively. The position of display area 13011 relative to the display screen corresponds to the position of the remaining horizontal task area in layout template 10011c relative to layout template 10011c, both located on the lower right side.

[0193] In the remaining display area, in response to launching an application, the tablet can also display a floating window in that area. For details on how to launch an application and display a floating window within a display area, please refer to the relevant explanations in section four below, such as those for methods one through three; further details will not be provided here.

[0194] In some embodiments, the tablet may employ a fifth method to determine the floating windows displayed in each of the above-described scenarios one through three. For details on the fifth method, please refer to the following comprehensive description of the methods; further explanation will not be provided here.

[0195] Scenario 4: If the floating window is not displayed, select layout template W. Layout template W can be any layout template.

[0196] Even without the floating window displayed, the tablet can still display the layout template in response to user actions such as clicking the layout button.

[0197] Referring to Figures 3 and 14, interface 301 does not include a floating window, representing a case where the floating window is not displayed. In response to a user's click on button 3011 in interface 301, the tablet can display interface 1401, which may also include template list 10011. Template list 10011 includes six layout templates: layout template 10011a, layout template 10011b, and layout template 10011c.

[0198] In response to the user's selection of layout template W, the tablet can display multiple display areas on the screen. The positions of these multiple display areas relative to the screen are identical to the positions of the multiple task areas in layout template W relative to layout template W.

[0199] Referring to Figures 14 and 15, in response to a user's selection of layout template 10011b from template list 10011 in interface 1401, the tablet can display interface 1501. Interface 1501 includes three display areas: display area 15011, display area 15012, and display area 15013. The positions of these three display areas relative to the display screen correspond one-to-one with the positions of the three task areas in layout template 10011b relative to layout template 10011b.

[0200] In each display area, in response to an application launch, the tablet can display a floating window for the application within that area. Below are several ways to launch applications and display floating windows within the task area.

[0201] Method 1

[0202] In response to a user dragging an app icon into the display area, the tablet can launch the app and display its floating window within that area.

[0203] Referring to Figures 15 and 16, in response to the user dragging the APP-1 icon 3012 from the bottom taskbar of interface 1501 to the display area 15011, the tablet can display interface 1601. The difference from interface 1501 is that the display area 15011 in interface 1601 includes a floating window 4011 for APP-1.

[0204] Method 2

[0205] The tablet can display recommended apps within the display area, such as showing the app icon. In response to user actions on the recommended apps, such as clicking the app icon, the tablet can launch the recommended app and display a floating window of it within the display area. This allows users to quickly launch apps and view floating windows through the recommended apps in the display area, saving time searching for apps and improving human-computer interaction efficiency.

[0206] Referring to Figures 15 and 16, the display areas 15011, 15012, and 15013 in interface 1501 all include application icons for recommended apps. For example, the recommended apps in display area 15011 include APP-1, APP-2, APP-3, APP-6, APP-10, APP-8, APP-7, APP-20, and APP-5; the recommended apps in display area 15012 include APP-2, APP-3, APP-6, APP-20, APP-8, APP-7, APP-1, and APP-5; and the recommended apps in display area 15013 include APP-2, APP-8, APP-9, APP-3, APP-6, APP-7, APP-20, APP-1, and APP-13. Taking the display area 15011 in interface 1501 as an example, in response to the user's click operation on the icon 3012 of APP-1 in the display area 15011 of interface 1501, the tablet can also display interface 1601.

[0207] Once the tablet displays a floating window within the display area, recommended apps within that area are not shown. For example, display area 15011 in interface 1601 includes floating window 4011 but does not include icons for recommended apps.

[0208] Within the same layout template, the recommended applications and / or order in multiple display areas can be exactly the same, partially the same, or completely different.

[0209] For example, in interface 1501, the recommended applications in display areas 15011, 15012 and 15013 are different, and the order of the recommended applications is also different.

[0210] For example, the recommended applications and their order differ between the horizontal display area corresponding to the horizontal task area and the vertical display area corresponding to the vertical task area. For instance, the horizontal display area may recommend applications that only support landscape mode and applications that support both landscape and portrait modes, while the vertical display area may recommend applications that only support portrait mode and applications that support both landscape and portrait modes.

[0211] The recommended application and / or order in different layout templates can be exactly the same, partially the same, or completely different.

[0212] Furthermore, the recommended applications and / or their order within each display area can change dynamically as applications are launched in other display areas.

[0213] If no application is launched in display area A2, the tablet displays a set of recommended applications n1 in display area A1. If application B1 is launched in display area A2, the tablet displays a set of recommended applications n2 in display area A1. The recommended applications in n2 are different from those in n1, and / or the order of the recommended applications in n2 is different from the order of the recommended applications in n1.

[0214] Referring to Figures 15 and 16, taking display area A1 as display area 15012 or 15013 and display area A2 as display area 15011 as an example: In interface 1501, no applications are running in display area 15011. The first four recommended applications in display area 15012 (n1) are APP-2, APP-3, APP-6, and APP-20, respectively. The first four recommended applications in display area 15013 (n1) are APP-2, APP-8, APP-9, and APP-3, respectively. In interface 1601, a floating window 4011 for APP-1 is displayed in display area 15011, indicating that APP-1 is running. The first four recommended applications in display area 15012 (n2) in interface 1601 are APP-3, APP-20, APP-6, and APP-9, which is different from the recommended applications in display area 15012 (n1) in interface 1501. Furthermore, the first four recommended applications in the display area 15013 of interface 1601 are APP-2, APP-9, APP-5, and APP-6, which is different from the recommended application set n1 in the display area 15013 of interface 1501.

[0215] It should be noted that this explanation only uses the example of changing the recommended app set when launching the app using method two. Optionally, launching the app using method one (mentioned above) or method three (described below) can also cause a similar change in the recommended app set, which will not be elaborated upon here.

[0216] In some embodiments, the tablet may employ a third method to determine recommended applications in each display area. For a detailed description of the third method below, please refer to the overall description of the method; further details will not be provided here.

[0217] Method 3

[0218] The display area can include a view button C1 for all applications. In response to a user's triggering action on the view button C1, such as clicking, the tablet can display an application panel D1, which includes more recommended applications. In response to a user's triggering action on any recommended application in the application panel D1, such as clicking, the tablet can launch that recommended application and display its floating window in the display area.

[0219] Referring to Figures 16 and 17A, the "+" 16011 within display area 15012 of interface 1601 is the view button C1. In response to the user's click on "+" 16011, the tablet can display interface 1701. Interface 1701 includes application panel 17011, which is application panel D1. The "Application Suggestions" in application panel 17011 include recommended applications such as APP-3, APP-20, APP-6, and APP-9, which are the same as those in display area 15012 of interface 1601, as well as APP-30, APP-33, and APP-25.

[0220] Referring to Figures 17A and 17B, in response to the user's click on the icon 17011a of APP-33 in interface 1701, the tablet can display interface 1711. The display area 15012 in interface 1711 includes a floating window 17111, which includes the application interface of APP-33.

[0221] In some embodiments, the tablet may employ a fourth method to determine recommended applications in the application panel D1. For a detailed description of the fourth method below, please refer to the summary description of the methods; further details will not be provided here.

[0222] The application panel D1 can also include all applications, such as the "All" area of ​​application panel 17011 which includes all applications. In response to a user's trigger action on any application among all applications, the tablet can also launch the application and display its floating window in the display area.

[0223] Additionally, the bottom taskbar can also include a "View All Apps" button C2. In response to the user's activation of button C2, the tablet can display an app panel D2, which can also include recommended apps and all apps. The recommended apps in app panel D2 can differ from those in app panel D1, and / or the order of the recommended apps can be different.

[0224] Referring to Figures 16 and 18, button 16012 in the bottom taskbar of interface 1601 is the view button C2. In response to the user's click on button 16012, the tablet can display interface 1801. Interface 1801 includes application panel 18011, which is application panel D2. The "Application Suggestions" in application panel 18011 include recommended applications such as APP-3, APP-6, APP-2, APP-10, APP-8, APP-7, APP-20, APP-1, APP-13, APP-5, etc., which differ from the recommended applications and their order in application panel 17011 of interface 1701.

[0225] For details regarding the differences between the recommended applications in Application Panel D1 and Application Panel D2, and / or the specific circumstances of different recommended applications, please refer to the relevant explanation of the fourth method below, which will not be discussed in detail here.

[0226] Optionally, the above methods 1, 2 and 3 can be flexibly combined to display floating windows in multiple display areas using multiple methods.

[0227] For example, the tablet can launch the application and display the floating window in the display area 15011 of the interface 1501 in method one, launch the application and display the floating window in the display area 15012 of the interface 1501 in method two, and launch the application and display the floating window in the display area 15013 of the interface 1501 in method three.

[0228] For example, the tablet can launch the application and display the floating window in display areas 15011 and 15012 of the interface 1501 using method two, and launch the application and display the floating window in display area 15013 of the interface 1501 using method three.

[0229] Scenario 3, Recommended task group.

[0230] In free screen mode, in response to user triggering of layout buttons, such as button 3011, the tablet can also display template tabs and task group tabs. For example, "Quick Layout" in interfaces 1001 and 1401 is a template tab, and "Smart Recommendation" is a task group tab.

[0231] By default, the template tag is selected. When the template tag is selected, the tablet can display the layout template. For example, in interfaces 1001 and 1401 above, "Quick Layout" is displayed in bold and underlined, indicating that "Quick Layout" is selected.

[0232] When a template label is selected, in response to the user's selection of a task group label, the tablet can display the selected task group label and the unselected template label.

[0233] When a task group label is selected, in response to the user's selection of a template label, the tablet can display the selected template label and the unselected task group label.

[0234] When the template tag is selected, the tablet can display a list of templates, thereby displaying layout templates. For details, please refer to the previous text about Interface 1001 and Interface 1401 and their descriptions, which will not be repeated here.

[0235] When the task group tab is selected, the tablet can display a list of task groups. This list can include at least one recommended task group, and each recommended task group contains layout styles for multiple applications. In this way, the tablet can recommend task groups and their layouts.

[0236] When at least one floating window is displayed, each recommended task group includes multiple applications, including the application to which the at least one floating window belongs, as well as other applications. In this way, the tablet can recommend task groups that include the currently displayed application and other applications.

[0237] Taking a single floating window as an example (see Figures 4, 19, and 20A), interface 401 includes the floating window 4011 of APP-1, thus having one floating window. In response to the user's click on button 3011 in interface 401, the tablet can display interface 1901. "Quick Layout" is selected in interface 1901, which includes a template list 10011. In response to the user's selection of "Smart Recommendation" in interface 1901, the tablet can display interface 2001. "Smart Recommendation" is selected in interface 2001, which includes a task group list 20011. The task group list 20011 includes six recommended task groups: 20011a, 20011b, 20011c, 20011d, 20011e, and 20011f. Each recommended app group contains multiple apps, including APP-1, which is the same as floating window 4011. Furthermore, these multiple apps also include other apps; for example, recommended task group 20011a includes APP-3, recommended task group 20011b includes APP-2 and APP-3, and recommended task group 20011c includes APP-2, APP-4, and APP-5…

[0238] It should be noted that, for the sake of simplicity, the applications in the recommended task group are all represented by P in the diagram. For example, APP-1 is simplified to P1, APP-2 is simplified to P2, and so on. This will not be further stated below.

[0239] Furthermore, the recommended task groups displayed on the tablet are essentially icons representing those groups. For example, recommended task group 20011a in interface 2001 is essentially an icon that includes APP-1, APP-3, and the border. The applications within the recommended task groups are essentially application identifiers, such as application icons. For simplicity, this article will directly use "recommended task groups" and "applications within recommended task groups" to describe them; further details will not be elaborated upon below.

[0240] In the task group list, corresponding to a layout template, the tablet can display one or more recommended task groups. The layout style of multiple applications in each recommended task group is the same as the layout style of multiple task areas in the corresponding layout template. Multiple applications and / or multiple applications in different recommended task groups may have different layouts. Alternatively, in the task group list, corresponding to a layout template, the tablet can display at most one recommended task group, and the layout style of multiple applications in this maximum recommended task group is the same as the layout style of multiple task areas in the corresponding layout template. This article mainly uses the example of displaying at most one recommended task group corresponding to a layout template, as shown in the interface 2001 in Figure 20A.

[0241] In this context, the layout styles of multiple applications in the recommended task group are the same as the layout styles of multiple task areas in the corresponding layout template. This can also be understood as: the positions of multiple applications relative to the recommended task group and the positions of multiple task areas relative to the layout template are identical.

[0242] Referring to Figure 20A, the task group list 20011 in interface 2001 includes recommended task groups 20011a, 20011b, 20011c, 10011d, 10011e, and 10011f, which correspond one-to-one with layout templates 10011a, 10011b, 10011c, 10011d, 10011e, and 10011f. Furthermore, the layout styles of multiple applications within the recommended task groups are identical to the layout styles of multiple task areas within their corresponding layout templates. For example, the position of APP-1 in recommended task group 20011a relative to the position of recommended task group 20011a is the same as the position of one vertical task area in layout template 10011a, both located on the left; the position of APP-3 in recommended task group 20011a relative to the position of recommended task group 20011a is the same as the position of the remaining vertical task area in layout template 10011a, both located on the right.

[0243] In the task group list, corresponding to at least one layout template among multiple layout templates, the tablet may not display the recommended task group. Referring to Figures 19 and 20B, in response to the user's selection of "Smart Recommendation" in interface 1901, the tablet can display interface 2011. The task group list 20111 in interface 2011 does not include the recommended task group 20011b corresponding to layout template 10011b, indicating that the tablet has not found a recommended task group corresponding to layout template 10011b. For example, if the historical task group data does not include task group data for applications using layout template 10011b and including at least one currently displayed floating window, the tablet will not find the recommended task group corresponding to layout template 10011b.

[0244] In the task group list, the tablet may also not display recommended task groups. Referring to Figures 19 and 20C, in response to the user's selection of "Smart Recommendation" in interface 1901, the tablet may display interface 2021. The task group list 20211 in interface 2021 will display "No Recommendations," indicating that there are no recommended task groups. For example, if the historical task group data does not contain task group data that includes at least one application belonging to the currently displayed floating window, the tablet may not display recommended task groups.

[0245] Additionally, even without a floating window, the task group list can include recommended task groups that have been frequently used in historical layout data. Referring to Figures 14 and 21, interface 1401 does not include a floating window. In response to the user's selection of "Smart Recommendation" in interface 1401, the tablet can display interface 2101, which includes a task group list 21011 containing multiple recommended task groups.

[0246] Without displaying a floating window, different recommended task groups can include completely different applications. For example, the applications in recommended task group 21011a and recommended task group 21011b in task group list 21011 are completely different. This increases the diversity of recommended task groups.

[0247] In some embodiments, the tablet may use a second method to determine the content displayed in the task group list, such as determining whether to display recommended task groups, or determining which recommended task groups to display. For a detailed description of the second method below, please refer to the overall description of the methods; further explanation will not be provided here.

[0248] In scenario 3 above, the way the tablet displays the task group list in response to the user's selection of a task group label is merely one exemplary method for displaying the task group list. Optionally, the tablet may also display the task group list in response to the user's trigger action 1 on the layout button, such as a click action.

[0249] Referring to Figures 4 and 22A, in response to a user's click on button 3011 in interface 401, the tablet can display interface 2201. Interface 2201 includes a template list 10011 and a task group list 20011, which are displayed separately in two separate panels.

[0250] It should be noted that the display formats of the template list and task group list mentioned above are merely illustrative.

[0251] Optionally, referring to Figures 4 and 22B, in response to a user's click on button 3011 in interface 401, the tablet can display interface 2211. Interface 2211 includes panel 22111, the upper part of which includes template list 22111a and the lower part includes task group list 22111b. Furthermore, template list 22111a only includes a portion of the layout templates; in response to a user's swipe operation in template list 22111a, the tablet can display more layout templates in template list 22111a. Similarly, task group list 22111b only includes a portion of the layout templates; in response to a user's swipe operation in task group list 22111b, the tablet can display more recommended task groups in task group list 22111b.

[0252] Alternatively, referring to Figure 22C, in the absence of recommended task groups, the tablet can display interface 2221, which includes a template list 22111a but does not include a task group list.

[0253] Additionally, for the parts of template list 22111a that are not explained in detail, please refer to the previous explanations of template lists, such as template list 10011, which will not be repeated here. Similarly, for the parts of task group list 22111b that are not explained in detail, please refer to the previous explanations of task group lists, such as task group list 20011 and task group list 20111, which will not be repeated here either.

[0254] After displaying the recommended task groups, in response to the user's selection of any recommended task group, the tablet can display multiple floating windows corresponding to multiple applications within that recommended task group. The layout style of these floating windows is the same as the layout style of the applications within the recommended task group. In other words, the position of each floating window relative to the screen corresponds one-to-one with the position of each application relative to the recommended task group. In this way, in response to a single user selection, the tablet can launch multiple applications and complete the layout display of the floating windows, improving human-computer interaction efficiency.

[0255] Referring to Figures 20A and 23A, interface 2001 includes a floating window 4011 for APP-1. In response to a user's selection of the recommended task group 20011a from the task group list 20011 in interface 2001, the tablet can display interface 2301. Interface 2301 includes floating windows 4011 for APP-1 and 5012 for APP-2. Furthermore, the layout style of floating windows 4011 and 5012 in interface 2301 is the same as that of APP-1 and APP-3 in recommended task group 20011a. Specifically, the position of floating window 4011 relative to the display screen is the same as that of APP-1 relative to recommended task group 20011a, both located on the left; the position of floating window 5012 relative to the display screen is the same as that of APP-3 relative to recommended task group 20011a, both located on the right.

[0256] Referring to Figures 20A and 11, interface 2001 includes a floating window 4011 for APP-1. In response to a user's selection of the recommended task group 20011b from the task group list 20011 in interface 2001, the tablet can display interface 1101. Interface 1101 includes floating windows 4011 for APP-1, 5011 for APP-2, and 5012 for APP-3. Furthermore, the layout style of floating windows 4011, 5011, and 5012 in interface 1101 is the same as the layout style of APP-1, APP-2, and APP-3 in the recommended task group 20011b. Specifically, the positions of floating window 4011 relative to the screen are the same as those of APP-1 relative to recommended task group 20011b, both located on the left side; the positions of floating window 5011 relative to the screen are the same as those of APP-2 relative to recommended task group 20011b, both located on the upper right side; and the positions of floating window 5012 relative to the screen are the same as those of APP-3 relative to recommended task group 20011b, both located on the lower right side.

[0257] After the user selects a recommended task group, the tablet can display the selected recommended task group, thus indicating the currently used recommended task group. Referring to Figure 23A, in the task group list 20011 of interface 2301, recommended task group 20011a is filled in dark, indicating that recommended task group 20011a is selected.

[0258] Optionally, after the user selects a recommended task group, the tablet may not display the task group list, allowing the layout effect of using the recommended task group to be fully presented. Referring to Figures 20A and 23B, in response to the user's selection of recommended task group 20011b from the task group list 20011 in interface 2001, the tablet may also display interface 2311. Compared to interface 2301, interface 2311 does not include the task group list 20011.

[0259] Of course, after displaying interface 2301, the tablet can also display interface 2311 in response to user triggering operations on areas outside the task group list 20011 or triggering operations on layout buttons 1.

[0260] Scenario 4, one-click layout.

[0261] In FreeScreen mode, in response to the user's triggering of the layout button, the tablet can also display a one-click layout button. When multiple floating windows are involved, in response to the user's triggering of the one-click layout button, the tablet can layout multiple currently displayed floating windows. This way, the tablet can complete the layout of the floating windows without the user needing to manually adjust them or select a layout template.

[0262] Referring to Figures 10 and 24A, interface 1001 includes floating windows 4011, 5011, and 5012, arranged horizontally in sequence. The "One-Click Layout" button in template list 10011 within interface 1001 is a one-click layout button. In response to the user's click on "One-Click Layout," the tablet can display interface 2401, which includes floating windows 4011, 5011, and 5012, and has the same layout style as layout template 10011e. It is evident that the layout style of the multiple floating windows has changed, indicating that the tablet has laid out multiple floating windows. Of course, the tablet can also achieve other layout styles, such as the layout style shown in interface 1101 in Figure 11; this application does not specifically limit this.

[0263] After the user triggers the one-click layout button, the tablet can display the pressed one-click layout button, indicating that one-click layout is currently in use. Referring to Figure 24A, the background of the "one-click layout" button in template list 10011 in interface 2401 is dark, indicating that "one-click layout" is in a pressed state.

[0264] Optionally, after the user triggers the one-click layout button, the tablet may not display the template list, allowing the layout effect using one-click layout to be fully presented. Referring to Figures 10 and 24B, in response to the user's click on "One-Click Layout" in interface 1001, the tablet may also display interface 2411. Compared to interface 2401, interface 2411 does not include template list 10011.

[0265] Of course, after displaying interface 2401, the tablet can also display interface 2411 in response to user triggering operations on areas outside the template list 20011 or triggering operations on layout buttons 1.

[0266] In some embodiments, the tablet may employ a first method to layout multiple floating windows, such as determining the layout template to be used and the display position of each floating window. For a detailed description of the first method below, please refer to the overall description of the method; further explanation will not be provided here.

[0267] Additionally, when only one floating window is displayed or no floating window is displayed, the tablet may not respond to the user's triggering of the one-click layout button.

[0268] Referring to Figure 14, the interface 1401 does not include a floating window. In response to the user's click operation on "One-click Layout" in the template list 10011 in the interface 1401, the tablet may not respond.

[0269] Referring to Figure 19, the interface 1901 includes a floating window 4011. The tablet may not respond to the user's click operation on "One-click Layout" in the template list 10011 in the interface 1901.

[0270] In scenario 4 above, the way the tablet lays out the floating window in response to the user's trigger operation on the one-click layout button is only one example. Optionally, the tablet can also lay out multiple floating windows in response to the user's trigger operation on the layout button 2, such as a long press operation on button 3011.

[0271] This application will exemplarily describe the main methods involved in implementing the interface response described above.

[0272] First Method

[0273] The first method can be used in scenario 4 above.

[0274] Referring to Figure 25, in the case of multiple floating windows displayed on a tablet, as shown in interface 1001 above, we will introduce the specific implementation of the first method for determining the layout of multiple floating windows on the tablet.

[0275] S2501. In response to the user's trigger operation on the one-click layout button, the tablet queries whether there is candidate task group data 0. The number of applications in the task group in candidate task group data 0 is the same as the number of floating windows in multiple floating windows. If not, execute S2502-S2503; if yes, execute S2504-S2505.

[0276] The tablet can store historical task group data from the user's free screen mode. Each historical task group record includes the following fields:

[0277] Task groups represent a combination of applications and their order. For example, in task groups APP-1, APP-2, and APP-3, the applications are APP-1, APP-2, and APP-3, and the order of APP-1, APP-2, and APP-3 is 1st, 2nd, and 3rd respectively.

[0278] A template indicates the layout template used for this task group. The task areas within the layout template also have a specific order. For example, in layout template 10011a, the vertical task area on the left is the first task area, and the vertical task area on the right is the second task area. As another example, in layout template 10011b, the vertical task area on the left is the first task area, the horizontal task area in the upper right is the second task area, and the horizontal task area in the lower right is the third task area.

[0279] The order in which tasks are applied within a task group corresponds to the order of task areas in the layout template. For example, if APP-1 is in the first position, it means that APP-1's floating window is displayed in the display area corresponding to the first task area in the layout template; if APP-2 is in the second position, it means that APP-1's floating window is displayed in the display area corresponding to the second task area in the layout template, and so on.

[0280] The number of times the layout template is used indicates the number of times the task group is laid out using this layout template.

[0281] Last Use Time indicates the last time this layout template was used to lay out the task group.

[0282] For example, referring to Table 1 below, the various fields in the historical task group data are described. The tablet can store historical task group data as shown in Table 1 below:

[0283] Table 1

[0284] The first historical task group data in Table 1 above indicates that: APP-1 and APP-2 were laid out using layout template 10011a. The floating window of APP-1 was displayed in the display area corresponding to the first task area of ​​layout template 10011a, and the floating window of APP-2 was displayed in the display area corresponding to the second task area (the vertical task area on the right). Furthermore, this layout was used a total of 10 times, with the last instance occurring on 2024-11-20 22:00:00.

[0285] The second historical task group data in Table 1 above indicates that: when layout template 10011b was used to layout APP-1, APP-2, and APP-3, the floating window of APP-1 was displayed in the display area corresponding to the first task area (the vertical task area on the left) of layout template 10011b; the floating window of APP-2 was displayed in the display area corresponding to the second task area (the horizontal task area in the upper right); and the floating window of APP-3 was displayed in the display area corresponding to the third task area (the horizontal task area in the lower right). Furthermore, this layout was used a total of 20 times, with the last instance occurring on 2024-11-22 at 15:00:00.

[0286] The third historical task group data in Table 1 above indicates that: when layout template 10011c was used to layout APP-1, APP-4, APP-5, and APP-2, the floating window of APP-1 was displayed in the display area corresponding to the first task area (the upper left horizontal task area) of layout template 10011c; the floating window of APP-4 was displayed in the display area corresponding to the second task area (the lower left horizontal task area); the floating window of APP-5 was displayed in the display area corresponding to the third task area (the upper right horizontal task area); and the floating window of APP-2 was displayed in the display area corresponding to the fourth task area (the lower right horizontal task area). Furthermore, this layout method was used a total of 22 times, with the last instance occurring on 2024-11-20 17:00:00.

[0287] Historical task group data primarily includes user-initiated layout data. The tablet updates the historical task group data after each user-initiated layout. This way, the recorded historical task group data clearly reflects the user's usage habits.

[0288] For example, historical task group data could include, in scenario 2, case 3, the layout data of when the user selects a layout template and launches the application in each display area. Based on this, the tablet can update the historical task group data in response to the user selecting a layout template and launching the application in each display area.

[0289] For example, historical task group data includes layout data of the recommended task group selected by the user in Scenario 3. Based on this, the tablet can update the historical task group data in response to the user's selection of the recommended task group.

[0290] Taking the user's selection of recommended task group 20011b in interface 2001 shown in Figure 20A as an example: Since recommended task group 20011b corresponds to layout template 10011b, the tablet can obtain the template's field value as 10011b; in recommended task group 20011b, APP-1 is laid out in the first task area, APP-2 in the second task area, and APP-3 in the third task area, so the tablet can obtain the task group's field values ​​as APP-1, APP-2, and APP-3. Simultaneously, in the second data entry of Table 1 above, the template's field value is 10011b, and the task group's field values ​​are APP-1, APP-2, and APP-3. Based on this, the tablet can increment the "Number of Uses" in the second data entry of Table 1 by 1 and update the last usage time to the time of this selection of recommended task group 20011b.

[0291] The tablet can store historical task group data in a database, such as the suggested database (suggestion.db) below. When multiple floating windows are displayed, in response to a user's triggering of the one-click layout button, the tablet can retrieve candidate task group data 0 from the database. Optionally, in response to a user's long-pressing of the layout button, the tablet can also retrieve candidate task group data 0 from the database.

[0292] The tablet can compare the number of applications included in a task group from multiple historical task group data with the number of currently displayed floating windows, and obtain candidate task group data 0 with the same number of applications and floating windows.

[0293] Taking interface 1001 as an example, interface 1001 includes three floating windows: the floating window of APP-1, the floating window of APP-2, and the floating window of APP-3. By querying historical task group data, the tablet can obtain four candidate task group data with a total of 3 applications, as shown in Table 2 below.

[0294] Table 2

[0295] If candidate task group data 0 is found, the tablet can lay out multiple floating windows based on candidate task group data 0, as shown in S2504-S2506 below, so that the layout result matches the user's historical layout preferences.

[0296] If no candidate task group data 0 is found, such as the number of applications and floating windows in each historical task group data being different, the tablet can lay out multiple floating windows based on information such as support for landscape and portrait screens, and the number of floating windows, as shown in S2502-S2503 below, so that the layout result matches the display requirements of the floating windows.

[0297] S2502, The tablet selects target layout template 1 from multiple layout templates. Target layout template 1 is the layout template with the highest matching degree between the multiple floating windows and the task area number and the number of floating windows, and the screen orientation of the multiple floating windows.

[0298] The tablet can compare the number of task areas included in multiple layout templates with the number of currently displayed floating windows to obtain layout templates with the same number of task areas as the number of floating windows (denoted as candidate layout templates). Then, based on the orientation (horizontal or vertical) of the task areas in each candidate layout template, the tablet can calculate the matching degree between the candidate layout template and the multiple floating windows in terms of their support for both horizontal and vertical screen orientations. The layout template with the highest matching degree is selected as the target layout template 1.

[0299] In cases where at least two layout templates have the same and highest matching degree, the tablet can choose either one. Alternatively, multiple layout templates can have a fixed order, and the tablet can choose the one that appears first in the order. For example, the order of the multiple layout templates is consistent with the display order of the multiple layout templates in template list 10011 in Figure 10, namely layout template 10011a, layout template 10011d, layout template 10011b, layout template 10011e, layout template 10011f, and layout template 10011c.

[0300] The orientation of the task area in the layout template is pre-configured. The task area orientation includes both horizontal and vertical orientations. The orientation of the task area is the same as the orientation of its corresponding display area. For example, a horizontal task area corresponds to a horizontal display area, and a vertical task area corresponds to a vertical display area. The horizontal display area can display floating windows that only support landscape mode and those that support both landscape and portrait modes, while the vertical display area can display floating windows that only support portrait mode and those that support both landscape and portrait modes.

[0301] For example, in the template list 10011 shown in Figure 10, the layout template 10011a has two vertical task areas. Therefore, the layout template 10011a can display two floating windows that only support portrait mode, or one floating window that only supports portrait mode and one floating window that supports both portrait and landscape modes, or two floating windows that support both portrait and landscape modes.

[0302] For example, layout template 10011b in template list 10011 shown in Figure 10 has one vertical task area and two horizontal task areas. Therefore, layout template 10011b can satisfy the display of one floating window that only supports portrait screen and two floating windows that only support landscape screen, or one floating window that only supports portrait screen and two floating windows that support both portrait and landscape screens, or two floating windows that only support landscape screen and one floating window that supports both portrait and landscape screens, or one floating window that only supports landscape screen, one floating window that only supports portrait screen and one floating window that supports both portrait and landscape screens, or three floating windows that support both portrait and landscape screens.

[0303] Furthermore, when calculating the matching degree of each candidate layout template, the tablet can match the orientation of the task area in the candidate layout template with the support of multiple floating windows for landscape and portrait screens to obtain the number of multiple floating windows that the candidate layout template can support. The larger the number, the higher the matching degree, and thus the matching degree of the candidate layout template can be obtained.

[0304] For example, if layout template 10011a supports displaying one of multiple floating windows, the matching degree is 1; if it supports displaying two of multiple floating windows, the matching degree is 2; and if it supports displaying three of multiple floating windows, the matching degree is 3.

[0305] Example 1: There are 3 floating windows, 2 of which only support landscape mode and the remaining 1 only supports portrait mode.

[0306] Layout templates 10011d, 10011b, and 10011e all include three task areas, the same number as the number of floating windows. Layout template 10011d has three vertical task areas, allowing it to display one of the three floating windows that only supports portrait mode, with a match score of 1. Layout template 10011b has one vertical task area and two horizontal task areas, allowing it to display one of the three floating windows that only supports portrait mode and two that only support landscape mode, with a match score of 3. Layout template 10011e also has one vertical task area and two horizontal task areas, allowing it to display one floating window that only supports portrait mode and two that only support landscape mode, with a match score of 3. As can be seen, layout templates 10011b and 10011e have the highest matching degree. The target layout template 1 can be the one that comes first in the order of layout templates 10011b and 10011e, such as layout template 10011b.

[0307] Example 2: There are 3 floating windows, 2 of which only support portrait mode, and the remaining floating window supports both portrait and landscape modes.

[0308] Layout templates 10011d, 10011b, and 10011e all include three task areas, the same number as the number of floating windows. Layout template 10011d has three vertical task areas, allowing it to display two floating windows that only support portrait mode and one that supports both portrait and landscape modes, with a matching degree of 3. Layout template 10011b has one vertical task area and two horizontal task areas, allowing it to display one floating window that only supports portrait mode and one that supports both portrait and landscape modes, with a matching degree of 2. Layout template 10011e also has one vertical task area and two horizontal task areas, allowing it to display one floating window that only supports portrait mode and one that supports both portrait and landscape modes, with a matching degree of 2. Therefore, layout template 10011d has the highest matching degree, and the target layout template 1 can be layout template 10011d.

[0309] S2503, the tablet uses the target layout template 1 to arrange multiple floating windows.

[0310] For example, the tablet can first allocate display areas for floating windows that only support landscape mode and floating windows that only support portrait mode. The floating windows that only support landscape mode are assigned to the horizontal display area corresponding to the horizontal task area in target layout template 1, and the floating windows that only support portrait mode are assigned to the vertical task area corresponding to the vertical task area in target layout template 1. Then, the tablet assigns floating windows that support both landscape and portrait mode to the display areas corresponding to the remaining task areas in target layout template 1. This prioritizes meeting the needs of both landscape and portrait modes, making the display of floating windows that only support landscape mode and floating windows that only support portrait mode more reasonable.

[0311] Furthermore, the tablet can allocate task areas according to the launch order of multiple floating windows: first, floating windows that only support landscape mode, and second, floating windows that only support portrait mode. The task area is allocated first when launched, and then later when launched. This prioritizes the display needs of the first launched floating window.

[0312] Similarly, tablets can also allocate task areas to floating windows that are supported in both portrait and landscape modes according to the launch order of multiple floating windows.

[0313] S2504. The tablet filters out target task group data 1 from candidate task group data 0. Target task group data 1 contains task group data from candidate task group data 0 that includes the task group with the most display applications.

[0314] The tablet can compare the applications included in the task groups of each candidate task group data 0 with the displayed applications to obtain the number of displayed applications included in the task groups of each candidate task group data 0, thereby obtaining the target task group data 1 that includes the most displayed applications.

[0315] Continuing with the example of interface 1001 shown in Table 2 and Figure 10 above, the displayed applications are APP-1, APP-2, and APP-3. The tablet compares the applications included in the task groups in each candidate task group data 0 in Table 2 with the displayed applications APP-1, APP-2, and APP-3, and obtains the following comparison results: The task groups APP-3, APP-1, and APP-2 in the first candidate task group data include APP-1, APP-2, and APP-3, a total of 3 displayed applications; the task groups APP-1, APP-4, and APP-3 in the second candidate task group data include APP-1 and APP-3, a total of 2 displayed applications; the candidate task groups APP-5, APP-2, and APP-8 in the third candidate task group data include APP-2, a total of 1 displayed application; and the candidate task groups APP-3, APP-9, and APP-10 in the fourth candidate task group data include APP-3, a total of 1 displayed application. As can be seen, the first candidate task group data includes the most display applications in task groups APP-3, APP-1, and APP-2. Therefore, the target task group data 1 is the first candidate task group data in Table 2 above.

[0316] If at least two candidate task group data 0s contain the same maximum number of display applications, then target task group data 1 is one of the at least two candidate task group data 0s. The tablet may choose one randomly. Alternatively, the tablet may select target task group data 1 from the at least two candidate task group data 0s based on the number of times it has been used and / or the time of its last use.

[0317] For example, the tablet can select candidate task group data 0 with the most usage frequency, and / or candidate task group data 0 with the most recent usage time among those whose usage frequency differs from the most frequent usage frequency within a preset range. The preset range can be a numerical value, such as 3 or 5. Alternatively, the preset range can be a percentage value, such as 30% or 20%. In this way, the tablet can select target task group data 1 with a high usage frequency and the most recent updated usage time.

[0318] Continuing with the example of APP-1, APP-2, and APP-3, the tablet query returned 7 candidate task group data entries with 3 applications. In addition to Table 2 above, Table 3 below also contains 3 candidate task group data entries:

[0319] Table 3

[0320] The three candidate task group data entries in Table 3 all include three applications: APP-1, APP-2, and APP-3. Therefore, there are a total of four candidate task group data entries (the first data entry in Table 2 and the three data entries in Table 3) that include the same maximum number (3) of display applications, as shown in Table 4 below:

[0321] Table 4

[0322] In Table 4 above, the third historical task group data 0 has been used 36 times, the most frequent. Taking a preset range of 30% as an example, the number of uses is above 36*(1-30%) = 25.2, thus satisfying the condition that the difference between the number of uses and the maximum number of uses is within the preset range. The fourth historical task group data 0 in Table 4 has been used 28 times, which is above 25.2. The tablet can compare the last time in the third and fourth historical task group data 0 in Table 4. If the last time of use in the fourth historical task group data 0 is updated, then the target task group data 1 is the fourth historical task group data 0.

[0323] Of course, the tablet can also directly select the candidate task group data 0 with the most usage frequency or the most recent usage time from at least two candidate task group data 0. This application does not impose specific limitations on this.

[0324] S2505, the tablet lays out multiple floating windows according to the target task group and target layout template 2 in the target task group data 1.

[0325] Taking the target task group data 1 as the fourth historical task group data in Table 4 above as an example, the target layout template 2 is layout template 10011b, and the tablet can arrange the multiple floating windows currently displayed according to layout template 10011b.

[0326] In some cases, the target task group data 1 includes all display applications. The tablet can display the floating window of the s-th display application in the target task group in the display area corresponding to the s-th task area in the target layout template 2.

[0327] Taking the target task group data 1 as the fourth candidate task group data 0 in Table 4 above as an example, the target task group is APP-1, APP-2, and APP-3, and the target layout template 2 is 10011b. This means that the floating window of APP-1 is displayed in the display area corresponding to the first task area of ​​layout template 10011b, the floating window of APP-2 is displayed in the display area corresponding to the second task area of ​​layout template 10011b, and the floating window of APP-3 is displayed in the display area corresponding to the third task area of ​​layout template 10011b. Based on this, the tablet can display the floating window 4011 of APP-1 in the display area corresponding to the first task area of ​​layout template 10011b, the floating window 5011 of APP-2 in the display area corresponding to the second task area of ​​layout template 10011b, and the floating window 5012 of APP-3 in the display area corresponding to the third task area of ​​layout template 10011b, as shown in Figure 11.

[0328] In other cases, one of the multiple display applications may not be included in the target task group of target task group data 1. The tablet can display the floating window of the s-th display application in the target task group in the display area corresponding to the s-th task area in the target layout template 2; and display the display applications not included in the target task group in the display areas corresponding to the remaining task areas of the target layout template 2.

[0329] Taking the target task group as APP-2, APP-3, and APP-4, the target layout template 2 as layout template 10011e, and the multiple display applications as APP-1, APP-2, and APP-3 as an example, the target task group includes display applications APP-2 and APP-3, but does not include APP-1. It can be shown that the floating window of APP-2 is displayed in the display area corresponding to the first task area of ​​layout template 10011e, the floating window of APP-3 is displayed in the display area corresponding to the second task area of ​​layout template 10011e, and the floating window of APP-4 is displayed in the display area corresponding to the third task area of ​​layout template 10011e. Based on this, the tablet can display the floating window 5011 of APP-2 in the display area corresponding to the first task area of ​​layout template 10011e, display the floating window 5012 of APP-3 in the display area corresponding to the second task area of ​​layout template 10011e, and display the floating window 4011 of APP-1 in the display area corresponding to the remaining third task area of ​​layout template 10011e, as shown in Figure 24A.

[0330] In other cases, at least two of the multiple display applications are not included in the target task group of target task group data 1. The tablet can display the floating window of the s-th display application in the target task group in the display area corresponding to the s-th task area in the target layout template 2. Furthermore, the tablet can, based on historical task group data including the target layout template 2, display the floating windows of these at least two display applications in the display areas corresponding to the remaining task areas of the target layout template 2, such as displaying them in the display area that has been displayed most frequently in the remaining task areas.

[0331] Taking the target task groups in target task group data 1 as APP-5, APP-2, and APP-8, and the target layout template 2 as layout template 10011e, displaying applications including APP-1, APP-2, and APP-3 as an example:

[0332] The target task group APP-5, APP-2, and APP-8 includes a display application APP-2, and APP-2 is located in the second position in the target task group. This means that the floating window of APP-2 is displayed in the display area corresponding to the second task area in the layout template 10011e. The tablet can display the floating window of APP-2 in the display area corresponding to the second task area of ​​the layout template 10011e.

[0333] The target task groups APP-5, APP-2, and APP-8 do not include the other two display applications APP-1 and APP-3. The remaining task areas are the first and third task areas of layout template 10011e. Furthermore, the tablet retrieved historical task group data including layout template 10011e, as shown in Table 5 below.

[0334] Table 5

[0335] In the historical task group data in Table 5 above, the floating window of APP-1 was displayed 25 times in the display area corresponding to the first task area of ​​layout template 10011e, and 0 times in the display area corresponding to the third task area. Therefore, the floating window of APP-1 was displayed most frequently in the display area corresponding to the first task area of ​​layout template 10011e. Similarly, the floating window of APP-3 was displayed 0 times in the display area corresponding to the first task area of ​​layout template 10011e, and 10 times in the display area corresponding to the third task area. Therefore, the floating window of APP-3 was displayed most frequently in the display area corresponding to the third task area of ​​layout template 10011e. Based on this, the tablet can display the floating window of APP-1 in the display area corresponding to the first task area of ​​layout template 10011e, and the floating window of APP-3 in the display area corresponding to the third task area of ​​layout template 10011e.

[0336] In addition, in the above S2504, if none of the candidate task group data 0, in which the number of applications in the task group is the same as the number of floating windows, are display applications, the tablet cannot obtain the target task group data 1 that meets the conditions.

[0337] Taking multiple display applications, including APP-1, APP-2 and APP-3, as an example, the tablet queries the historical task group data and obtains 3 candidate task group data with 3 applications as shown in Table 6 below.

[0338] Table 6

[0339] In Table 4 above, none of the task groups in candidate task group data 0 include display applications. Using the aforementioned S2504, the tablet struggles to obtain target task group data 1 that meets the requirements. For situations like the one shown in Table 4 where it's difficult to determine target task group data 1, the tablet can identify target task group data 2 within the task groups of candidate task group data 0 that shares the same application category as multiple display applications, and then lay out multiple floating windows according to the target layout template 3 in target task group data 2.

[0340] The application categories include, but are not limited to, at least two of the following: video, social, book, music, game, education, shopping, and news.

[0341] The tablet can compare the application categories of the applications included in the task groups in each candidate task group data with the application categories of the displayed applications to determine the target task group data2 that has the same application categories as multiple displayed applications.

[0342] Taking the example of multiple displayed applications APP-1, APP-2, and APP-3 corresponding to game applications, video applications, and social applications respectively, and continuing with the example in Table 4 above: In the first historical task group data in Table 4, the application categories of task groups APP-4, APP-5, and APP-6 correspond to game applications, book applications, and social applications respectively, which are not exactly the same as the application categories of the multiple displayed applications. In the second historical task group data in Table 1, the application categories of task groups APP-8, APP-11, and APP-9 correspond to social applications, book applications, and music applications respectively, which are not exactly the same as the application categories of the multiple displayed applications. In the third historical task group data in Table 1, the application categories of task groups APP-7, APP-13, and APP-15 correspond to video applications, social applications, and game applications respectively, which are exactly the same as the application categories of the multiple displayed applications. The tablet can determine that the target task group data 2 is the third historical task group data in Table 1.

[0343] Of course, if there are at least two target task group data 2 that meet the conditions, the tablet can also select one from them. The tablet can randomly select one. Alternatively, the tablet can select one based on the number of uses and / or the last use time of at least two target task group data 2. For details, please refer to the relevant explanation in S2504 above regarding the selection of target task group data 1 from at least two candidate task group data 0, which will not be repeated here.

[0344] The tablet can display the floating windows of various display applications in the target task area of ​​the target layout template 3. The target task area is the task area of ​​the application with the same application category as the display application in the task group of the target task group data 2.

[0345] Continuing with the example of target task group data 2 being the third historical task group data in Table 1, the target layout template is layout template 10011e. APP-1 in the multiple display applications has the same application category as APP-15 in target task group data 2. APP-15 is located in the third position of the task group, and the tablet can display the floating window of APP-15 in the display area corresponding to the third task area of ​​layout template 10011e. Similarly, APP-2 in the multiple display applications has the same application category as APP-7 in target task group data 2. APP-7 is located in the first position of the task group, and the tablet can display the floating window of APP-7 in the display area corresponding to the first task area of ​​layout template 10011e. Finally, APP-3 in the multiple display applications has the same application category as APP-13 in target task group data 2. APP-13 is located in the second position of the task group, and the tablet can display the floating window of APP-13 in the display area corresponding to the second task area of ​​layout template 10011e.

[0346] It should be noted that, using the first method, if a single floating window is currently displayed or no floating window is displayed, the tablet may not respond to the user's triggering of the one-click layout. For example, the tablet could prompt that at least two floating windows must be launched to support one-click layout.

[0347] Second method

[0348] The second method can be used in scenario 3 above.

[0349] The following section, with reference to Figure 26, describes the specific implementation of the second method for determining the recommended task groups in the task group list using the tablet, such as determining the specific implementation of the recommended task groups in the task group lists of interfaces 2001, 2011, 2021, and 2101.

[0350] S2601. In response to the user's selection of a recommended task group tag, the tablet checks whether a floating window is currently displayed. If yes, execute S2602-S2603; otherwise, execute S2604.

[0351] When at least one floating window is currently displayed, the tablet can query historical task group data that includes the displayed application in the task group and determine the recommended task group, as shown in S2602-S2603, so that the recommended task group includes the displayed application.

[0352] If the floating window is not currently displayed, the tablet can determine the recommended task groups according to the number of times it is used, from high to low, as shown in S2604.

[0353] Optionally, in response to the user's trigger operation 1 on the layout button, the tablet can also detect whether a floating window is currently displayed and perform subsequent steps based on the detection result.

[0354] Optionally, if the floating window is not currently displayed, the tablet may not display the recommended task group in response to the user's selection of the recommended task group label or the user's trigger operation 1 on the layout button. Correspondingly, if the tablet detects that the floating window is not currently displayed in response to the user's selection of the recommended task group label or the user's trigger operation 1 on the layout button, it may not execute S2604.

[0355] S2602, The tablet queries the target task group data 3 of the layout template to be recommended. The target task group data 3 includes the layout template to be recommended, and the task group of the target task group data 3 includes the display application.

[0356] The layout template to be recommended can be any of the multiple layout templates. The tablet can iterate through multiple layout templates to obtain the layout template to be recommended in turn.

[0357] For example, the tablet can provide six layout templates, including but not limited to the template list 10011 shown in Figure 10. Taking layout template 10011b as the recommended layout template, and the currently displayed floating window of APP-1 (i.e., the application displayed is APP-1), the tablet can filter the target task group data 3 as shown in Table 7 below from the historical task group data:

[0358] Table 7

[0359] In the historical task group data in Table 7, the value of the template field is 10011b, and the task group includes APP-1, which satisfies the condition of the target task group data 3.

[0360] The tablet can display at most one recommended task group of layout templates to be recommended. It can be understood that a task group and a layout template from one target task group data 3 can generate a recommended task group. Correspondingly, the tablet can obtain one recommended task group using one target task group data 3. If multiple target task group data 3s are obtained, the tablet can select one from them. The tablet can choose one randomly. Alternatively, the tablet can select one based on the number of uses and / or the last use time from at least two target task group data 3s. For details, please refer to the relevant explanation in S2504 above regarding the selection of target task group data 1 from at least two candidate task group data; it will not be repeated here.

[0361] Of course, the tablet can also display multiple recommended task groups of the layout template to be recommended. Correspondingly, if multiple target task group data 3 are obtained, the tablet may not need to select any.

[0362] The recommended layout template can be one where the number of task areas is greater than the number of floating windows. In this way, when the tablet uses the recommended layout template, it can display not only the currently displayed at least one floating window, but also floating windows for other applications. As shown in Figure 20A, the recommended task group 20011b in the task group list 20011 of interface 2001 includes APP-1, indicating that the floating window of the currently displayed APP-1 can be displayed, and also includes APP-2 and APP-3, indicating that the floating windows of APP-2 and APP-3 can be displayed.

[0363] For example, if the number of floating windows is 1, then the number of task areas of the layout template to be recommended is at least 2. The layout template to be recommended can be layout template 10011a (number of task areas is 2), layout template 10011d (number of task areas is 3), layout template 11011b (number of task areas is 3), layout template 10011e (number of task areas is 3), layout template 10011f (number of task areas is 4), and layout template 11011b (number of task areas is 4) in the interface 1901 shown in Figure 19.

[0364] For another example, if the number of floating windows is 2, then the number of task areas of the layout template to be recommended is at least 3. The layout template to be recommended can be layout template 10011d (number of task areas is 3), layout template 11011b (number of task areas is 3), layout template 10011e (number of task areas is 3), layout template 10011f (number of task areas is 4), and layout template 11011b (number of task areas is 4) in the interface 1901 shown in Figure 19.

[0365] For example, if the number of floating windows is 3, then the number of task areas for each layout template is at least 4. The layout templates to be recommended can be layout template 10011f (with 4 task areas) and layout template 11011b (with 4 task areas) in the interface 1901 shown in Figure 19.

[0366] It should be noted that if the number of floating windows is the same as the maximum number of task areas for multiple layout templates (e.g., the number of floating windows is 4 and the maximum number of task areas is also 4), the tablet will have difficulty recommending more other applications through the recommended task group. In this case, the tablet can choose not to execute S2602 and its subsequent steps, and will not display the recommended task group.

[0367] It should be noted that in free screen mode, a tablet can typically launch a maximum number of floating windows within a task area. Consequently, the number of floating windows will not exceed the maximum number of task areas.

[0368] S2603, the tablet displays the recommended task group corresponding to the layout template to be recommended based on the task group in the target task group data 3 and the target layout template 4.

[0369] The tablet can populate the various applications from the task group in the target task group data 3 into the various task areas of the target layout template 4 to obtain recommended task groups. Since the task group in the target task group data 3 includes the display application and other applications besides the display application, the resulting recommended task groups also include the display application and other applications. This allows the tablet to recommend other applications associated with the display application to the user, as well as layout styles for the display application and other applications.

[0370] Taking target task group data 3 as the historical task group data in Table 7 as an example, then target layout template 4 is layout template 10011b in Table 7. In task groups APP-1, APP-2, and APP-3 of target task group data 3: APP-1 is in the first position, so the tablet can fill APP-1 into the first task area of ​​layout template 10011b; APP-2 is in the second position, so the tablet can fill APP-2 into the second task area of ​​layout template 10011b; APP-3 is in the third position, so the tablet can fill APP-3 into the third task area of ​​layout template 10011b. Thus, we can obtain recommended task group 20011b in recommended task group template 20011 in interface 2001 as shown in Figure 20A.

[0371] The above S2602-S2603 only describes the determination of the recommendation task group for one layout template to be recommended. For multiple layout templates to be recommended, such as the 6 layout templates in interface 1901 shown in Figure 19, the tablet can use the same method to determine the recommendation task group for each layout template.

[0372] After determining the recommended task groups for all layout templates, the tablet can display a task group list 20011b in interface 2001 as shown in Figure 20A. The order of the recommended task groups is the same as the order of the layout templates.

[0373] Additionally, the tablet may not be able to find the target task group data 3 for the layout template to be recommended. For example, there may be no historical task group data that includes the layout template to be recommended. Or, the historical task group data that includes the layout template to be recommended may not include the display application. In this case, the tablet may not display the recommended task group for the layout template to be recommended, as shown in Figure 20B, where the task group list 20111 in interface 2011 does not include the recommended task group corresponding to layout template 10011b.

[0374] Furthermore, the tablet may not be able to find all target task group data for the layout templates to be recommended. In this case, the tablet can display an empty task group list, as shown in the task group list 20111 in interface 2021 of Figure 20C, which includes the message "No recommendations available," indicating that there are no recommended task groups. Alternatively, the tablet can choose not to display the task group list, as shown in interface 2221 of Figure 22C, which does not include the task group list.

[0375] Following steps S2602-S2603, the tablet can recommend layout styles for display applications and other applications associated with those applications to the user. Subsequently, the user can select recommended task groups to choose other applications and layout styles, improving human-computer interaction efficiency.

[0376] S2604: The tablet displays multiple recommended task groups in descending order of usage frequency.

[0377] For example, the tablet can display several of the most frequently used task groups, such as six recommended task groups. The tablet can sort multiple historical task group data sets from highest to lowest usage frequency to obtain the top six task group data sets. Based on the task groups and layout templates in each of the six task group data sets, recommended task groups are obtained, thus resulting in six recommended task groups.

[0378] Multiple recommended task groups can be prioritized for sorting by layout template. Furthermore, if at least two recommended layouts correspond to the same layout template, they can be sorted by usage frequency. For example, in the interface 2101 shown in Figure 21A, recommended task groups 21011c and 21011d in the task group list 21011 both correspond to layout template 10011e, and recommended task group 21011c has been used more times than recommended task group 21011d. Therefore, the tablet can display recommended task group 21011c before recommended task group 21011d.

[0379] Alternatively, multiple recommended task groups can all be sorted by the number of times they have been used.

[0380] Using the S2604, the tablet can display combinations of frequently used task groups and layouts (i.e., recommended task groups), allowing users to quickly access previously used task groups and layouts.

[0381] Third method

[0382] The third method can be used in Method 2 of Scenario 2 above. Using the third method, the tablet can determine the recommended applications in each display area.

[0383] The following section, with reference to Figure 27, describes the specific implementation of the third method for determining recommended applications in each display area of ​​the tablet, such as determining recommended applications in display areas 15011, 15012, and 15013 in interface 1501 shown in Figure 15, recommended applications in display areas 15012 and 15013 in interface 1601 shown in Figure 16, and recommended applications in display area 15013 in interface 1711 shown in Figure 17B.

[0384] S2701. In the absence of a floating window, in response to the user's selection of a layout template, the tablet queries the target task group data 4, which includes the currently selected layout template.

[0385] Taking the currently selected layout template 10011b as an example, the tablet can retrieve the target task group data 4 shown in Table 8 below from the historical task group data:

[0386] Table 8

[0387] In Table 8, the value of the template field in each historical task group data is 10011b, therefore it belongs to target task group data 4.

[0388] S2702. The tablet traverses the selected layout template and the corresponding display area. It counts the applications that have been displayed in the current display area and their display counts in the target task group data 4. It then obtains the application ranking 1, which is the application with the highest number of displays in the current display area from the lowest to the highest number.

[0389] In other words, the tablet can iterate through the display of each task area corresponding to the currently selected layout template and obtain the application ranking for each display area. Here, the current display area refers to the currently traversed display area.

[0390] It should be noted that after selecting a layout template, the display area on the tablet corresponds one-to-one with the task area of ​​the currently selected layout template, and the order is also consistent. For example, the first task area corresponds to the first display area, the second task area corresponds to the second display area, and so on.

[0391] The number 2 can be less than the number of recommended positions in the display area (e.g., the number 1), so that in addition to providing recommended applications with high display frequency in the display area, other recommended applications can also be provided.

[0392] There are several possibilities for application sorting 1: if the number of applications displayed in the current display area of ​​the target task group data 4 is less than the number 2, then the number of applications in the sorted application sorting 1 will be less than the number 2; or, if the number of applications displayed in the current display area of ​​the target task group data 4 is greater than or equal to the number 2, then the number of applications in the sorted application sorting 1 will be equal to the number 2.

[0393] Taking quantity 2=4 as an example, based on the target task group data 4 in Table 8 above, the following describes the specific implementation of the application sorting 1 for determining the display area corresponding to each task area in the layout template 10011b.

[0394] The first display area corresponding to the first task area in layout template 10011b is shown in display area 15011 of interface 1501 in Figure 15. The tablet can statistically determine that the first application in the task group in Table 8 includes APP-2, APP-1, and APP-3, meaning a total of 3 applications were displayed in the first display area, fewer than 4. Furthermore, the number of times these applications were displayed in the first display area is 60 (30+10+20), 68 (25+9+8+13+6+7), and 30 (16+5+9). The display frequency is sorted from highest to lowest as APP-1, APP-2, and APP-3. Therefore, the tablet can obtain the application ranking for the first display area as: APP-1, APP-2, and APP-3.

[0395] The second display area corresponding to the second task area in layout template 10011b is shown in display area 15012 of interface 1501 in Figure 15. The tablet can statistically determine that the second-ranked applications in the task group in Table 8 include APP-2, APP-3, APP-7, APP-6, APP-10, APP-9, APP-20, APP-13, and APP-5. That is, a total of 9 applications were displayed in the first display area, more than 4. The number of times these applications were displayed in the second display area is 50 (30+20), 41 (25+16), 10, 18 (9+9), 5, 8, 13, 6, and 7, respectively. The top 4 applications in terms of display frequency are APP-2, APP-3, APP-6, and APP-20. Therefore, the tablet can obtain the application ranking 1 corresponding to the second display area as: APP-2, APP-3, APP-6, and APP-20.

[0396] The third display area corresponding to the third task area in layout template 10011b is shown in display area 15012 of interface 1501 in Figure 15. The tablet can statistically determine that the third displayed application in the task group in Table 8 includes APP-8, APP-2, APP-9, APP-5, APP-3, APP-6, APP-18, and APP-15. That is, a total of 8 applications were displayed in the first display area, more than 4. The number of times these applications were displayed in the third display area is 30, 41 (25+16), 28 (10+5+13), 18 (9+9), 20, 8, 6, and 7, respectively. The top 4 applications in terms of display frequency are APP-2, APP-8, APP-9, and APP-3. Therefore, the tablet can obtain the application ranking for the third display area as: APP-2, APP-8, APP-9, and APP-3.

[0397] S2703. If the current display area is a landscape display area, the tablet filters out applications that only support portrait mode and applications in application sort 1 from the application launch count sorting of the installed applications, and obtains application sort 2.

[0398] Tablets can track and sort the number of times installed apps are launched. For example, the YOYO Assistant app on a tablet can track the number of times various apps are launched over a period of time and sort them from highest to lowest launch count. When determining recommended apps for different task areas, the tablet can use the launched count data from multiple apps and sort them accordingly.

[0399] The landscape display area can show apps that only support landscape mode and apps that support both landscape and portrait modes, but it cannot display apps that only support portrait mode. Based on this, the tablet can filter out apps that only support portrait mode from the startup count. It can be understood that an app's support for landscape and portrait modes corresponds to the support for those modes in its floating windows. If an app only supports landscape mode, then its floating window will also only support landscape mode. Therefore, the floating windows of the filtered apps can be displayed in the landscape display area.

[0400] Furthermore, the apps in the top app ranking are also apps installed on the tablet. Filtering out apps in the top app ranking can prevent the same app from being recommended repeatedly in the same display area.

[0401] For example, the apps installed on the tablet, sorted by launch count from highest to lowest, are: APP-3, APP-6, APP-2, APP-10, APP-8, APP-7, APP-20, APP-1, APP-13, APP-5, APP-22... and APP-10 only supports portrait mode. Continuing with the example in Table 8 above:

[0402] In layout template 10011b, the second task area is a horizontal task area, so the corresponding second display area is also a horizontal display area. Furthermore, the application sorting 1 for the second display area is APP-2, APP-3, APP-6, and APP-20. The tablet can filter out APP-2, APP-3, APP-6, and APP-20 (which are included in application sorting 1) from the above launch count sorting, as well as filter out the application APP-10, which only supports portrait mode. The resulting application sorting 2 is: APP-8, APP-7, APP-1, APP-13, APP-5, APP-22…

[0403] In layout template 10011b, the third task area is a horizontal task area, so the corresponding third display area is also a horizontal display area. Furthermore, the application sorting 1 for the third display area is APP-2, APP-8, APP-9, APP-3. The tablet can filter out APP-2, APP-8, APP-9, and APP-3 (which are included in application sorting 1) from the above launch count sorting, as well as filter out the application APP-10, which only supports portrait mode. The resulting application sorting 2 is: APP-6, APP-7, APP-20, APP-1, APP-13, APP-5, APP-22…

[0404] S2704. The tablet combines application sorting 1 and application sorting 2 to obtain recommended application sorting m1. The top 1 recommended applications in recommended application sorting m1 are displayed in the current horizontal display area.

[0405] Among them, quantity 1 is greater than quantity 2, and quantity 1 can be 8, 9, 10... Those skilled in the art can flexibly set it according to actual needs.

[0406] Continuing with the examples in S2702 and S2703 above, and taking quantity 1 = 9 as an example:

[0407] In layout template 10011b, the application sort 1 in the second display area corresponding to the second task area is APP-2, APP-3, APP-6, APP-20, and the application sort 2 is APP-8, APP-7, APP-1, APP-13, APP-5, APP-22... The combined recommended application sort m1 is APP-2, APP-3, APP-6, APP-20, APP-8, APP-7, APP-1, APP-13, APP-5, APP-22... The tablet can display the first 9 applications in the recommended application sort m1 (APP-2, APP-3, APP-6, APP-20, APP-8, APP-7, APP-1, APP-13, APP-5) in the second display area corresponding to the second task area in layout template 10011b, as shown in the 9 recommended applications in display area 15012 of interface 1501 in Figure 15.

[0408] In layout template 10011b, the application sorting 1 in the third display area corresponding to the third task area is APP-2, APP-8, APP-9, APP-3, and the application sorting 2 is APP-6, APP-10, APP-7, APP-20, APP-1, APP-13, APP-5, APP-22... The combined recommended application sorting m1 is APP-2, APP-8, APP-9, APP-3, APP-6, APP-7, APP-20, APP-1, APP-13, APP-5, APP-22... The tablet can display the first 9 applications in the recommended application sorting m1 (APP-2, APP-8, APP-9, APP-3, APP-6, APP-7, APP-20, APP-1, APP-13) in the third display area corresponding to the third task area in layout template 10011b, as shown in the 9 recommended applications in display area 15013 of interface 1501 in Figure 15.

[0409] In this way, the tablet can recommend not only frequently displayed applications in a landscape display area, but also applications that users often use on the tablet that support both landscape and portrait modes, thus increasing the diversity of recommended applications.

[0410] Furthermore, the tablet will display frequently used apps in the landscape view area first, thus prioritizing recommendations for these apps, which better aligns with users' historical layout habits and improves the accuracy of recommendations.

[0411] S2705. If the current display area is a portrait display area, the tablet filters out applications that only support landscape mode and applications in application sort 1 from the number of times the installed applications have been launched, and obtains application sort 3.

[0412] The portrait display area can show apps that only support portrait mode and apps that support both portrait and landscape modes, but it cannot display apps that only support landscape mode. Based on this, the tablet can filter out apps that only support landscape mode from the startup count. In this way, the floating windows of the filtered apps can be displayed in the portrait display area.

[0413] Furthermore, the apps in the top app ranking are also apps installed on the tablet. Filtering out apps in the top app ranking can prevent the same app from being recommended repeatedly in the same display area.

[0414] For example, the apps installed on the tablet, sorted by launch count from highest to lowest, are: APP-3, APP-6, APP-2, APP-10, APP-8, APP-7, APP-20, APP-1, APP-13, APP-5, APP-22... and APP-13 only supports landscape mode. Continuing with the example in Table 8 above:

[0415] If the first task area of ​​layout template 10011b is a vertical task area, then the corresponding first display area is a vertical display area. Furthermore, the application sorting 1 corresponding to the second display area is APP-1, APP-2, and APP-3. The tablet can filter out APP-1, APP-2, and APP-3 (which are included in application sorting 1) from the above launch count sorting, as well as filter out the application APP-13 (which only supports landscape mode). The resulting application sorting 3 is: APP-6, APP-10, APP-8, APP-7, APP-20, APP-5, APP-22…

[0416] S2706, tablet combination application sorting 1 and application sorting 3, to obtain recommended application sorting m2, and display the top 1 recommended applications in recommended application sorting m2 in the current display area.

[0417] Continuing with the examples in S2702 and S2704 above, and taking quantity 1 = 9 as an example:

[0418] In layout template 10011b, the application sorting 1 in the first display area corresponding to the first task area is APP-1, APP-2, APP-3, and the application sorting 3 is APP-6, APP-10, APP-8, APP-7, APP-20, APP-5, APP-22... The combined recommended application sorting m2 is APP-1, APP-2, APP-3, APP-6, APP-10, APP-8, APP-7, APP-20, APP-5, APP-22... The tablet can display the first 9 applications in the recommended application sorting m2 (APP-1, APP-2, APP-3, APP-6, APP-10, APP-8, APP-7, APP-20, APP-5) in the first display area corresponding to the first task area of ​​layout template 10011b, as shown in Figure 15, which is the 9 recommended applications in display area 15011 of interface 1501.

[0419] In this way, the tablet can recommend applications that are frequently displayed in a vertical display area, as well as applications that users frequently use on the tablet that only support portrait mode and applications that support both portrait and landscape modes, thus increasing the diversity of recommended applications.

[0420] Furthermore, the tablet will display frequently used apps in the vertical display area first, thus prioritizing recommendations for these apps, which better aligns with users' historical layout habits and improves the accuracy of recommendations.

[0421] It should be noted that if no target task group data 4 that meets the conditions is found in S2701, then application ranking 1 cannot be obtained in S2702. Consequently, the final recommended application rankings m1 and m2 will not include the applications in application ranking 1, and the recommended applications displayed in the display area will also not include the applications in application ranking 1.

[0422] For example, for the landscape display area, the tablet sorts the installed apps by their launch frequency, filters out apps that only support portrait mode, and then obtains a recommended app ranking and makes recommendations. Therefore, the recommended apps displayed in multiple landscape display areas can be the same.

[0423] For example, in the portrait display area, the tablet can filter out apps that only support landscape mode by sorting the number of times the installed apps have been launched, thus obtaining a recommended app ranking and making recommendations. Therefore, the recommended apps displayed in multiple portrait display areas can be the same.

[0424] S2707. After launching application B1 in display area A2 among multiple display areas, the tablet statistical target task group data 4, when application B1 is launched in display area A2, the number of times each application is displayed in the remaining display areas A1, and the application ranking 4 is obtained by ranking the number of times each application is displayed in each display area A1 from high to low.

[0425] Application B1 can be launched using any of the methods described above, from method one to method three.

[0426] Among them, display area A1 refers to the display area of ​​multiple display areas other than display area A2 where no application has been launched.

[0427] There can be multiple display areas A1. For example, display area A1 can be display area 1502 and display area 1503 in interface 1601 shown in Figure 16, display area A2 can be display area 1501 in interface 1601, and application B1 can be APP-1 launched in display area 1501 in interface 1601.

[0428] Display area A2 can also be multiple. For example, display area A1 can be display area 15013 in interface 1711 shown in Figure 17B, display area A2 can be display area 15011 and display area 15012 in interface 1711, and application B1 can be APP-1 and APP-33 launched in display area 15011 in interface 17011.

[0429] Continuing with the example from Table 8 above, and taking display area A2 as display area 15011 and application B1 as APP-1, the tablet can retrieve the 2nd, 4th, and 9th-12th records from the target task group data 4 shown in Table 8. The application ranked first in the task group is APP-1, indicating that the floating window of APP-1 is displayed in display area 15011. By analyzing these 8 records in Table 8, the tablet can obtain the application rankings 4 for display areas 1502 and 1503 respectively.

[0430] The second application in the task group, displayed in display area 15012 (the second display area), includes APP-3, APP-6, APP-9, APP-20, APP-13, and APP-5. These applications were displayed 25, 9, 8, 13, 6, and 7 times respectively in the second position. The top four applications, ranked from highest to lowest display frequency, are APP-3, APP-20, APP-6, and APP-9. The tablet can thus obtain the application ranking for display area 15012 as APP-3, APP-20, APP-6, and APP-9, as shown in interface 1601 in display area 15012, which lists the top four recommended applications.

[0431] The third application in the task group, displayed in display area 15013 (the third display area), includes APP-2, APP-5, APP-6, APP-9, APP-18, and APP-15. These applications were displayed 25, 9, 8, 13, 6, and 7 times respectively in the second position. The top four applications, ranked from highest to lowest display frequency, are APP-2, APP-9, APP-5, and APP-6. The tablet can thus obtain the application ranking for display area 15013 as APP-2, APP-9, APP-5, and APP-6, as shown in interface 1601, which displays the top four recommended applications in display area 15013.

[0432] For any display area A1, the tablet can be recommended to use the following S2708-S2709 or S2710-S2711.

[0433] S2708. If the display area A1 is a landscape display area, the tablet filters out applications that only support portrait mode and applications in application sort 4 from the application launch count sort of the installed applications, and obtains application sort 5.

[0434] S2709, tablet combination application sorting 4 and application sorting 5, to obtain recommended application sorting m3, and display the top 1 recommended applications in recommended application sorting m3 in display area A1.

[0435] For S2708-S2709, please refer to the explanation of S2703-S2704 above, which will not be repeated here.

[0436] S2710. If the display area A1 is a vertical display area, the tablet filters out applications that only support landscape mode and applications in application sort 4 from the number of times the installed applications are launched, and obtains application sort 6.

[0437] S2711, tablet combination application sorting 4 and application sorting 6, to obtain recommended application sorting m4, and display the top 1 recommended applications in recommended application sorting m4 in display area A1.

[0438] For S2710-S2711, please refer to the explanation of S2705-S2706 above, which will not be repeated here.

[0439] Fourth method

[0440] The fourth method can be used in method three of scenario 2 above.

[0441] Using the fourth method, the tablet can determine recommended applications in application panel D1. For example, using the fourth method, the tablet can determine recommended applications in the "Application Suggestions" section of application panel 17011 in interface 1701.

[0442] In response to the user's triggering operation of the view button C1 for all applications in any display area, the tablet can obtain the recommended application sorting of that display area, such as the recommended application sorting m1, recommended application sorting m2, etc., and fill the recommended applications into the recommended positions in the application panel D1 (such as "Application Suggestions") according to the recommended application sorting from front to back.

[0443] In this design, the number of recommended apps in the application recommendation area of ​​application panel D1 is typically greater than the number of recommended apps in the display area. For example, the display area has one recommended app, as shown in the nine recommended apps in each display area of ​​interface 1501 in Figure 15, while the application recommendation area in application panel D1 has three recommended apps, as shown in the twelve recommended apps in the "Application Suggestions" section of application panel 17011 in interface 1701 in Figure 17A. This allows the tablet to provide more recommended applications in application panel D1.

[0444] In summary, by using the fourth method, the tablet can provide a greater number of recommended applications in the application panel D1, in the same order as those in the display area.

[0445] Meanwhile, the application panel D2 includes recommended applications sorted by the number of times the installed applications have been launched. It does not distinguish between applications' support for landscape and portrait modes, nor is it sorted by historical task group data. Therefore, it is different from the recommended applications in the application panel D1.

[0446] Fifth Method

[0447] The fifth method can be used in scenarios one through three of scenario 2 above. Using the fifth method, the tablet can determine the floating windows displayed in the display area corresponding to each task area in the selected layout template.

[0448] For example, using the fifth method, in response to the user's selection operation of the layout template 10011b in the interface 1001 shown in Figure 10, the tablet can determine to display the floating windows 4011, 5011, and 5012 one by one in the vertical display area on the left, the horizontal display area on the upper right, and the horizontal display area on the lower right in the interface 1101 shown in Figure 11.

[0449] For example, using the fifth method, in response to the user's selection operation of the layout template 10011a in the interface 1001 shown in Figure 10, the tablet can determine to display the floating window 4011 alone in the vertical display area on the left side of the interface 1201 shown in Figure 12A, and to display the floating windows 5011 and 5012 together in the vertical display area on the right side of the interface 1201 shown in Figure 12A.

[0450] For example, using the fifth method, in response to the user's selection operation of the layout template 10011c in the interface 1001 shown in Figure 10, the tablet can determine to display the floating windows 4011, 5011 and 5012 one by one in the upper left horizontal display area, the lower left horizontal display area and the right horizontal display area in the interface 1301 shown in Figure 13.

[0451] The algorithm flow of the fifth method is described below with reference to Figure 28:

[0452] S2801. When at least two floating windows are displayed, in response to the user's selection operation on any layout template, the tablet sorts at least one floating window, wherein the sorting reference factors include at least one of the following: the floating window's support for landscape and portrait screens, the operation order of the floating windows, the position of the floating windows on the display screen, the opening order of the floating windows, and the floating window itself.

[0453] For example, any layout template can be layout template X in case one, layout template Y in case two, or layout template Z in case three.

[0454] Furthermore, the tablet can use the following process to sort at least two floating windows:

[0455] S2801a. The tablet sorts at least one floating window in the following order: supports only landscape mode, supports only portrait mode, and supports both landscape and portrait modes.

[0456] The tablet can be configured with at least one floating window, including floating window a, floating window b, and floating window c, where floating window a only supports landscape mode, floating window b only supports portrait mode, and floating window c supports both landscape and portrait modes.

[0457] In this way, when determining the display area of ​​the floating window, the tablet can prioritize the display area of ​​floating windows that only support landscape mode and those that only support portrait mode, thus prioritizing the directional requirements of the display area for floating windows that only support landscape mode and those that only support portrait mode.

[0458] In practice, different floating windows may have the same level of support for both portrait and landscape modes, making it difficult to sort them using S2801a. Referring to Figure 29, floating windows 29011 and 29012 in interface 2901 only support landscape mode. Using S2801a, the tablet cannot determine the correct order for floating windows 29011 and 29012. In this case, S2801b can be used to sort floating windows with the same support for both portrait and landscape modes.

[0459] S2801b: The tablet sorts floating windows according to their Z-Order, based on whether they support both portrait and landscape orientations.

[0460] Normally, each time a floating window is interacted with—such as clicking, dragging, or opening—the tablet places that floating window on the top layer. In this mechanism, floating windows that are interacted with later are placed on a higher layer, and those that are interacted with earlier are placed on a lower layer. The layer can also be understood as a value in the direction perpendicular to the display screen and along the front of the screen (also called Z-Order). The higher the layer, the larger the Z-Order; the lower the layer, the larger the Z-Order. Based on this, the tablet can sort floating windows according to their Z-Order from largest to smallest, and floating windows with the same support for both portrait and landscape modes, thus placing floating windows that are interacted with later in the order of operation at the front, and those that are interacted with earlier in the order of operation at the back.

[0461] Taking the example that both floating windows a and b only support landscape mode, the tablet can obtain the Z-order of floating window a and floating window b. The Z-order of floating window a is greater than that of floating window b, indicating that the operation order of floating window a is later. The tablet can place floating window a before floating window b.

[0462] In this way, when determining the display area of ​​the floating window, the tablet can prioritize the display area of ​​the floating window that is operated later in the order.

[0463] In practice, floating windows with the same support for both portrait and landscape screens may have the same Z-Order, making it difficult to sort them using S2801b. Referring to Figure 29, floating windows 29011 and 29012 in interface 2901 do not overlap and have the same Z-Order, making it difficult to sort them using S2801b. In this case, S2801c can be used to sort floating windows with the same Z-Order.

[0464] S2801c: The tablet sorts floating windows with the same Z-Order according to the X-axis value of the floating window in the two-dimensional plane of the display screen.

[0465] Tablets typically define the floating windows in the display area from left to right.

[0466] Referring to Figures 10 and 11, taking the user's selection of layout template 10011b in interface 1001 shown in Figure 10 as an example, in response to the user's selection of layout template 10011b in interface 1001, the tablet first determines the floating window displayed in the vertical display area on the left side of interface 1101 shown in Figure 11, and then determines the floating windows displayed in the two horizontal display areas on the right side of interface 1101 shown in Figure 11.

[0467] Based on the aforementioned mechanism of determining floating windows from left to right, the tablet can sort floating windows with the same Z-Order according to their position on the display screen from left to right (represented by X-axis values, as shown by the arrows in Figure 29), ensuring that floating windows closer to the left are sorted first, and those closer to the right are sorted last. This way, when determining the task area for floating windows later, the tablet can prioritize displaying floating windows closer to the left on the left side of the display area, and then display floating windows closer to the right on the right side, thus reducing the displacement required when moving floating windows to their respective display areas.

[0468] Taking the same Z-Order of floating window a and floating window b as an example, the tablet can obtain the X-axis value of floating window a and floating window b. Based on the X-axis value, it can be found that floating window a (floating window 4011 in interface 1001 as shown in Figure 10) is located to the left of floating window b (floating window 5011 in interface 1001 as shown in Figure 10), indicating that floating window a is closer to the left side of the display screen. The tablet can place floating window a in front of floating window b.

[0469] In practice, floating windows with the same Z-Order may have the same X-axis value, making it difficult to sort them using S2801c. Referring to Figure 29, the center of floating windows 29011 and 29012 in interface 2901 are both x1 away from the left edge of the display screen, meaning their X-axis values ​​are the same. Therefore, it's difficult to sort floating windows 29011 and 29012 using S2801c. In this case, S2801d can be used to sort floating windows with the same X-axis value.

[0470] S2801d and the tablet sort floating windows by task number from smallest to largest, and floating windows with the same X-axis value.

[0471] When launching a floating window, the tablet can create a task ID. The task ID is smaller for earlier launched floating windows and larger for later launched ones. The tablet can sort floating windows with the same X-axis value according to their task IDs from smallest to largest, thus ensuring that earlier launched floating windows are listed first, and later launched ones are listed last. This allows the tablet to prioritize the display area of ​​the earlier launched floating windows when determining their display area.

[0472] Referring to Figure 29, the task number of floating window 29011 in interface 2901 is 1, and the task number of floating window 29012 is 2. The tablet can place floating window 29011 before floating window 29012.

[0473] After the above steps S2801a-2801d, the tablet can determine the unique order of at least two floating windows.

[0474] It should be noted that the sorting methods for at least two floating windows shown in S2801a-S2801d above are merely exemplary. Optionally, the tablet can also reduce the sorting steps. For example, the tablet can sort simply by task number. Another example is that the tablet can sort by the floating windows' support for landscape and portrait modes and their task numbers. Alternatively, the tablet can change the order of the above sorting steps. For example, the tablet can first sort by X-axis value, and then sort floating windows with the same X-axis value by Z-Order. This application does not specifically limit this approach.

[0475] S2802. The tablet obtains the floating windows to be laid out in order of floating window sorting. Based on the support of the floating windows to be laid out for landscape and portrait screens and the sorting of multiple display areas, the display area of ​​the floating windows to be laid out is determined.

[0476] For example, if the floating windows are ordered as floating window a, floating window b, and floating window c, then the floating windows to be laid out can be floating window a, floating window b, and floating window c in sequence, and the tablet can determine the display areas of floating window a, floating window b, and floating window c in sequence.

[0477] The multiple display areas are arranged in a certain order, with the display areas closer to the left side of the screen appearing earlier and the display areas closer to the left side of the screen appearing later.

[0478] Depending on the different screen orientations for floating windows, the following methods can be used to determine the display area of ​​the floating window to be laid out on the tablet:

[0479] The floating window to be laid out only supports landscape mode: The tablet searches for unoccupied landscape display areas sequentially according to the display area order. If an unoccupied landscape display area is found, the tablet determines that unoccupied landscape display area as the display area for the floating window to be laid out. If no unoccupied landscape display area is found, the tablet determines the first unoccupied display area as the display area for the floating window to be laid out, according to the display area order. In this way, the tablet can display floating windows that only support landscape mode in landscape display areas as much as possible. It can be understood that once the tablet determines the display area of ​​a floating window, that display area is occupied, and the same applies below.

[0480] The floating window to be laid out only supports portrait mode: The tablet searches for unoccupied vertical display areas sequentially according to the display area order. If an unoccupied vertical display area is found, the tablet determines that unoccupied vertical display area as the display area for the floating window to be laid out. If no unoccupied vertical display area is found, the tablet determines the first unoccupied display area as the display area for the floating window to be laid out. In this way, the tablet can display the floating window that only supports portrait mode within the vertical display area as much as possible.

[0481] The floating window to be laid out supports both portrait and landscape orientations: The tablet can determine the first unoccupied display area as the display area for the floating window to be laid out, according to the order of the display areas.

[0482] Furthermore, regarding scenarios one through three in scenario 2 mentioned above, the following differences exist in S2802:

[0483] For scenario one, the number of task areas and the number of floating windows in layout template X are both n1.

[0484] The tablet can display each of the n1 floating windows to be laid out in the n1 display areas one by one, following the steps in S2802 above.

[0485] In scenario two, the number of task areas n3 in layout template Y is less than the number of floating windows n2.

[0486] The tablet can, following the steps in S2802 above, display the first n3-1 floating windows to be laid out in the floating window sorting within the n3-1 display areas. Subsequently, the tablet can determine the display areas of the remaining n2-(n3-1) floating windows to be laid out in the floating window sorting as the remaining display areas within the n3 display areas, and display the remaining n2-(n3-1) floating windows in the last remaining display area.

[0487] In scenario three, the number of task areas (n5) in layout template Z is greater than the number of floating windows (n4).

[0488] The tablet can display the n4 floating windows to be laid out in the n4 display areas one by one, following the steps in S2802 above.

[0489] It should be noted that in scenario three, there is also a case where there is only one floating window. In this case, the tablet can omit the aforementioned steps of sorting the floating windows and determine the display area of ​​the floating window to be laid out based on its support for landscape and portrait modes and the order of the task areas in layout template Z. Specifically, for the tablet's determination of the display area when the floating window only supports landscape, only supports portrait, or supports both landscape and portrait modes, please refer to the explanation of determining the display area of ​​the floating window to be laid out in S2802 above; it will not be repeated here.

[0490] The implementation of various functions in the aforementioned free-screen mode typically requires software support. The tablet's software system can adopt a layered architecture, event-driven architecture, microkernel architecture, microservice architecture, or cloud architecture. This application's embodiments use a layered Android architecture... Taking the operating system as an example, the software architecture of the tablet involved in the embodiments of this application will be introduced with reference to Figure 30.

[0491] Figure 30 shows a schematic diagram of the software architecture of a tablet provided in an embodiment of this application.

[0492] A layered architecture divides software into several layers, each with a clear role and function. Layers communicate with each other through software interfaces. In one implementation, 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.

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

[0494] As shown in Figure 30, the application package may include applications such as a launcher, system UI, smart assistant (such as YOYO), messaging, calling, memo, file, video, browser, and gallery. The applications in this application can also be replaced with other software such as mini-programs or atomic services.

[0495] Desktop applications include applications that run on the system desktop, and the tablet can interact with the user through the GUI provided by the system user interface. In some embodiments, in free screen mode, desktop applications can display the aforementioned application panel D1.

[0496] System UI refers to the user interface of the operating system. System UI runs as applications, providing the basic GUI 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 drop-down menu, the notification bar, the lock screen, the desktop interface, the volume control dialog box, the screenshot display interface, the power button, and the recent tasks interface (also known as the background running window).

[0497] In some embodiments, in free screen mode, the system UI can display template lists, task group lists, layouts after selecting a layout template, and displays after one-click layout.

[0498] The smart assistant app can track the usage frequency of apps installed on the tablet and sort the installed apps by usage frequency.

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

[0500] As shown in Figure 30, the application framework layer may include multiple system services, such as Activity Task Manager, WindowOrganizerController, Activity Manager Service (AMS), Window Manager Service (WMS), content providers, view system, resource manager, notification manager, etc.

[0501] Activity and task management, as a partial refactoring of the activity management service, is responsible for managing application activities and tasks. In some embodiments, activity and task management can be used to query application configurations, including querying the application's support for portrait and landscape modes and its support for free-screen mode. Users can configure applications that support displaying as floating windows in free-screen mode on the tablet, obtaining a free-screen whitelist. If an application is on the free-screen whitelist, it indicates that the application supports free-screen mode. In free-screen mode, in response to user actions on the application, the tablet displays the application as a floating window.

[0502] The Window Organization Controller, as part of the window management service nested stack enhancements, allows applications to manage and control the layout and display of windows in a more granular and isolated manner. In some embodiments, the Window Organization Controller can be used to launch and layout multiple applications included in a recommended task group after detecting a user's selection of that group.

[0503] The Window Management Service is used to manage window applications. It can obtain the screen size, determine whether to display in full-screen mode, whether to use split-screen mode, and whether there are floating windows, status bars, screen lock, or screen captures. The Window Management Service is a service, also known as the Window Manager Service (WMS).

[0504] A window can be understood as an area on a display screen that shows the user interface (UI) and allows user interaction. In some embodiments, a window can also hide the user interface (i.e., the software's operating interface), quickly revealing application navigation and functions when the user needs to interact, or reopening the application's operating interface based on triggered commands. From a system perspective, a window is essentially a canvas. A display screen can include multiple windows, and the layout, order, and animations of these windows are managed by the Window Management Service (WMS). Windows are layered; higher-level windows are displayed on top of lower-level windows, obscuring them. For example, floating windows are always displayed on the top layer.

[0505] Content providers store and retrieve data, making that data accessible to the window management service. This data can include files, folders, text, videos, images, audio, made and received phone calls, browsing history and bookmarks, phone books, etc.

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

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

[0508] 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 tablet, and flashing indicator lights.

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

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

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

[0512] 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), rendering modules, etc.

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

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

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

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

[0517] The rendering module can be used to draw and render images on the draggable window of the first object. For example, when the first object is text or a file, it can draw and render shadows and backgrounds on the draggable window of the text or file. When the first object is an image, it can draw and render shadows on the draggable window of the image.

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

[0519] The following section, referring to Figure 31, further introduces the capabilities provided by desktop applications, system user interface, smart assistant, activity task management, and window organization controller in free screen mode:

[0520] Desktop Applications: In the task area, provide the ability to display all applications (allAPP) in the application panel D1. For example, in response to a user's request to view all applications, such as the "+" trigger mentioned earlier, the desktop application can receive an inter-process communication request from the system user interface to request the display of all applications. After receiving the request, the desktop within the desktop application can retrieve all applications from the taskbar and display them.

[0521] The system user interface further includes desktop mode, template module, desktop pattern module, FreeFromController, intelligenceSuggestion module, database module, and ShellTaskOrganzier module.

[0522] Desktop mode can be used for cross-process communication between the system user interface and desktop applications, such as transmitting information like display requests for all applications and the status of closing all applications.

[0523] The template module can be used to display recommended applications in the task area. Furthermore, the template module can retrieve and display recommended applications from the recommendation engine module.

[0524] The desktop style module can be used to display a list of templates and a list of task groups. Furthermore, the desktop style module can retrieve recommended task groups from the recommendation engine module and display them in the task group list.

[0525] Among them, the floating window controller can be used for window avoidance when multiple floating windows are displayed.

[0526] For example, in a one-click layout scenario, the floating window controller can perform window avoidance based on layout parameters, such as layout template, task area of ​​multiple floating windows, and current position of multiple floating windows, and finally display the layout effect.

[0527] For example, in the scenario of recommended task groups, the floating window controller can perform window avoidance based on the layout parameters of the recommended task group, such as the layout template in the recommended task group, the task area of ​​multiple floating windows, and the current position of at least one floating window, and finally display the layout effect of the recommended task group.

[0528] Furthermore, the floating window controller can obtain the layout parameters of the recommended task group and / or the layout parameters of the layout template from the recommendation engine module to implement window avoidance.

[0529] The recommendation engine module can be used to determine recommended applications in the task area, recommended task groups in the task group list, and the layout style of the one-click layout. Furthermore, the recommendation engine management module can obtain data support from modules such as the database module, task organization module, system services, and smart assistant to determine the aforementioned recommended applications, recommended task groups, and the layout style of the one-click layout.

[0530] The database module can be used to manage users' historical task group data, such as retrieving historical task group data from the recommendation database (suggestion.db) and providing it to the recommendation engine module. The recommendation database can be located under the path / data / data / systemui / database.

[0531] The task organization module can be used for window information management, such as saving the taskID of the currently displayed floating window and providing it to the recommendation engine module.

[0532] Activity task management can be used to query information such as application whitelists for portrait and landscape orientations, and application whitelists, and the query results are provided to the recommendation engine module. Furthermore, activity task management can query the free-screen whitelist and the portrait / landscape whitelist from the multi-window task configuration file (hn_multi_window_config.xml).

[0533] The window organization controller can be used to launch and display applications in the user-selected recommended task group.

[0534] The smart assistant can include a brain-client, which sorts the apps installed on the tablet by usage frequency and provides the sorting results to the recommendation engine module.

[0535] This application embodiment, in conjunction with the software structure of the aforementioned tablet, describes the specific implementation of several main functions in the free screen mode.

[0536] Feature 1: Recommended Applications.

[0537] Referring to Figure 32, the process of displaying recommended applications in the display area includes:

[0538] S3201, The template module receives a request to display recommended applications (.android.wm.shell.desktopmode.template.view.HnTemplatePartContainer#showAppTips).

[0539] In the absence of a floating window, users can trigger a request to display recommended applications when selecting or switching layout templates.

[0540] Alternatively, launching an application in one display area can trigger an update to display recommended applications in other display areas.

[0541] Alternatively, in scenario three above, the user's selection of layout template Z will also trigger a request to display recommended applications.

[0542] S3202, Template module obtains visible tasks (getVsibleTasks).

[0543] In this context, a visible task can be understood as a currently displayed floating window, such as the floating window of application B1 launched in display driver A2, or the floating window of an application that has been launched in at least one display area.

[0544] S3203, The template module requests the recommendation engine module to obtain the recommended application 1 (getSuggestionApp).

[0545] Among them, Recommended Application 1 refers to the recommended application determined based on the user's historical task group data.

[0546] The request to retrieve recommended application 1 may include the application to which the currently displayed floating window belongs, its display area, the identifier of the layout template, and the identifier of the current display area. It should be noted that the recommended application must be determined for each display area where no floating window is displayed. Accordingly, the template module should request recommended application 1 from the recommendation engine module for each display area where no floating window is displayed. The identifier of the current display area is the display area for which the request to retrieve recommended application 1 is directed.

[0547] S3204. The recommendation engine module retrieves a data list (tmpTemplateUseDataList) with the same template name.

[0548] In this way, the data list includes historical task group data using the layout template currently selected by the user.

[0549] S3205, The recommendation engine module sorts applications by the number of times they are displayed (sort(tmpTemplateUseDataList)).

[0550] This allows you to sort applications according to the number of times they are displayed in the current display area.

[0551] S3206, The recommendation engine module retrieves the top 4 apps in the ranking (suggestionApps.add). That is, the previous quantity of 2 is 4.

[0552] S3207. The recommendation engine module returns a list of recommended applications (userdataSuggest) based on user data to the template module.

[0553] This allows us to return the application obtained from S3206.

[0554] It should be noted that if there is no historical task group data for the currently selected layout template, there may be no recommended applications in the recommended application list 1.

[0555] S3208, The template module requests the recommendation engine module to obtain the recommended application 2 (requestSuggestionApps).

[0556] Among them, recommended application 2 refers to the application determined based on the floating window's support for landscape and portrait modes and the orientation of the current display area.

[0557] S3209, The recommendation engine module iterates through the recommendation list (e.g., using a for loop).

[0558] The recommended list refers to a list of recommendations sorted by the number of times an application has been used.

[0559] S3210, The recommendation engine module obtains the applications that can be displayed in the current display area (suggestionApps.add).

[0560] If the current display area is a landscape display area, and the application being iterated over is either an application that only supports landscape mode or an application that supports both landscape and portrait modes, then the current display area supports displaying that application.

[0561] If the current display area is a portrait display area, and the application being iterated through is either an application that only supports portrait mode or an application that supports both portrait and landscape modes, then the current display area supports displaying that application.

[0562] S3211, The recommendation engine module returns a list of recommended applications that can be displayed to the template module (intelegentSuggest).

[0563] In this way, the application obtained in S3210 can be returned.

[0564] S3212, The template module merges recommended application list 1 and recommended application list 2 and filters them.

[0565] The template module can filter out apps from recommended app list 1 from recommended app list 2, thus avoiding duplicate recommendations of the same app.

[0566] S3213, The template module displays the first 9 items of the merged list in the current display area. That is, the previous quantity 1 is 9.

[0567] The merged list can be understood as the recommended application list in the fourth method mentioned above.

[0568] For example, the template module can retrieve the first 9 application icons and display them in the current display area. This allows the display area to show both frequently displayed applications and applications that the user often uses.

[0569] Referring to Figure 33, the process of launching an application in the display area, such as launching a recommended application, includes:

[0570] S3301, The template module receives the request to start the application.

[0571] For example, any of the startup methods described in Method 1 to Method 3 above can trigger a request to start the application.

[0572] S3302, Template module marks the area to be displayed (steCurrentDrop).

[0573] The area to be displayed is one of several display areas. For example, the area to be displayed is the area where the user clicks on a recommended application.

[0574] For example, the template module can mark the area to be displayed by setting a flag, such as setting it to true.

[0575] S3303, Template module triggers application startup (startAppforRegion).

[0576] After marking the area to be displayed, the template module can begin the application startup process.

[0577] S3304. The template module requests the task list (getTaskList) from the floating window controller.

[0578] The task list records currently running applications (including those running in the foreground and background).

[0579] S3305, the floating window controller returns a list of tasks to the template module.

[0580] S3306. The task list includes applications to be launched, and the template module is launched using a warm start method through the floating window controller.

[0581] This allows for faster startup of applications that are pending launch. The application to be launched is the one requesting to be launched.

[0582] S3307. Applications not to be started are not included in the task list. Template modules are started using a cold start method.

[0583] S3308. After startup is complete, the template module triggers the display of the startup application (onTaskAppeared).

[0584] Once the startup is complete, the template module can begin the process of displaying the application's floating window.

[0585] S3309. The template module iterates through each display area to find the area to be displayed.

[0586] The template module can compare whether the currently traversed display area has a flag indicating a region to be displayed, such as `true`. If a flag indicates a region to be displayed, then the currently traversed display area is the region to be displayed. If no flag indicates a region to be displayed, then traversing to the next display area is possible.

[0587] S3310, The template module adds a new task (addNewTask) to the area to be displayed and sets the boundaries (setBounds).

[0588] The boundary is used to limit the display area of ​​the floating window.

[0589] S3311, The template module displays a floating window (showAppTips) for launching the application within the boundary. This allows the application to be launched and the floating window to be displayed within the area to be shown.

[0590] Referring to Figure 34, the process of displaying recommended applications in the application panel D1 includes:

[0591] S3401, The template module receives requests to view all applications.

[0592] For example, after a user performs a trigger operation on the entry point for viewing all applications in the display area, such as "+", the template module can receive a request to view all applications.

[0593] S3402, The template module retrieves the merged list.

[0594] The merged list can be obtained by merging and filtering as described in S3212 above.

[0595] After obtaining the merged list corresponding to each display area, the template module can temporarily store the merged list. Upon receiving a request to view all applications, it can query the stored list to obtain the corresponding merged list.

[0596] S3403, The template module sends the merged list to the desktop application.

[0597] S3404: Desktop Applications - Retrieve the top 12 applications from the merged list. That is, the number 3 mentioned earlier is 12.

[0598] For example, a desktop application can retrieve the application icons of the first 12 applications in the order they appear in the merged list.

[0599] S3405, Desktop Applications: Display the first 12 applications in the application panel D1. For example, display the application icons of the first 12 applications.

[0600] In this way, the desktop application can display more recommended apps in the order of the merged list.

[0601] It should be noted that after displaying the application panel D1, in response to the user's trigger operation on any application in the application panel D1, the application can also be launched using the process shown in Figure 33 above, which will not be elaborated here.

[0602] Feature 2: Recommend task groups.

[0603] Referring to Figure 35A, the process for providing recommended task groups in the task group list includes:

[0604] S3501, The desktop application detected a user's click on the layout button.

[0605] Upon detecting a click on the layout button, the execution of the display template list and task group list can be triggered, as shown in interface 2201 in Figure 22A above.

[0606] S3502, The desktop application requests the display layout template (showhnDesktopPatternView) from the desktop task controller (DsktopTaskController).

[0607] S3503, The desktop task controller requests the desktop style module to display the layout template (showhnDesktopPatternView).

[0608] S3504. The desktop application searches for the recommendation task group (isNeedFindTemplateUserData) in the recommendation engine module.

[0609] It should be noted that there is no specific order between S3502-S3503 and S3504 mentioned above.

[0610] Figure 35A illustrates the example of triggering the display of recommended task groups by clicking on a layout button. It should be noted that in the embodiment where the user selects a task group label, such as "Smart Recommendation," to trigger the display of recommended task groups, it is the desktop style module that detects the user's selection of the task group label. The desktop application in S3501-S3504 above should be replaced by the desktop style module.

[0611] S3505, Desktop Style Module loads template resource files.

[0612] After S3503, selecting a layout template allows loading template resource files, providing access to the resources to be displayed in the template list. For example, the template resource files might contain the icons for each layout template in template list 10011 mentioned earlier.

[0613] S3506, Desktop Style Module: Create a RecycleView.

[0614] A circular view can be used to display lists of templates and task groups.

[0615] S3507, The recommendation engine module determines the recommendation task group (getOpenFindTemplateUserData).

[0616] After S3504, the recommendation engine module can then execute S3507. There is no strict order between S3507 and S3505-S3506.

[0617] For details on the specific implementation of the recommendation engine module in determining the recommendation task group, please refer to the relevant introduction of the second method mentioned above, which will not be repeated here.

[0618] S3508, the desktop style module obtains the recommended task group (getPatternList) from the recommendation engine module. This gives the resources to be displayed in the task group list.

[0619] S3509, Desktop Style Module generates a loop view.

[0620] After generating the RecycleView, you can then display the list of templates and the list of task groups in the RecycleView.

[0621] Referring to Figure 35B, the process of launching the application after selecting the recommended task group includes:

[0622] S3521, The desktop style module detected that the user selected the recommended task group.

[0623] For example, when a user selects any recommended task group in the task group list, the desktop style module can detect this action event.

[0624] S3522, The desktop style module requests the start group task from the recommendation engine module.

[0625] The task group includes multiple applications from the recommended task group selected by the user.

[0626] S3523, when applied to the foreground, recommends that the engine module perform a avoidance animation to the Window Container Transaction (WCT).

[0627] An application in the foreground refers to a floating window that is displayed when the user selects a recommended task group. For example, the application in the foreground could be APP-1, to which floating window 4011 belongs in interface 2001.

[0628] After selecting a recommended task group, the application currently displayed in the foreground will move from its current position to the corresponding display area in the recommended task group, and an avoidance animation will be executed.

[0629] S3524. When the application is running in the background, the recommendation engine module should use warm start (start tasks) for window container transactions.

[0630] S3525, Application not started. Recommendation: The engine module builds startup parameters for the window container transaction and performs a cold start (send pending intent).

[0631] By using S3524 and S3525 as described above, all applications included in the recommended task group that are not displayed in the foreground can be launched. For example, if the user selects recommended task group 20011b in interface 2001, the applications not displayed in the foreground include APP-2 and APP-3.

[0632] S3526, The recommendation engine module requests operations (applyTransaction) from the task organization module for multiple window containers.

[0633] S3527. The task organization module executes the application startup process to the desktop task container (DsktopTaskContainer).

[0634] S3528, The desktop task container repositions the desktop tasks to the floating window controller.

[0635] S3529, The floating window controller obtains the repositioning task (getNeeRepositiontask) from the recommendation engine module.

[0636] The repositioned task is the task that was already displayed in the foreground when the user selected the recommended task group, such as the floating window 4011 in the example in S3523.

[0637] S3530 and the floating window controller record position differences and execute offset animations.

[0638] Location difference refers to the difference between the current location of the task that needs to be repositioned and its location within the user-selected recommended task group. This location difference can be used to perform offset animation, which is an animation of the repositioned task moving from its current location to its current location within the recommended task group.

[0639] S3531, the floating window controller sends cold and warm start tasks (getTaskBounds) to the recommendation engine module.

[0640] S3532, the floating window controller sets boundaries (setBounds) and reorders (setReorder) for window container transactions.

[0641] This allows us to determine the display area for each task.

[0642] S3533, the floating window controller returns the constructed WCT to the desktop task controller.

[0643] Next, when displaying recommended task groups selected by the user, the display can be based on the constructed WCT, which can move the currently displayed floating window to a new position and display other floating windows.

[0644] Function 3: One-click layout.

[0645] Referring to Figure 36, the one-click layout process includes:

[0646] S3600, the desktop style module detected a one-click layout request.

[0647] For example, in response to a user's trigger operation on the one-click layout button, or trigger operation 2 on the layout button, such as a long press operation, the desktop style module can detect the one-click layout request.

[0648] S3601, The desktop style module obtains the layout template (getSuggestionTemplateID) from the recommendation engine module.

[0649] In this way, the desktop style module can determine the layout template for a one-click layout of multiple currently displayed floating windows.

[0650] For details on the specific implementation of the recommendation engine module in determining the layout template, please refer to the previous explanation of the first method; it will not be repeated here.

[0651] S3602, Desktop Style Module Template Creation Indicator (creatTemplateIndicator).

[0652] This allows us to begin determining the layout and position of the multiple currently displayed floating windows.

[0653] S3603, Desktop Style Module: Create View (creatView).

[0654] The view is used to display the various floating windows.

[0655] S3604, The desktop style module initializes the selection view (initSelectView) to the template module.

[0656] S3605, Template module triggers automated template (autoTemplate).

[0657] S3606, The template module obtains the position information of each application layout from the recommendation engine module (getTemplateIdList).

[0658] This allows us to determine the display area for each floating window.

[0659] For details on how the recommendation engine module determines the display area of ​​each floating window, please refer to the explanation of the first method above; it will not be repeated here.

[0660] S3607, Template module sets the target location of the task (setTaskToTargetRegion).

[0661] S3608, Template module filling task (fillingTask).

[0662] In short, the task of each floating window is filled into the corresponding target position, and finally the floating window is displayed at the target position.

[0663] S3609, The template module sets boundaries (setBounds) and reorders (setReorder) for window container transactions.

[0664] This application also provides an electronic device, which may include a display screen, a memory, and one or more processors (such as a CPU, GPU, NPU, etc.). The display screen, memory, and processor are coupled. The memory is used to store computer program code, which includes computer instructions. When the processor executes the computer instructions, the electronic device can perform various functions or steps performed by the device in the above method embodiments.

[0665] This application also provides a chip system. The chip system includes at least one processor and at least one interface circuit. The at least one processor and at least one interface circuit are interconnected via lines. The processor is used to support an electronic device in implementing the various steps in the above method embodiments, and the at least one interface circuit can be used to receive signals from other devices (e.g., memory) or to send signals to other devices (e.g., a communication interface). The chip system may include a chip and may also include other discrete devices.

[0666] This application also provides a computer storage medium including instructions that, when executed on the electronic device, cause the electronic device to perform the steps in the above method embodiments.

[0667] This application also provides a computer program product including instructions that, when executed on the electronic device, cause the electronic device to perform the steps in the method embodiments described above.

[0668] The technical effects of the chip system, computer storage medium, and computer program product are similar to those in the preceding method embodiments.

[0669] It should be understood that in the various embodiments of this application, the order of the above-mentioned processes does not imply the order of execution. The execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of this application.

[0670] Those skilled in the art will recognize that the modules and algorithm steps of the various examples described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are implemented in hardware or software 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.

[0671] Those skilled in the art will understand that, for the sake of convenience and brevity, the specific working processes of the systems, devices, and modules described above can be referred to the corresponding processes in the foregoing method embodiments, and will not be repeated here.

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

[0673] The modules described as separate components may or may not be physically separate. The components shown as modules may or may not be physical modules; that is, they may be located on one device or distributed across multiple devices. Some or all of the modules can be selected to achieve the purpose of this embodiment according to actual needs.

[0674] In addition, the functional modules in the various embodiments of this application can be integrated into one device, or each module can exist physically separately, or two or more modules can be integrated into one device.

[0675] In the above embodiments, implementation can be achieved entirely or partially through software, hardware, firmware, or any combination thereof. When implemented using software programs, implementation can be entirely or partially in the form of a computer program product. This computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on a computer, all or part of the processes or functions described in the embodiments of this application are generated. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer instructions can be stored in a computer storage medium or transmitted from one computer storage medium to another. For example, the computer instructions can 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 storage medium can be any available medium accessible to a computer or a data storage device including one or more servers, data centers, etc., that can be integrated with the medium. The available medium can be a magnetic medium (e.g., floppy disk, hard disk, magnetic tape), an optical medium (e.g., DVD), or a semiconductor medium (e.g., solid-state disk (SSD)).

[0676] The above description is merely a specific embodiment of this application, but the scope of protection of this application is not limited thereto. Any variations or substitutions that can be easily conceived by those skilled in the art within the scope of the technology disclosed in this application should be included within the scope of protection of this application. Therefore, the scope of protection of this application should be determined by the scope of the claims.

Claims

A display method characterized by comprising: include: Display a first interface, the first interface including a first taskbar, the first taskbar including an icon of a first application and a first button; In response to the first operation, a second interface is displayed, the second interface including a second taskbar, the second taskbar including an icon of the first application, a second button and a third button, and the first operation including an operation on the first button; In response to the second operation, a third interface is displayed, the third interface including a first window of the first application and a second taskbar, the window size of the first window is smaller than the window size of the full-screen display window of the first application, and the second operation includes operations on the icon of the first application; In response to the third operation, a fourth interface is displayed, the fourth interface including the first window, icons for at least one recommended task group and the second taskbar, each recommended task group icon including the identifiers of at least two applications, each recommended task group icon including the identifier of the first application, and the third operation including the operation of the third button; In response to the fourth operation, a fifth interface is displayed, the fifth interface including the first window and the second window of the second application, the fourth operation including the operation on the icon of the first recommended task group, the icon of the first recommended task group including the identifier of the first application and the identifier of the second application, the position of the first window in the fifth interface is different from the position of the first window in the third interface. The method of claim 1, wherein The layout of the first and second windows in the fifth interface is the same as the layout of the icons of the first and second applications in the first recommended task group. The method according to claim 1 or 2, characterized in that The second interface includes an icon and wallpaper image of a third application, the icon of which is displayed in an area outside the second taskbar; The third interface includes wallpaper images but does not include the icon of the third application. The method according to any one of claims 1-3, characterized in that The fifth interface includes a second taskbar; After displaying the fifth interface, the method further includes: In response to the fifth operation, a sixth interface is displayed. The sixth interface includes the first taskbar and also includes a full-screen display window of the first application or a full-screen display window of the second application. The fifth operation includes an operation on the second button. The method according to claim 4, characterized in that After displaying the sixth interface, the method further includes: In response to the sixth operation, a seventh interface is displayed, the seventh interface including the second taskbar and the first window, the seventh interface not including the second window, and the sixth operation including the operation on the first button in the first taskbar. The method according to any one of claims 1-5 is characterized in that, The fourth interface also includes an icon for at least one layout template, and each layout template icon includes at least two task areas. The method according to any one of claims 1-5, characterized in that The response to the third operation, displaying the fourth interface, includes: In response to the operation of the third button, an eighth interface is displayed, which includes an icon of at least one layout template and a fourth button, and each layout template icon includes at least two task areas. In response to the operation of the fourth button, the fourth interface is displayed. The method according to any one of claims 1-7, characterized in that The second taskbar in the third interface includes an icon for the fourth application; After displaying the third interface, the method further includes: In response to the seventh operation, a ninth interface is displayed, which includes the second taskbar, the first window, and the third window of the fourth application. The seventh operation includes operations on the icon of the fourth application. In response to the eighth operation, a tenth interface is displayed, which includes the first window and the third window. The eighth operation includes an operation on the third button in the second taskbar. The position of the first window in the ninth interface is different from the position of the first window in the tenth interface, and the position of the third window in the ninth interface is different from the position of the third window in the tenth interface. The method of claim 8, wherein The response to the eighth operation, displaying the tenth interface, includes: In response to the operation of the third button, an eleventh interface is displayed, which includes an icon of at least one layout template and a fifth button. Each layout template icon includes at least two task areas. In response to the operation of the fifth button, the tenth interface is displayed. The method according to any one of claims 1-9, characterized in that After displaying the second interface, the method further includes: In response to the ninth operation, a twelfth interface is displayed, the twelfth interface including an icon of at least one layout template, each layout template icon including at least two task areas, the ninth operation including an operation on the third button; In response to an operation on the icon of the first layout template, a thirteenth interface is displayed, the thirteenth interface including a first display area and a second display area, each display area including icons of at least two applications. The method of claim 10, wherein After displaying the thirteenth interface, the method further includes: In response to the tenth operation, the fourteenth interface is displayed, which includes the first display area and the second display area. The first display area includes the fourth window of the fifth application and does not include the application icon. The second display area includes the icons of at least two applications. Specifically, at least two application icons in the second display area of ​​the fourteenth interface are different from those in the second display area of ​​the thirteenth interface; and / or, the order of the icons in the second display area of ​​the fourteenth interface is different from that in the second display area of ​​the thirteenth interface. The method according to any one of claims 1-11, characterized in that After displaying the second interface, the method further includes: In response to the third operation, a fifteenth interface is displayed, the fifteenth interface including at least one icon for a recommended task group and a second task bar, wherein the icon for the at least one recommended task group in the fifteenth interface is different from the icon for the at least one recommended task group in the fourth interface. The method according to any one of claims 1-12, characterized in that The second interface includes an icon for the sixth application; After displaying the second interface, the method further includes: In response to the eleventh operation, the sixteenth interface is displayed, the sixteenth interface including the fifth window of the sixth application and the second taskbar, the window size of the fifth window is smaller than the window size of the full-screen display window of the sixth application, and the eleventh operation includes operation on the icon of the sixth application; In response to the third operation, a seventeenth interface is displayed, which includes the fifth window and the second taskbar, and also includes a prompt message indicating that there are no recommendations at the moment. The method according to any one of claims 1-13, characterized in that After displaying the fifth interface, the method further includes: The eighteenth interface is displayed, which includes a sixth window, a seventh window, an eighth window, and a ninth window. The sixth, seventh, and eighth windows are portrait windows, and the ninth window is a landscape window. The eighteenth interface also includes icons for a second layout template and a third layout template. The icons for the second layout template include a first task area, a second task area, and a third task area. The first task area is a vertical task area, and the second and third task areas are horizontal task areas. The icons for the third layout template include a fourth task area, a fifth task area, and a sixth task area. The fourth, fifth, and sixth task areas are vertical task areas. In response to an operation on the icon of the second layout template, a nineteenth interface is displayed, which includes a sixth window, a ninth window, and a third display area. The third display area includes a seventh window and an eighth window. The positions of the sixth window, the ninth window, and the third display area relative to the display screen correspond one-to-one with the positions of the first task area, the second task area, and the third task area relative to the icons of the second layout template. In response to an operation on the icon of the third layout template, a twentieth interface is displayed. The twentieth interface includes a sixth window, an eighth window, and a fourth display area. The fourth display area includes a seventh window and a ninth window. The positions of the sixth window, the eighth window, and the fourth display area relative to the display screen correspond one-to-one with the positions of the fourth task area, the fifth task area, and the sixth task area relative to the icons of the third layout template. The method according to any one of claims 1-14, characterized in that The response to the third operation, displaying the fourth interface, includes: In response to the third operation, query the first task group data of each layout template, the first task group data including the identifier of a layout template and the identifier of the first application; When there are multiple first task group data for any layout template, the target first task group data for any layout template is selected from the multiple first task group data based on the number of times the first task group data is used and / or the last time it was used; when there is only one first task group data for any layout template, the first task group data is the target first task group data for any layout template. The fourth interface is displayed, which includes at least one recommended task group. The at least one recommended task group includes the first task group in the target first task group data. The first task group includes the identifiers of at least two applications. The first task group includes the identifier of the first application. The method according to claim 8 or 9, characterized in that The response to the eighth operation, displaying the tenth interface, includes: In response to the eighth operation, query the second task group data. The number of application identifiers in the task group of the second task group data is the same as the number of windows in the multiple windows in the ninth interface. The multiple windows include the first window and the third window. If the second task group data is found and there are multiple second task group data, a target second task group data is selected from the multiple second task group data. The target second task group data is the task group data that includes the most target application identifiers among the multiple second task group data. The target application identifier is the identifier of the application to which the multiple windows belong. If there is only one second task group data, the second task group data is the target second task group data. On the tenth interface, the multiple windows are laid out according to the task group and layout template identifiers in the target second task group data. The method of claim 16, wherein The method further includes: If no data for the second task group is found, select a target layout template. The target layout template is the layout template with the highest matching degree with the landscape and portrait orientation of the multiple windows among the layout templates with the same number of task areas as the number of windows of the multiple windows. The multiple windows are laid out according to the target layout template on the tenth interface. The method according to claim 10 or 11, characterized in that The step of displaying the thirteenth interface in response to an operation on the icon of the first layout template includes: In response to an operation on the icon of the first layout template, query the data of the third task group, which includes the identifier of the first layout template; Traverse each display area, count the applications that have been displayed in the current display area and their display counts in the data of the third task group, and obtain the first application sorted by the number of times it has been displayed in the current display area from high to low. The current display area is a landscape display area. The landscape applications and the applications in the first application sort are filtered out from the number of times the installed applications are launched to obtain the second application sort. The first application sort and the second application sort are combined to obtain the first recommended sort. The icons of the first number of applications in the first recommended sort are displayed in the current display area of ​​the thirteenth interface. The current display area is a vertical display area. The vertical screen applications and the applications in the first application sort are filtered out from the number of times the installed applications are launched to obtain the third application sort. The first application sort and the third application sort are combined to obtain the second recommended sort. The icons of the first number of applications in the second recommended sort are displayed in the current display area of ​​the thirteenth interface. An electronic device, characterized by comprising: The electronic device includes: one or more processors; a memory; wherein the memory is coupled to the one or more processors, the memory is used to store computer program code, the computer program code including computer instructions, and the one or more processors call the computer instructions to cause the electronic device to perform the method as described in any one of claims 1-18. A computer program product comprising instructions, characterized in that When the computer program product is run on an electronic device, it causes the electronic device to perform the method as described in any one of claims 1-18. A computer-readable storage medium comprising instructions, characterized in that, When the instructions are executed on an electronic device, the electronic device causes the electronic device to perform the method as described in any one of claims 1-18.

Images