Desktop layout method and electronic device

Abstract

The present application provides a desktop layout method and an electronic device. The method comprises: in response to an operation of starting a desktop, displaying a first desktop interface on an electronic device, wherein the first desktop interface comprises a first summary message and a card stack area, the card stack area is used for displaying at least one card in a stacked manner, each card corresponds to one application category, and each card comprises an icon of at least one application; in response to a tap operation of a user on the first summary message, displaying a message summary bar for each message on the electronic device; in response to a tap operation of the user on a message summary bar for a first message to be processed, starting a first application corresponding to the first message to be processed; and in response to a tap operation of the user on a first card, displaying a second desktop interface, wherein the second desktop interface comprises an application type bar corresponding to the first card, a card display area, and an application icon display area. The solution changes traditional desktop layout methods, allowing users to handle messages more efficiently and quickly.

Description

Desktop layout methods and electronic devices Technical Field

[0001] This application relates to the field of electronic device technology, and more particularly to a desktop layout method and electronic device. Background Technology

[0002] With the continuous development of technology, electronic devices are becoming increasingly multifunctional, capable of supporting numerous applications, each containing a multitude of services. This makes it difficult for users to quickly find the service they want. Furthermore, various chat, shopping, and lifestyle applications generate a wide variety of incoming messages, notifications, and alerts, such as chat messages, text messages, call notifications, delivery notifications, food delivery notifications, and calendar reminders. This further complicates the process, making it challenging for users to quickly locate and process the messages they wish to view or handle.

[0003] When using electronic devices, users need to search through numerous application icons on the desktop interface to find the target application each time they turn on the device. They also need to find the target service or view various messages or notifications from the target application or service. When users need to view multiple messages distributed across multiple applications, they need to repeat the above steps of searching for applications and opening applications to find messages multiple times. This process is cumbersome, time-consuming, and laborious.

[0004] In short, existing desktop layout solutions cannot allow users to quickly process various messages generated before electronic devices are turned on. Therefore, how to make the desktop layout more reasonable so that users can easily find and manage messages is an urgent technical problem to be solved.

[0005] Summary of the Invention

[0006] This application provides a desktop layout method and an electronic device that enables users to quickly process various messages generated before the electronic device is turned on.

[0007] In a first aspect, a desktop layout method is provided, comprising: in response to an operation of launching a desktop, displaying a first desktop interface on an electronic device, the first desktop interface including a first summary message and a card stacking area, the card stacking area being used to stack and display at least one card, each card corresponding to an application category, and each card including an icon of at least one application; the first summary message being used to indicate at least one pending message generated in the electronic device prior to the operation of launching the desktop; in response to a user's click operation on the first summary message, displaying a first display interface on the electronic device, the first display interface including a message summary bar for each message in the at least one pending message; in response to a user's click operation on the message summary bar of the first pending message, launching a first application, the first pending message being any one of the at least one pending message, and the first application being the application corresponding to the first pending message; in response to a user's click operation on a first card, displaying a second desktop interface, the second desktop interface including an application type bar, a card display area, and an application icon display area, the application type bar including the application type corresponding to the first card, the card display area including the first card, and the application icon display area being used to display icons of all applications in the first card; the first card being a card in the card stacking area.

[0008] This technical solution primarily changes the traditional desktop layout by summarizing and displaying messages generated before the electronic device is turned on. Users can then click on the summarized messages to view further content, achieving more efficient and faster message processing. By focusing on the messages that need processing, the solution guides users to decide how to proceed based on the summarized information, eliminating the need to manually check all applications for messages as in traditional solutions. This avoids the tedious steps of opening each application individually and then locking onto the messages requiring management. Because the summarized messages aggregate messages that meet user management expectations, this solution allows for quick identification and management of the messages that need attention. The card stacking area categorizes applications by type and presents them in a stacked manner, allowing users to access the corresponding desktop sub-screen for further interaction by clicking on cards in the card stacking area.

[0009] In one possible implementation, the first card is the topmost card in the card stack area.

[0010] It should be understood that traditional solutions require first finding the application, then opening the target application, and then finding the message. This process needs to be repeated repeatedly to process all the messages. The solution in this application, however, first aggregates all messages, then allows users to select the message they want to process based on their needs. With a simple click, the corresponding application or service can be opened, thus achieving convenient message processing.

[0011] In conjunction with the first aspect, in some implementations of the first aspect, the method further includes: displaying the running interface of the first application in the form of a pop-up window in the first display interface; and managing the first pending message in response to the user's management operation on the first pending message in the running interface of the first application. In this implementation, by directly launching and displaying the first application, the user can directly manage messages in the first application without having to exit the desktop interface and search for and launch the first application again, which is convenient for subsequent user operations. The pop-up window display also makes it easy for the user to know that the first display interface is also displayed at the bottom of the pop-up window, thus allowing the user to quickly return to the first display interface according to the pop-up window's display logic.

[0012] In conjunction with the first aspect, in some implementations of the first aspect, the method further includes: in response to a user's click operation on the message summary bar of the first pending message, displaying at least one associated icon in the form of a pop-up window in the first display interface. The at least one associated icon includes the icon of at least one application associated with the first pending message and / or the icon of at least one service associated with the first pending message. In this implementation, associated icons are also provided to facilitate user access to the relevant applications.

[0013] In one example, the method further includes: responding to a user's click on any one of the at least one associated icon, launching and displaying the running interface of the application or service corresponding to the clicked icon. In this example, when a user clicks any associated icon, they can enter the application corresponding to that icon without having to exit the current interface and then launch the associated application, thus improving the user experience.

[0014] In conjunction with the first aspect, in some implementations of the first aspect, the first display interface is displayed as a pop-up window within the first desktop interface. However, it should be understood that, besides being displayed as a pop-up window, the first display interface can also be a regular display interface, rather than a small window like a pop-up window. In this case, the pop-up window display format allows users to quickly return to the first desktop interface according to the pop-up window's display logic.

[0015] In conjunction with the first aspect, in some implementations of the first aspect, the first desktop interface further includes a second summary message, which indicates at least one pending transaction. The method further includes: in response to a user's click on the second summary message, displaying a second display interface on the electronic device, the second display interface displaying at least one transaction summary bar, each transaction summary bar corresponding to a pending transaction; and in response to a user's click on a first transaction summary bar, launching and displaying the running interface of the application or service corresponding to the first transaction summary bar in a pop-up window on the second display interface, the first transaction summary bar being any one of the at least one transaction summary bar. This implementation provides a management process for pending transactions; by viewing and clicking on the summaries of pending transactions, users can quickly access the corresponding application or service for processing.

[0016] In conjunction with the first aspect, in some implementations of the first aspect, the method further includes: in response to a user's click on the first transaction summary bar, displaying at least one associated icon in a pop-up window in the second display interface. The at least one associated icon includes an icon for at least one application and / or service associated with the first transaction summary bar. In this implementation, displaying the associated icon facilitates the user's use of the associated application or service.

[0017] In one example, the method further includes: responding to a user's click on any one of the at least one associated icon, launching and displaying the running interface of the application or service corresponding to the clicked icon. In this example, the user can quickly enter the associated application or service by clicking the associated icon, without having to exit the current interface and then launch the associated application or icon, which is more convenient.

[0018] In conjunction with the first aspect, in some implementations of the first aspect, the second display interface is displayed as a pop-up window within the first desktop interface. However, it should be understood that besides being displayed as a pop-up window, the second display interface can also be a regular display interface, rather than a small window like a pop-up window. Here, the pop-up window display format allows users to quickly return to the first desktop interface according to the pop-up window's display logic.

[0019] In conjunction with the first aspect, in some implementations of the first aspect, the method further includes: responding to a user's click on the first icon in the first card of the card stack area, launching and displaying the running interface of the application or service corresponding to the first icon. In this implementation, application icons are presented to the user in the form of cards according to type, allowing the user to directly enter the application by clicking any icon in the card, which is convenient and quick. In one example, the method further includes: responding to a user's click on any application icon in the application icon display area, launching the application and displaying the application's running interface. In this example, the user can enter the corresponding application by clicking the icon in the application icon display area. When the application the user wants to launch is not in the card display area, the user can find and launch the application by following the steps in this example.

[0020] In another example, the method further includes: in response to a user's swipe gesture in the application icon display area, displaying the application icon that was not previously displayed on the second desktop interface. When an application type contains too many application icons, the user can swipe to view other application icons that are not currently displayed on the screen.

[0021] In conjunction with the first aspect, in some implementations of the first aspect, the method further includes: responding to a user's first operation on the second desktop interface, displaying a third desktop interface. The third desktop interface includes an application type bar, a card display area, and an application icon display area. The application type bar includes the application type corresponding to the second card, the card display area includes the second card, and the application icon display area displays icons for all applications in the second card. In other words, the first operation can be used to switch to a desktop sub-screen corresponding to another application type.

[0022] In one example, the first action is either a horizontal swipe on the second desktop interface, or a click on the application type corresponding to the second card in the application type bar on the second desktop interface. This example provides a demonstration of the first action for switching desktop sub-screens.

[0023] In conjunction with the first aspect, in some implementations of the first aspect, the first card is the topmost card in the card stacking area. The method further includes: in response to a user's swipe operation on the first card, displaying the first card stacked below the first card on the top layer of the card stacking area. In this implementation, the topmost card can be changed via a swipe operation.

[0024] In one example, the method further includes: in response to a user's swipe gesture on the first card, displaying the first card at the bottom of the card stacking area. In this example, displaying the topmost first card at the bottom of the stacking area, instead of deleting it directly, prevents the user from accidentally deleting the first card and being unable to find the application from the first card.

[0025] In conjunction with the first aspect, in some implementations of the first aspect, the method further includes: responding to a second operation by the user on the second desktop interface, displaying an editing interface for the second desktop interface; responding to a third operation by the user on the editing interface of the second desktop interface, managing the application icons corresponding to the second desktop interface, wherein the third operation includes at least one of the following: adding an application icon to an application type corresponding to the second desktop interface, deleting an application icon from an application type corresponding to the second desktop interface, adjusting the display icon in the card corresponding to the second desktop interface, and adding, deleting, or modifying the application type name in the application type bar of the interface. In this implementation, a method for editing desktop sub-screens is provided.

[0026] In one example, the second action is a two-finger pinch gesture on the second desktop interface. However, it should be understood that it could also be another action, such as clicking on the corresponding control, to enter the editing interface.

[0027] In conjunction with the first aspect, in certain implementations of the first aspect, when displaying the first desktop interface on the electronic device in response to the desktop launch operation, it may include: when the desktop style of the electronic device is the smart style, displaying the first desktop interface on the electronic device in response to the desktop launch operation; or, when the desktop style of the electronic device is not the smart style, displaying the desktop interface corresponding to the current desktop style on the electronic device in response to the desktop launch operation. In this implementation, the aforementioned first desktop interface is only accessed when the desktop style is the smart style, while when the desktop style is not the smart style, a desktop interface of another style is displayed, and elements such as the first summary message and card stacking area in the aforementioned first desktop interface are not displayed, and the aforementioned subsequent steps are not executed. This implementation provides an example of the coexistence between the newly created desktop style (desktop layout scheme) and the original desktop style of this application.

[0028] In a second aspect, a desktop layout apparatus is provided, the apparatus comprising a unit consisting of software and / or hardware for performing any of the methods of the first aspect.

[0029] Thirdly, an electronic device is provided, comprising: one or more processors, and a memory; the memory is coupled to the one or more processors, the memory being used to store computer program code, the computer program code including computer instructions, wherein the one or more processors invoke the computer instructions to enable the electronic device to implement any of the methods of the first aspect.

[0030] Fourthly, a computer-readable storage medium is provided, the computer-readable storage medium including instructions that, when executed on an electronic device, enable the electronic device to implement any of the methods of the first aspect.

[0031] Fifthly, a computer program product is provided, comprising a computer program that, when executed by an electronic device, can implement any of the methods of the first aspect. Attached Figure Description

[0032] Figure 1 is a schematic interactive diagram of message management in a traditional desktop layout scenario.

[0033] Figure 2 is a schematic interactive diagram of a global message summary processing procedure according to an embodiment of this application.

[0034] Figure 3 is a schematic interactive diagram of a global service summary processing procedure according to an embodiment of this application.

[0035] Figure 4 is a schematic diagram of another summary message processing procedure according to an embodiment of this application.

[0036] Figure 5 is a schematic interactive diagram of a desktop sub-screen according to an embodiment of this application.

[0037] Figure 6 is a schematic diagram of an editing interface for a desktop sub-screen according to an embodiment of this application.

[0038] Figure 7 is a schematic interactive diagram of selecting a desktop style according to an embodiment of this application.

[0039] Figure 8 is a schematic flowchart of a desktop layout method according to an embodiment of this application.

[0040] Figure 9 is a schematic diagram of the hardware structure of an electronic device according to an embodiment of this application. Detailed Implementation

[0041] The embodiments of this application will now be described in conjunction with the accompanying drawings.

[0042] Figure 1 is a schematic interactive diagram of message management in a traditional desktop layout scenario. As shown in Figure 1, in a traditional desktop layout, icons of many applications are displayed on the desktop. When an application generates messages that need to be processed, the total number of these messages is displayed above the application icon. Based on this display, the user clicks to open the applications that need to process the messages for message management. As shown in interface 101 of Figure 1, applications such as email, phone, SMS, settings, fitness, shopping, browser, dining, music, cloud storage, and transportation all have messages that need to be managed, and the number varies. Therefore, when the user wants to manage these messages, the user can only open each application to view and manage the messages one by one. Figure 1 takes opening the music application for message management as an example. When the user clicks the music application icon in desktop interface 101, the electronic device responds to the click operation and launches the music application. As shown in interface 102, the music application displays the homepage content after being launched. When the user clicks the "My" option on interface 102, the electronic device responds to the click and enters the user information management interface, as shown in interface 103. Interface 103 contains a message management control, and the number of messages requiring processing is indicated on the control. When the user clicks the message management control on interface 103, the electronic device responds to the click and opens the message management interface (not shown in Figure 1), allowing the user to view and manage messages. It can be seen that in the example shown in Figure 1, viewing and managing messages in the music application requires three search and click operations before entering the message management interface, where messages can then be viewed and managed. If the user needs to view and manage all messages, they must repeat the above operations for each application, which is time-consuming and laborious.

[0043] Furthermore, electronic devices generate a vast number and diverse range of messages. Some of these messages are unnecessary for the user, while others are crucial and require prompt attention. For example, missed calls may include unwanted advertising or sales calls, or important calls from family or work, requiring the user to open the phone app and filter each message. Emails may contain spam that the user wants to ignore, or important work emails and notifications, requiring the user to open the email app and process each message. Shopping apps may generate messages such as shopping progress updates, reminders, and logistics information, as well as promotional or advertising messages from merchants, all requiring user filtering and processing. SMS apps may send notifications, travel reminders, or irrelevant messages. Other scenarios are not listed here. This complexity of messages, scattered across various applications, makes it difficult for users to process quickly and identify useful information.

[0044] To address the aforementioned issues, this application proposes a novel desktop layout scheme. By summarizing numerous pending messages and displaying these summaries on the desktop, users can easily view and manage messages by clicking on them. This approach uses the summary messages as a starting point to launch applications, enabling users to quickly process messages, especially those that meet their management needs. This eliminates the need for users to rummage through applications, open them one by one, and check for messages requiring processing and management, as is common in traditional solutions.

[0045] Figure 2 is a schematic interactive diagram illustrating a global message summary processing procedure according to an embodiment of this application. Interface 201 in Figure 2 can be seen as an example of the first desktop interface (first screen) in the desktop layout scheme of this application embodiment, i.e., an example of the first desktop interface. The electronic devices in this application embodiment can be mobile phones, tablets, laptops, in-vehicle systems, smart wearable devices, and other electronic devices.

[0046] When an electronic device starts up its desktop, the first desktop screen that is displayed is the desktop home screen, as shown in interface 201 in Figure 2.

[0047] It should be noted that the operation to launch the desktop can be any user operation that can trigger desktop launch, such as fingerprint unlocking, password unlocking, facial recognition unlocking, mechanical button unlocking, and other screen wake-up operations.

[0048] As shown in interface 201, the desktop home screen (an example of the first desktop interface) includes a global message summary area and a frequently accessed application area. The global message summary area includes a global message summary (an example of the first summary message) and / or a global service summary (an example of the second summary message). Both the global message summary and the global service summary are displayed in the form of floating capsules, and the number of summaries is displayed. The frequently accessed application area includes a card stacking area and a frequently used application fixed area. The frequently used application fixed area displays multiple application icons, while the card stacking area displays at least one card in a stacked manner. Each card corresponds to an application type, and each card includes at least one application icon.

[0049] It should be noted that Interface 201 is merely an example for the desktop home screen. When applying this solution in practice, some modifications and adjustments can be made. For instance, the global message summary area could have only one summary, which includes both chat messages and notifications or other types of messages generated by various services / applications—that is, the summary includes both primary and secondary summary information. Another example is that the maximum number of application icons that can be displayed on each card in the card stacking area can be set as needed. Yet another example is that the high-frequency application access area does not include a fixed area for frequently used applications. Other possible scenarios are not listed here.

[0050] It should also be understood that in Figure 2, "service" and "message" are separated. "Message" can be understood as messages generated from chat communication with other users, i.e., messages sent by real people, intelligent customer service, or various robots. "Service," on the other hand, refers to pending transactions generated within an application or service, such as delivery notifications, software update notifications, pre-order notifications, game reminders, schedule reminders, travel information reminders, etc. In some cases, for ease of understanding, "message" can be understood as "chat content," and "service" as all other information or transactions besides "message." The "Global Service Summary," also known as the "Global Transaction Summary," can be understood as each transaction corresponding to a service, and each service may generate one or more transactions, or none at all.

[0051] In another example, the distinction between "message" and "service" can be omitted, and they can all be referred to as "message" or "information".

[0052] When a user clicks on the global message summary in interface 201, interface 202 is displayed on the electronic device in response to the click. Interface 202 can be seen as an example of the first display interface. As shown in interface 202, it displays a summary of the messages that need to be processed (pending messages). Each pending message corresponds to a message summary column, but it should be understood that each message summary column can also correspond to multiple pending messages. This message summary column mainly summarizes the actual content of the pending messages. For example, the following examples are provided: a message from "Mom": "Mom asks about your recent life and wants you to buy some household items when you come home this weekend"; a message from "Boss": "Boss needs you to purchase a piece of equipment"; a message from "Wife": "Wife asks when you will be home tonight and is worried about the children's studies"; a message from "Little A": "Little A has invited you to a weekend dinner party." It can be seen that the message summary column does not simply copy the messages, but summarizes the substantive content of the messages, making it easier for users to obtain key information.

[0053] The sources of messages in the global message summary can be text and / or voice messages from chat applications, messages from SMS applications, or text and / or voice messages from chat services in other applications.

[0054] When a user clicks on any message summary bar in interface 202, the electronic device responds to the click operation by launching the application / service corresponding to that message summary bar, so that the user can view the detailed content of the message or manage the message in the corresponding application interface.

[0055] Figure 2 uses a user clicking on a message summary from "Mom" that reads, "Mom asks about your recent life and wants you to buy some groceries when you come home this weekend." When the user clicks on this summary, the electronic device responds by displaying interface 203. Interface 203 then displays the running interface of the application (the target application) corresponding to the summary in a pop-up window. This running interface shows the chat interface with "Mom" within the corresponding chat application. It can be seen that the central idea of ​​the chat message in the running interface corresponds to the content described in the summary. Furthermore, interface 203 also displays related icons in a pop-up window. These related icons mainly represent applications / services associated with the message content; for example, icons for several shopping applications, such as Shopping App A, are shown. Since the chat mentions the need to buy groceries, the icons of several shopping applications are displayed as related icons to facilitate quick selection of an application for shopping.

[0056] In another possible example, suppose a message summary bar reads, "Little B tells you to try to arrive at the station before 8 o'clock to catch the same train," and the associated icons could be icons of travel-related applications such as ride-hailing apps, map apps, etc.

[0057] Related icons can be generated by extracting keywords from the message summary bar and then identifying matching related applications and / or services based on those keywords. The icons for these related applications then constitute the associated icons for that message summary bar. Keyword extraction and matching application generation can be performed using two separate models, such as two neural network models: one for keyword extraction and the other for identifying matching applications. However, it should be understood that a single, unified neural network model can also be used to generate associated icons for any message summary bar. This model can extract keywords from the message summary bar and then identify matching applications based on those keywords.

[0058] It should be understood that interface 203 uses a pop-up window to display the target application's running interface and associated icons as an example. In actual applications, it is also possible to display only the normal interface of the target application's running interface and associated icons without using a pop-up window. The pop-up window format allows users to easily return to the previous display interface (i.e., return to interface 202) by clicking on an empty area of ​​the screen (areas other than the target application's running interface and associated icons area), thereby continuing to view and process other messages.

[0059] In one example, when a user clicks on an area of ​​interface 203 other than the target application's running interface and associated icon area, the electronic device responds to the click operation, re-displays interface 202, and sets the aforementioned message summary bar to the "processed" state upon re-displaying interface 202. That is, in interface 202, to facilitate user differentiation between processed and unprocessed message summary bars, they can be presented with different states. For example, the "processed" message summary bar can be grayed out, while the "unprocessed" message summary bar will not be grayed out. Another example is to add a checkmark to the "processed" message summary bar to indicate that the message summary bar has been processed, while the "unprocessed" message summary bar will not have a checkmark. Other methods to distinguish whether a message has been processed are not listed here.

[0060] Figure 2 uses the processing of global message summaries as an example, but it should be understood that a similar interactive process can be used to display and manage global service summaries. Figure 3 is a schematic interactive diagram of a global service summary processing procedure according to an embodiment of this application. As shown in Figure 3, when a user clicks on the capsule of global service summaries in interface 201, the electronic device responds to the click operation by displaying interface 204, which displays the application or service transactions that need to be processed. Interface 204 mainly shows the following examples: "Courier locker pickup code 345625", "Flight HB1234 departing in 4 hours", "A platform takeaway expected to arrive in 10 minutes", and "A live broadcast reminder for Shopping B application that you are following, which will start in 5 minutes". When a user clicks on any of the transaction summary columns, they can enter the running interface of the application / service corresponding to that transaction summary column to process the transaction.

[0061] It should be understood that, for transactions, after launching and displaying the corresponding application / service, associated icons can also be displayed as shown in interface 203 of Figure 2 to facilitate users' use of other related applications. For example, after clicking on the "Flight" transaction summary bar, a catering application or a ride-hailing application can be displayed to facilitate users' ordering of food or hailing a taxi. However, it should be understood that not all transactions need associated icons. For example, picking up a package from a parcel locker does not require other associated icons. It should also be understood that for some transactions, there may be multiple corresponding applications / services. In this case, the application priority can be set to determine which application is launched after clicking on the transaction summary bar. For example, for the transaction "Flight HB1234 departing in 4 hours", it may come from an alarm reminder from a calendar application, a travel reminder SMS from an airline in a text messaging application, a travel reminder email from a ticketing platform in an email application, or a flight reminder message from a ticketing application. This involves multiple applications. In this case, the priority of the corresponding application can be set to determine which application's running interface should be displayed when the transaction summary bar is clicked.

[0062] Figure 4 is a schematic diagram of another summary message processing procedure according to an embodiment of this application. As shown in Figures 2 and 3 above, when the user clicks on the global message summary in interface 201, interface 202 is displayed. When the user clicks on the global service summary in interface 201, interface 204 is displayed. Both interfaces 202 and 204 only display the details corresponding to the clicked global message summary capsule. Figure 4 shows an example of another interaction process. As shown in Figure 4, assuming the user clicks on either "global service summary" or "global message summary" in interface 201 (here, clicking on "global service summary" is used as an example), in response to the click operation, interface 209 is displayed on the electronic device. Interface 209 includes both a message summary column for messages that need to be processed and a transaction summary column for transactions that need to be processed.

[0063] However, it should be understood that although interface 209 shows the message summary bar above the transaction summary bar, in actual applications, the transaction summary bar can also be above the message summary bar, and there is no limitation.

[0064] It should also be understood that interface 209 can also be displayed in response to the user's subsequent click on "Global Service Summary" and "Global Message Summary". In other words, after the user clicks on either of the two global summaries, interface 202 or interface 204 is displayed. If the user returns to interface 201 from interface 202 or 204 and then clicks on the other global summary, interface 209 is displayed. For example, when the user clicks on "Global Message Summary" in interface 201, interface 202 is displayed. When the user returns to interface 201 from interface 202, interface 201 is displayed. When the user clicks on "Global Service Summary" again in interface 201, interface 209 is displayed. Other cases are similar and will not be elaborated further.

[0065] As mentioned above, there may also be only one summary message, assuming it is the first summary message, which includes the aforementioned "Global Service Summary" and "Global Message Summary". In this case, in response to the user clicking on the first summary message in the first desktop interface, a first display interface is displayed. The first display interface includes a message summary column for each message in at least one pending message indicated by the first summary message. Furthermore, in this case, it is not necessary to distinguish between the message summary column and the transaction summary column.

[0066] Figure 5 is a schematic interactive diagram of a desktop sub-screen according to an embodiment of this application. A desktop sub-screen can be understood as other desktop interfaces besides the main desktop screen. Each desktop sub-screen corresponds to an application type and is used to display the icons of all applications in the cards of that application type, as well as to manage the application icons under that application type. In essence, desktop sub-screens are used for categorizing and managing desktop icons.

[0067] When a user swipes away the "Frequently Used" application card in interface 201, that is, performs a swipe operation in the card stacking area of ​​interface 201, the electronic device responds to the swipe operation and displays interface 205. Interface 205 is still the home screen, but the card displayed on the top layer of the card stacking area changes from "Frequently Used" to "Work". In other words, the "Frequently Used" card displayed on the top layer of the card stacking area in interface 201 is removed, and the new card displayed on the top layer is "Work".

[0068] In one example, the "Frequently Used" card can be deleted after a swipe. In another example, the "Frequently Used" card can be moved to the bottom after a swipe, making it the bottom layer of the card stack, so that the user can bring the "Frequently Used" card back to the top after multiple swipes or swiping in the opposite direction.

[0069] When the user clicks the "Work" card displayed at the top of interface 205, the electronic device displays interface 206. Interface 206 includes an application type bar (which can be considered a top bar), a card display area, and an application icon display area. The application type bar displays the application types and distinguishes the application type of the current desktop sub-screen from other application types. This distinction is achieved by using a bolder and larger font for the application type of the current screen compared to other application types.

[0070] Interface 206 also includes a summary of the current screen. The summary of the current screen shows a different number of items compared to the global service summary and global message summary in interface 201, because the summary displayed for the current screen only includes the message / transaction summaries generated by each application within the current screen. However, it should be understood that the summary for the current screen can be omitted, meaning that interface 206 may not include the summary for the current screen.

[0071] In one possible implementation, the electronic device receives a summary operation from the user on the current screen of interface 206 (e.g., a combination of one or more of the operations such as clicking, swiping, and double-clicking). In response to the user's operation, the electronic device can display the message content in the form of a pop-up window. For details, please refer to the embodiment shown in Figures 2-4, where the user clicks on the global information summary area of ​​the first screen.

[0072] The cards displayed in the card display area are the cards clicked by the user in interface 205. The application icon display area is used to display all application icons under this card (application type). When there are too many application icons to be displayed completely in the application icon display area of ​​interface 206, the user can scroll to view other application icons, as shown in interface 207. That is to say, when the user performs a scrolling operation in interface 206, application icons that were not previously displayed are displayed in response to this operation in this desktop sub-screen.

[0073] When users want to manage the application icons contained in any application type or the application icons displayed in the cards of that application type, they can do so by entering the editing interface of the desktop sub-screen corresponding to that application type. This will be explained in conjunction with Figure 6 below.

[0074] Figure 6 is a schematic diagram of the editing interface of a desktop sub-screen according to an embodiment of this application. Figure 6 takes the editing of the desktop sub-screen corresponding to the "Frequently Used" application type as an example. As shown in Figure 6, when the user performs a two-finger pinch operation on interface 210, the electronic device displays interface 211 in response to the two-finger pinch operation. Interface 211 is an example of the editing interface of the desktop sub-screen. Figure 6 shows how to add, delete, or adjust the order of icons displayed in cards, as well as how to add, delete, or adjust the order of icons under application types, by dragging and dropping.

[0075] It should be understood that, in addition to the two-finger pinch operation mentioned above, another way to enter the editing interface is to set a control in interface 210 for entering the editing interface, and then enter the editing interface by clicking the control.

[0076] Users can change the name of the application type by clicking or double-clicking the application type in interface 211.

[0077] As shown in interface 211, the example card for the application type "Frequently Used" displays six existing icons, and the alternative application icon display area below the card shows icons for applications not listed on the card. Users can manage application icons under this application type by pressing and dragging.

[0078] When the user presses and holds icon A, which is not in the card, on interface 211 and drags it into the card, interface 212 is displayed in response to this press and drag operation. In interface 212, icon A is added to the card, and icon A is removed from the list of candidate application icons.

[0079] When a user presses and holds icon B in the card in interface 212 and drags it to the alternative application icon display area, interface 213 is displayed in response to the press and drag operation of icon B. In interface 213, icon B is no longer included in the card, but icon B is added to the alternative application icon display area.

[0080] Users can also adjust the order of icons in the card by dragging and dropping, which will not be elaborated further.

[0081] It should be noted that Figure 6 is presented as an example where the number of applications in the card is less than its maximum, and the number of alternative applications is also less than its maximum, for ease of understanding the actual changes after dragging the icons. In practice, it is common for an application type to contain more icons than the card can display. In this case, the first few icons in the card that can be displayed can be shown. Taking interface 210 as an example, assuming there are 10 icons in the frequently used type and the card can display a maximum of 8, the first 8 icons in the card can be displayed, and the other icons can be viewed after expanding the card.

[0082] It should also be understood that both interfaces 206 and 210 have an icon display area below the card display area. However, the application icon display area in interface 206 displays the application icon corresponding to the card, that is, the application icon under the application type corresponding to the card; while the alternative application icon display area in interface 210 displays alternative application icons, that is, application icons that do not belong to the card, or application icons that do not belong to the application type corresponding to the card.

[0083] Figure 7 is a schematic interactive diagram illustrating the selection of a desktop style according to an embodiment of this application. As shown in Figure 7, interface 220 represents a desktop layout under the traditional desktop style, which can also be considered as standard style, ordinary style, regular style, standard desktop layout, ordinary desktop layout, regular desktop layout, traditional desktop layout, etc. When the user clicks the icon of the settings application in interface 220, the electronic device responds to the click operation, launches the settings application, and displays the running interface 221 of the settings application. As shown in interface 221, some services or settings items in the settings application are available for user selection. When the user clicks "Desktop and Personalization" in interface 221, that is, clicks the control corresponding to desktop management, in response to the click operation, interface 222 is displayed on the electronic device. Interface 222 is a management interface related to desktop management, and includes some settings items. Users can adjust the desktop settings of the electronic device by clicking different settings items. As shown in interface 222, the current desktop style of the electronic device is the standard style. When the user clicks the desktop style section in interface 222, in response to the click operation, interface 223 is displayed on the electronic device. As shown in interface 223, the desktop style includes multiple styles. The desktop layout scheme described in this application corresponds to the smart style, which is in an unselected state, while the standard style is in a selected state. When the user clicks the checkbox corresponding to the smart style in interface 223, the smart style will be updated to the selected state, while the standard style will be updated to the unselected state.

[0084] It should be understood that interface 223 provides three examples: standard style, smart style, and drawer style. However, in practice, only two of these styles may exist, and the styles may be named differently. There are no restrictions, as long as it can support users in choosing between the new desktop layout scheme and the traditional desktop layout scheme provided in this application.

[0085] It should also be understood that Figure 7 only shows an example of switching from the standard style to the smart style, but the interaction process of switching from the smart style to the standard style, as well as switching from any of the three desktop styles to other styles, is similar, so it will not be described again.

[0086] Figure 8 is a schematic flowchart of a desktop layout method according to an embodiment of this application. The steps in Figure 8 will be described below.

[0087] S801, in response to the operation of launching the desktop, displays the first desktop interface on the electronic device.

[0088] The first desktop interface includes a first summary message and a card stacking area. The card stacking area is used to display at least one card, each card corresponding to an application category, and each card includes an icon of at least one application. The first summary message is used to indicate at least one pending message generated in the electronic device before the desktop is launched. Interface 201 can be seen as an example of the first desktop interface. The global message summary in interface 201 can be seen as an example of the first summary message.

[0089] It should be noted that the steps in Figure 8 can be executed each time the desktop is started to manage messages and / or transactions. Therefore, when the desktop is started, the messages and / or transactions generated before the desktop was started are managed.

[0090] In some cases, when the first summary message can also include summaries of all transactions and messages, the combination of the global message summary and the global service summary in interface 201 can be regarded as an example of the first summary message.

[0091] In the global message summary in interface 201, "+12" represents the total number of pending messages, which is an example of at least one pending message mentioned above, and the number is 12.

[0092] The first summary message and the second summary message below can be obtained by processing messages received by the electronic device and / or information generated by applications or services on the electronic device using large models or neural network models.

[0093] In one example, a large model can be used to summarize the messages received by the electronic device, remove redundant information, extract the central idea, and obtain at least one message summary column. A first summary message is then generated based on all message summary columns prior to the desktop launch operation. Therefore, in this embodiment, the message content in each message summary column is presented in a concise, meaningful way, allowing users to quickly obtain key information from the received messages.

[0094] In one implementation, the first summary message is displayed in the form of a capsule on the first desktop interface.

[0095] As mentioned above, electronic devices may include a variety of desktop styles, and the desktop layout scheme provided in this application corresponds to one of these desktop styles. Therefore, after the desktop startup operation occurs, the user may enter the first desktop interface of the desktop layout scheme provided in this application, or they may enter the desktop interface of other desktop styles.

[0096] In one implementation, step S801 may include: when the desktop style of the electronic device is a smart style, displaying a first desktop interface on the electronic device in response to the desktop startup operation; or, when the desktop style of the electronic device is not a smart style, displaying a desktop interface corresponding to the current desktop style on the electronic device in response to the desktop startup operation. In this implementation, the first desktop interface is only accessed when the desktop style is smart, while other styles of desktop interfaces are displayed when the desktop style is not smart. Therefore, elements such as the first summary message and card stacking area in the first desktop interface will not be displayed, and the subsequent steps will not be executed. This implementation provides an example of coexistence between the newly created desktop style (desktop layout scheme) and the existing desktop style.

[0097] S802, In response to the user's click operation on the first summary message, a first display interface is displayed on the electronic device.

[0098] The first display interface includes a message summary bar for each message in at least one pending message. Interface 202 can be considered an example of the first display interface. In some cases, interface 209 can also be considered an example of the first display interface.

[0099] In one implementation, the first display interface can be displayed as a pop-up window within the first desktop interface, as shown in interfaces 202 and 209. However, it should be understood that, in addition to being displayed as a pop-up window, the first display interface can also be a regular display interface (ordinary display interface), covering the entire screen display area, rather than a small window display like a pop-up window. In this case, the pop-up window display format allows users to quickly return to the first desktop interface according to the pop-up window's display logic.

[0100] It should also be understood that, in the embodiments of this application, in order to distinguish between the desktop interface belonging to the desktop layout (desktop style) and other interfaces, the terms "desktop interface" and "display interface" are used respectively. The first desktop interface (desktop first screen), the second desktop interface (desktop sub-screen corresponding to a certain application type), and the third desktop interface (desktop sub-screen corresponding to another application type) are all desktop interfaces.

[0101] It should be noted that one message summary bar can correspond to at least one pending message, and one pending message can correspond to only one message summary bar. As shown in interface 203, the meanings of two messages are summarized in the same message summary bar.

[0102] S803, In response to the user's click operation on the message summary bar of the first pending message, launch the first application.

[0103] The first pending message is any one of at least one pending message, and the first application is the application corresponding to the first pending message. The message summary bar clicked by the user in interface 202 can be regarded as an example of the message summary bar of the first pending message, the target application shown in interface 203 can be regarded as an example of the first application, and either of the two messages in interface 203 can be regarded as an example of the first pending message.

[0104] In one implementation, when launching the first application, the method further includes: displaying the running interface of the first application in a pop-up window on the first display screen; and managing the first pending message in response to the user's management operation on the running interface of the first application. In this implementation, by directly launching and displaying the first application, users can manage messages directly within the first application without needing to exit the desktop and re-find and launch the first application, thus facilitating subsequent user operations. The pop-up window display also makes it easy for users to know that the first display screen is still displayed at the bottom of the pop-up window, allowing them to quickly return to the first display screen according to the pop-up window's display logic.

[0105] However, it should be understood that the application's running interface can also be displayed in a normal interface instead of as a pop-up.

[0106] In another example, the above method further includes: returning to display the first display interface in response to a user's click operation outside the pop-up window in the first display interface; or, returning to display the first display interface in response to a user's swipe operation in the first application running interface.

[0107] In another implementation, the method further includes: in response to a user's click on the message summary bar of the first pending message, displaying at least one associated icon in a pop-up window on the first display interface. The at least one associated icon includes the icon of at least one application associated with the first pending message and / or the icon of at least one service associated with the first pending message. In this implementation, associated icons are also provided to facilitate user access to relevant applications; the associated icons shown in interface 203 can be considered an example of this implementation.

[0108] In one example, the method further includes: responding to a user's click on any one of the at least one associated icon, launching and displaying the running interface of the application or service corresponding to the clicked icon. In this example, when a user clicks any associated icon, they can enter the application corresponding to that icon without having to exit the current interface and then launch the associated application, thus improving the user experience.

[0109] In another implementation, the first desktop interface further includes a second summary message, which indicates at least one pending transaction. The method further includes: in response to a user's click on the second summary message, displaying a second display interface on the electronic device, where at least one transaction summary bar is displayed, each corresponding to a pending transaction; and in response to a user's click on a first transaction summary bar, launching and displaying the running interface of the application or service corresponding to the first transaction summary bar in a pop-up window on the second display interface, where the first transaction summary bar is any one of the at least one transaction summary bar. This implementation provides a management process for pending transactions, allowing users to quickly access and process the corresponding application or service by viewing and clicking on the summaries of pending transactions.

[0110] The global service summary in interface 201 can be seen as an example of the second summary message.

[0111] A global service summary can be obtained by aggregating the recommended services obtained from the smart service recommendation function of electronic devices. The smart service recommendation function mainly combines geofencing information and current electronic device usage behavior information to obtain services that meet the user's expectations and recommends them to the user on the electronic device.

[0112] Interface 204 can be seen as an example of a second display interface, the transaction summary column in interface 204 can be seen as an example of at least one transaction summary column, and any transaction summary column in interface 204 can be seen as an example of a first transaction summary column.

[0113] In some implementations, interface 209 can also be seen as an example of a second display interface.

[0114] It should be understood that, as mentioned above, messages and transactions may not be distinguished. In this case, the second summary message can be regarded as being included in the first summary message.

[0115] In one implementation, the method further includes: in response to a user's click on the first transaction summary bar, displaying at least one associated icon in a pop-up window on the second display interface. The at least one associated icon includes an icon for at least one application and / or service associated with the first transaction summary bar. In this implementation, displaying the associated icon facilitates the user's use of the associated application or service.

[0116] In one example, the method further includes: responding to a user's click on any one of the at least one associated icon, launching and displaying the running interface of the application or service corresponding to the clicked icon. In this example, the user can quickly enter the associated application or service by clicking the associated icon, without having to exit the current interface and then launch the associated application or icon, which is more convenient.

[0117] In one implementation, the second display interface is shown as a pop-up window within the first desktop interface. However, it should be understood that besides being displayed as a pop-up window, the second display interface can also be a regular display interface, rather than a pop-up window. The pop-up window format allows users to quickly return to the first desktop interface according to the pop-up window's display logic.

[0118] S804, in response to the user's click on the first card, displays the second desktop interface.

[0119] The second desktop interface includes an application type bar, a card display area, and an application icon display area. The application type bar includes the application type corresponding to the first card, the card display area includes the first card, and the application icon display area displays the icons of all applications in the first card; the first card is a card in the card stacking area. Interface 206 can be seen as an example of the second desktop interface.

[0120] In one possible implementation, the first card is the topmost card in the card stack area.

[0121] In this step, users can enter the corresponding desktop sub-screen by clicking the card. Since the maximum number of icons that a card can display is limited, there may be situations where not all applications under this application type can be displayed on the card. In this case, users can enter the desktop sub-screen by clicking the card to further view or manage the application icons under this application type.

[0122] In one implementation, the method further includes: responding to a user's click on the first icon in the first card of the card stack area, launching and displaying the running interface of the application or service corresponding to the first icon. In this implementation, application icons are presented to the user in the form of cards according to their type, allowing the user to directly access the application by clicking any icon in the card, which is convenient and quick. For example, the "Frequently Used" card in the card stack area of ​​interface 201 can be considered an example of the first card; the user can directly access the application by clicking any application icon in the "Frequently Used" card of interface 201.

[0123] In one implementation, the method further includes: responding to a user's click on any application icon in the application icon display area, launching the application and displaying its running interface. In this implementation, users can enter the corresponding application by clicking on an icon in the application icon display area. If the application the user wants to launch is not in the card display area, they can find and launch it following the steps in this example.

[0124] In another implementation, the method further includes: in response to a user's swipe operation in the application icon display area, displaying the application icon that was not displayed on the second desktop interface before the swipe operation. When there are too many application icons under an application type, users can swipe to view other application icons that are not displayed on the screen. Interfaces 206-207 can be seen as examples of the operation process in this example.

[0125] In one implementation, the method further includes: responding to a first operation by the user on the second desktop interface, displaying a third desktop interface. The third desktop interface includes an application type bar, a card display area, and an application icon display area. The application type bar includes the application type corresponding to the second card, the card display area includes the second card, and the application icon display area displays icons for all applications in the second card. In other words, the user can switch to a desktop sub-screen corresponding to another application type using the first operation. For example, if interface 206 corresponds to the first card and interface 210 corresponds to the second card, the user can switch to interface 210 from interface 206 using the first operation.

[0126] In one example, the first operation is either a horizontal swipe on the second desktop interface or a click on the application type corresponding to the second card in the application type bar on the second desktop interface. This example provides a demonstration of the first operation for switching desktop sub-screens. Referring to interface 206, this could involve a left swipe on interface 206 to switch desktop sub-screens, or directly clicking on other application types in the application type bar. Other cases will not be listed individually.

[0127] In one implementation, when the first card is the topmost card in the card stacking area, the method further includes: in response to a user's swipe operation on the first card, displaying the first card stacked below the first card on the top layer of the card stacking area. In this implementation, the topmost card can be changed via a swipe operation. The operations of interfaces 201-205 shown in Figure 5 can be seen as an example of this process.

[0128] In one example, the method further includes: in response to a user's swipe gesture on the first card, displaying the first card at the bottom of the card stacking area. In this example, instead of deleting the first card, which would otherwise be displayed on top, it is displayed at the bottom (i.e., the last) of the stacking area to prevent the user from accidentally deleting the first card and being unable to find the application from the first card.

[0129] In one implementation, the method further includes: displaying an editing interface for the second desktop interface in response to a second user operation on the second desktop interface; and managing application icons corresponding to the second desktop interface in response to a third user operation on the editing interface, wherein the third operation includes at least one of the following: adding application icons to the application type corresponding to the second desktop interface, deleting application icons from the application type corresponding to the second desktop interface, adjusting the display icons in the card corresponding to the second desktop interface, and adding, deleting, or modifying the application type name in the application type column of the interface. This implementation provides a method for editing desktop sub-screens. The process shown in Figure 6 can be considered an example of this implementation.

[0130] In one example, the second action is a two-finger pinch gesture on the second desktop interface. However, it should be understood that it could also be another action, such as clicking on the corresponding control, to enter the editing interface.

[0131] The method shown in Figure 8 primarily changes the traditional desktop layout by summarizing and displaying messages from before the electronic device is opened, allowing users to process messages more efficiently and quickly. By focusing on the messages that need processing, it guides users to decide how to proceed based on the summarized information, eliminating the need to check each application individually for messages as in traditional solutions. This avoids the tedious steps of opening each application to view messages and locking onto those requiring management. Because the summary messages in this application aggregate messages that meet user management expectations, it allows for quick identification and further management of the messages that need attention. The card stacking area categorizes applications by type and presents them in a stacked manner, allowing users to quickly launch the corresponding application by clicking the application icon in the top-level card, and to access the corresponding desktop sub-screen for further interaction by clicking the top-level card.

[0132] It should be understood that traditional solutions require first finding the application, then opening the target application, and then finding the message. This process needs to be repeated repeatedly to process all the messages. The solution in this application, however, first aggregates all messages, then allows users to select the message they want to process based on their needs. With a simple click, the corresponding application or service can be opened, thus achieving convenient message processing.

[0133] The methods of the embodiments of this application have been described above with reference to the accompanying drawings. It should be understood that although the steps in the flowcharts of the embodiments described above are shown sequentially, these steps are not necessarily executed in the order shown in the figures. Unless explicitly stated herein, there is no strict order restriction on the execution of these steps, and they can be executed in other orders. Moreover, at least some steps in the flowcharts of the embodiments described above may include multiple steps or multiple stages. These steps or stages are not necessarily completed at the same time, but can be executed at different times. The execution order of these steps or stages is not necessarily sequential, but can be performed alternately or in turn with other steps or at least a portion of the steps or stages of other steps. The apparatus of the embodiments of this application will now be described with reference to the accompanying drawings.

[0134] Figure 9 is a schematic diagram of the hardware structure of an electronic device according to an embodiment of this application. As shown in Figure 9, the electronic device 900 may include a processor 910, an external memory interface 920, an internal memory 921, a sensor module 980, buttons 990, a camera 993, a display screen 994, etc. The sensor module 980 may include a pressure sensor 980A, a fingerprint sensor 980H, a touch sensor 980K, etc.

[0135] It is understood that the structures illustrated in the embodiments of this application do not constitute a specific limitation on the electronic device 900. In other embodiments of this application, the electronic device 900 may include more or fewer components than illustrated, or combine some components, or split some components, or have different component arrangements. The illustrated components may be implemented in hardware, software, or a combination of software and hardware.

[0136] For example, the processor 910 shown in FIG9 may include one or more processing units, such as an application processor (AP), a modem processor, a graphics processing unit (GPU), an image signal processor (ISP), a controller, a memory, a video codec, a digital signal processor (DSP), a baseband processor, and / or a neural network processing unit (NPU). The different processing units may be independent devices or integrated into one or more processors.

[0137] The controller can be the nerve center and command center of the electronic device 900. The controller can generate operation control signals based on the instruction opcode and timing signals to control the fetching and execution of instructions.

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

[0139] Electronic device 900 implements display functions through a GPU, a display screen 994, and an application processor. The GPU is a microprocessor for image processing, connecting the display screen 994 and the application processor. The GPU is used to perform mathematical and geometric calculations and for graphics rendering. Processor 910 may include one or more GPUs, which execute program instructions to generate or modify display messages.

[0140] The display screen 994 is used to display images, videos, etc. The display screen 994 includes a display panel. In some embodiments, the electronic device 900 may include one or N display screens 994, where N is a positive integer greater than 1.

[0141] Electronic device 900 can achieve shooting function through ISP, camera 993, video codec, GPU, display 994 and application processor.

[0142] The camera 993 is used to capture still images or videos. In some embodiments, the electronic device 900 may include one or N cameras 993, where N is a positive integer greater than 1.

[0143] An NPU (Neural Processing Unit) is a computational processor for neural networks (NNs). By borrowing the structure of biological neural networks, such as the transmission patterns between neurons in the human brain, it can quickly process input messages and continuously learn on its own. NPUs can enable intelligent cognitive applications in electronic devices, such as image recognition, facial recognition, speech recognition, and text understanding.

[0144] The external storage interface 920 can be used to connect an external memory card, such as a secure digital (SD) card, to expand the storage capacity of the electronic device 900. The external memory card communicates with the processor 910 through the external storage interface 920 to perform data storage functions. For example, music, video, and other files can be saved on the external memory card.

[0145] Internal memory 921 can be used to store computer executable program code, which includes instructions. Processor 910 executes various functional applications and data processing of electronic device 900 by running the instructions stored in internal memory 921. Internal memory 921 may include a program storage area and a data storage area. The program storage area may store the operating system, at least one application program required for a function (such as sound playback, image playback, etc.), etc. The data storage area may store data created during the use of electronic device 900 (such as audio data, phonebook, etc.). Furthermore, internal memory 921 may include high-speed random access memory and may also include non-volatile memory, such as at least one disk storage device, flash memory device, universal flash storage (UFS), etc.

[0146] Pressure sensor 980A is used to sense pressure signals and convert them into electrical signals. In some embodiments, pressure sensor 980A can be disposed on display screen 994. There are many types of pressure sensors 980A, such as resistive pressure sensors, inductive pressure sensors, and capacitive pressure sensors. A capacitive pressure sensor may include at least two parallel plates with conductive material. When force is applied to pressure sensor 980A, the capacitance between the electrodes changes. Electronic device 900 determines the pressure intensity based on the change in capacitance. When a touch operation is applied to display screen 994, electronic device 900 detects the intensity of the touch operation based on pressure sensor 980A. Electronic device 900 can also calculate the touch position based on the detection signal from pressure sensor 980A. In some embodiments, touch operations applied to the same touch position but with different touch operation intensities can correspond to different operation commands. For example, when a touch operation with an intensity less than a first pressure threshold is applied to the SMS application icon, a command to view an SMS is executed. When a touch operation with an intensity greater than or equal to the first pressure threshold is applied to the SMS application icon, a command to create a new SMS is executed.

[0147] The fingerprint sensor 980H is used to collect fingerprints. The electronic device 900 can utilize the characteristics of the collected fingerprints to achieve fingerprint unlocking, accessing application locks, taking photos with fingerprints, answering calls with fingerprints, etc.

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

[0149] Buttons 990 include a power button, volume buttons, etc. Buttons 990 can be mechanical buttons or touch-sensitive buttons. Electronic device 900 can receive button input and generate key signal inputs related to user settings and function control of electronic device 900.

[0150] It should be noted that the message interaction and execution process between the above-mentioned devices / units are based on the same concept as the method embodiments of this application. For details on their specific functions and technical effects, please refer to the method embodiments section, and they will not be repeated here.

[0151] Those skilled in the art will clearly understand that, for the sake of convenience and brevity, the above-described division of functional units and modules is merely an example. In practical applications, the above functions can be assigned to different functional units and modules as needed, that is, the internal structure of the device can be divided into different functional units or modules to complete all or part of the functions described above. The functional units and modules in the embodiments can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit. The integrated unit can be implemented in hardware or as a software functional unit. Furthermore, the specific names of the functional units and modules are only for easy differentiation and are not intended to limit the scope of protection of this application. The specific working process of the units and modules in the above system can be referred to the corresponding process in the foregoing method embodiments, and will not be repeated here.

[0152] This application also provides an electronic device, which includes: one or more processors and a memory; the memory is coupled to the one or more processors, and the memory is used to store computer program code, the computer program code including computer instructions, wherein the one or more processors call the computer instructions to cause the electronic device to perform the steps of any of the above methods.

[0153] This application also provides a computer-readable storage medium including instructions that, when executed on an electronic device, cause the electronic device to perform the steps of any of the above methods.

[0154] This application provides a computer program product, which includes a computer program that, when run on an electronic device, causes the electronic device to perform the steps of any of the above methods.

[0155] If the integrated unit is implemented as a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, all or part of the processes in the methods of the above embodiments of this application can be implemented by a computer program instructing related hardware. The computer program can be stored in a computer-readable storage medium, and when executed by a processor, it can implement the steps of the various method embodiments described above. The computer program includes computer program code, which can be in the form of source code, object code, executable files, or certain intermediate forms. The computer-readable medium can include at least: any entity or device capable of carrying computer program code to a photographic device / electronic device, a recording medium, a computer memory, a read-only memory (ROM), a random access memory (RAM), an electrical carrier signal, a telecommunication signal, and a software distribution medium. Examples include USB flash drives, portable hard drives, magnetic disks, or optical disks. In some jurisdictions, according to legislation and patent practice, computer-readable media cannot be electrical carrier signals or telecommunication signals.

[0156] In the above embodiments, the descriptions of each embodiment have different focuses. For parts that are not described in detail or recorded in a certain embodiment, please refer to the relevant descriptions of other embodiments.

[0157] Those skilled in the art will recognize that the units 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.

[0158] In the embodiments provided in this application, it should be understood that the disclosed apparatus / devices and methods can be implemented in other ways. For example, the apparatus / device embodiments described above are merely illustrative. For instance, the division of modules or units is only a logical functional division, and in actual implementation, there may be other division methods. For example, multiple units or components may be combined or integrated into another system, 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 apparatuses or units may be electrical, mechanical, or other forms.

[0159] The units described as separate components may or may not be physically separate. The components shown as units may or may not be physical units; that is, they may be located in one place or distributed across multiple network units. Some or all of the units can be selected to achieve the purpose of this embodiment according to actual needs.

[0160] It should be understood that, when used in this application specification and the appended claims, the term "comprising" indicates the presence of the described features, integrals, steps, operations, elements and / or components, but does not exclude the presence or addition of one or more other features, integrals, steps, operations, elements, components and / or a collection thereof.

[0161] It should also be understood that the term “and / or” as used in this application specification and the appended claims means any combination of one or more of the associated listed items and all possible combinations, and includes such combinations.

[0162] As used in this application specification and the appended claims, the term "if" may be interpreted, depending on the context, as "when," "once," "in response to determination," or "in response to detection."

[0163] Furthermore, in the description of this application and the appended claims, the terms "first," "second," "third," etc., are used only to distinguish descriptions and should not be construed as indicating or implying relative importance.

[0164] References to "one embodiment" or "some embodiments" as described 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.

[0165] The above-described embodiments are only used to illustrate the technical solutions of this application, and are not intended to limit them. Although this application has been described in detail with reference to the foregoing embodiments, those skilled in the art should understand that modifications can still be made to the technical solutions described in the foregoing embodiments, or equivalent substitutions can be made to some of the technical features. Such modifications or substitutions do not cause the essence of the corresponding technical solutions to deviate from the spirit and scope of the technical solutions of the embodiments of this application, and should all be included within the protection scope of this application.

Claims

1. A method for desktop layout, characterized in that, include: In response to the operation of launching the desktop, a first desktop interface is displayed on the electronic device. The first desktop interface includes a first summary message and a card stacking area. The card stacking area is used to stack and display at least one card, each card corresponding to an application category, and each card includes an icon of at least one application. The first summary message is used to indicate at least one pending message generated in the electronic device prior to the operation of launching the desktop; In response to a user's click on the first summary message, a first display interface is displayed on the electronic device, the first display interface including a message summary bar for each of the at least one message to be processed; In response to the user's click operation on the message summary bar of the first pending message, the first application is launched, wherein the first pending message is any one of the at least one pending messages, and the first application is the application corresponding to the first pending message; In response to a user's click on the first card, a second desktop interface is displayed. The second desktop interface includes an application type bar, a card display area, and an application icon display area. The application type bar includes the application type corresponding to the first card, the card display area includes the first card, and the application icon display area is used to display the icons of all applications in the first card. The first card is a card in the card stacking area.

2. The method according to claim 1, characterized in that, When launching the first application, the method further includes: The running interface of the first application is displayed in the form of a pop-up window in the first display interface; In response to the user's management operation on the first message to be processed in the running interface of the first application, the first message to be processed is managed.

3. The method according to claim 1 or 2, characterized in that, The method further includes: In response to a user's click on the message summary bar of the first pending message, at least one associated icon is displayed in the first display interface as a pop-up window. The at least one associated icon includes the icon of at least one application associated with the first pending message and / or the icon of at least one service associated with the first pending message.

4. The method according to claim 3, characterized in that, The method further includes: In response to a user's click on any one of the at least one associated icons, the application or service interface corresponding to the clicked icon is launched and displayed.

5. The method according to any one of claims 1 to 4, characterized in that, The first display interface is displayed as a pop-up window within the first desktop interface.

6. The method according to any one of claims 1 to 5, characterized in that, The first desktop interface also includes a second summary message, which indicates at least one pending transaction; the method further includes: In response to a user's click on the second summary message, a second display interface is displayed on the electronic device. The second display interface displays at least one transaction summary column, and each transaction summary column corresponds to a pending transaction. In response to the user's click on the first transaction summary bar, the running interface of the application or service corresponding to the first transaction summary bar is launched and displayed in the second display interface as a pop-up window. The first transaction summary bar is any one of the at least one transaction summary bar.

7. The method according to claim 6, characterized in that, The method further includes: In response to a user's click on the first transaction summary bar, at least one associated icon is displayed in the second display interface as a pop-up window. The at least one associated icon includes an icon of at least one application and / or service associated with the first transaction summary bar.

8. The method according to claim 7, characterized in that, The method further includes: In response to a user's click on any one of the at least one associated icons, the application or service interface corresponding to the clicked icon is launched and displayed.

9. The method according to any one of claims 5 to 8, characterized in that, The second display interface is displayed in the form of a pop-up window on the first desktop interface.

10. The method according to any one of claims 1 to 9, characterized in that, The method further includes: In response to a user's click on the first icon in the first card of the card stacking area, the running interface of the application or service corresponding to the first icon is launched and displayed.

11. The method according to any one of claims 1 to 10, characterized in that, The method further includes: In response to a user clicking on any application icon in the application icon display area, the application is launched and its running interface is displayed.

12. The method according to any one of claims 1 to 10, characterized in that, The method further includes: In response to a user's swipe operation in the application icon display area, the application icon that was not displayed on the second desktop interface before the swipe operation is displayed on the second desktop interface.

13. The method according to any one of claims 1 to 10, characterized in that, The method further includes: In response to a user's first operation on the second desktop interface, a third desktop interface is displayed. The third desktop interface includes an application type bar, a card display area, and an application icon display area. The application type bar includes the application type corresponding to the second card, the card display area includes the second card, and the application icon display area is used to display the icons of all applications in the second card.

14. The method according to claim 13, characterized in that, The first operation is a horizontal swipe operation on the second desktop interface, or a click operation on the application type corresponding to the second card in the application type bar on the second desktop interface.

15. The method according to any one of claims 1 to 14, characterized in that, The first card is the topmost card in the card stacking area, and the method further includes: In response to the user's swipe gesture on the first card, the first card stacked below the first card is displayed on the top layer of the card stacking area.

16. The method according to claim 15, characterized in that, The method further includes: In response to the user's swipe gesture on the first card, the first card is displayed on the bottom layer of the card stacking area.

17. The method according to any one of claims 1 to 16, characterized in that, The method further includes: In response to a second operation by the user on the second desktop interface, the editing interface of the second desktop interface is displayed; In response to a third operation performed by the user in the editing interface of the second desktop interface, the application icons corresponding to the second desktop interface are managed. The third operation includes at least one of the following: adding an application icon to the card display area or application icon display area of ​​the second desktop interface, deleting an application icon from the card display area or application icon display area of ​​the second desktop interface, and adding, deleting or modifying the application type name in the application type bar of the interface.

18. The method according to claim 17, characterized in that, The second operation is a two-finger pinch operation on the second desktop interface.

19. The method according to any one of claims 1 to 18, characterized in that, The operation of displaying a first desktop interface on an electronic device in response to launching a desktop includes: When the desktop style of the electronic device is set to smart style, in response to the launch desktop operation, the first desktop interface is displayed on the electronic device; or... When the desktop style of the electronic device is not the smart style, in response to the operation of launching the desktop, the desktop interface corresponding to the current desktop style is displayed on the electronic device.

20. An electronic device, characterized in that, The electronic device includes: one or more processors, and memory; The memory is coupled to the one or more processors, the memory being used to store computer program code, the computer program code including computer instructions, the one or more processors invoking the computer instructions to cause the electronic device to perform the method as described in any one of claims 1 to 19.

21. A chip system, characterized in that, The chip system is applied to an electronic device, the chip system including one or more processors, the one or more processors being used to invoke computer instructions to cause the electronic device to perform the method as described in any one of claims 1 to 19.

22. A computer-readable storage medium, characterized in that, The computer-readable storage medium includes instructions that, when executed on an electronic device, cause the electronic device to perform the method as described in any one of claims 1 to 19.

Images