Shortcut icon display method and electronic equipment

Abstract

The invention discloses a shortcut icon display method and electronic equipment, and relates to the technical field of terminals. The method comprises the steps that a first interface is displayed, and the first interface comprises a first desktop icon of a target application; and starting the target application in response to a click operation on the first desktop icon at the first moment. And at a second moment, the target application is updated, and the second moment is after the first moment. After the target application is updated, a second interface is displayed, and the second interface comprises a second desktop icon of the target application. At a third moment, in response to a first operation on the second desktop icon, displaying a first shortcut icon of the target application; the click operation on the second desktop icon is not received between the second moment and the third moment, and the first shortcut icon corresponds to the first shortcut of the target application. Therefore, after the target application is updated and before the target application is clicked and started after the updating, the shortcut icon of the target application can be correctly displayed, and the man-machine interaction experience is improved.

Description

Technical Field

[0001] The embodiments of the present application relate to the field of terminal technology, and in particular to a method for displaying a shortcut icon and an electronic device. Background Art

[0002] Electronic devices like mobile phones and tablets often support long-pressing desktop icons to provide shortcuts. For example, in response to a user clicking a chat app on a mobile phone, shortcuts like "Start Chat," "Add Friend," and "Scan" can be displayed on the desktop. This allows the electronic device to provide quick access to various sub-functions of the application, allowing users to directly access the corresponding sub-functions.

[0003] Furthermore, when providing a shortcut, the electronic device may also display a shortcut icon (referred to as a shortcut icon) to vividly illustrate the function of the shortcut.

[0004] However, after an application is updated, after a long press operation is performed on the desktop icon of the application, the electronic device may not display the shortcut icon correctly, such as displaying an incorrect shortcut icon or not displaying the shortcut icon. Summary of the Invention

[0005] The present application provides a method for displaying a shortcut icon and an electronic device, which can correctly display the shortcut icon even after the application is updated, thereby improving the human-computer interaction experience.

[0006] To achieve the above objectives, this application adopts the following technical solutions:

[0007] In a first aspect, a method for displaying shortcut icons is provided. The method comprises: displaying a first interface, such as interface 401 below, including a first desktop icon for a target application, such as desktop icon 4011 in interface 401. At a first moment, in response to a click on the first desktop icon, the target application is launched, as illustrated by the process from interface 401 to interface 402. At a second moment, the target application is updated, the second moment occurring after the first moment. After the target application is updated, a second interface, such as interface 501 below, is displayed, including a second desktop icon for the target application, such as desktop icon 5011 in interface 501. At a third moment, in response to a first operation on the second desktop icon, a first shortcut icon for the target application is displayed, the first shortcut icon corresponding to the first shortcut of the target application, as illustrated by the process from interface 501 to interface 502. The first shortcut may be any of the shortcuts in interface 502, such as "Scan," "Add Friend," "Start Chat," or "Pay." The third moment is after the second moment, and no click operation on the second desktop icon is received between the second moment and the third moment, that is, the target application has not been clicked to start after the target application is updated.

[0008] To sum up, by using this application, the shortcut icon can be correctly displayed after the application is updated and before it is clicked to start, thereby improving the human-computer interaction experience.

[0009] In a possible design of the first aspect, the first operation includes: a long press operation, as shown in Scenario 1 below; or a long press and drag operation of the border of the second desktop icon, as shown in Scenario 2 below.

[0010] That is to say, in various scenarios where the shortcut display is triggered, the shortcut icon can be guaranteed to be displayed correctly.

[0011] In a possible design of the first aspect, the first shortcut icon corresponds to the first shortcut of the target application before the update, such as the "Scan" icon in interface 502 is the same as the "Scan" icon in interface 404 before the update.

[0012] In one possible design of the first aspect, at a third moment, after displaying the first shortcut icon of the target application in response to the first operation on the second desktop icon, the method further includes: displaying a third interface, such as interface 505 below, which includes a second desktop icon of the target application, such as desktop icon 5011 in interface 505. At a fourth moment, in response to the first operation on the second desktop icon, displaying a second shortcut icon of the target application, the second shortcut corresponding to the first shortcut, as shown in the response process from interface 505 to interface 506. Between the third moment and the fourth moment, the target application was launched in response to the click operation on the second desktop icon.

[0013] That is to say, after the target application is updated and the target application is clicked to start after the update, the correct shortcut icon can also be displayed.

[0014] In a possible design method of the first aspect, the second shortcut icon corresponds to the first shortcut of the updated target application, such as the "Scan" icon 5061 in interface 506 is different from the "Scan" icon before the update displayed in interface 404 and interface 502.

[0015] That is, after the target application is updated and the target application is clicked to start after the update, the updated shortcut icon can be displayed.

[0016] In a possible design of the first aspect, the above method also includes: in response to a click operation on the first desktop icon, obtaining and storing first shortcut information of the target application, where the first shortcut information indicates the correspondence between the shortcut of the target application and the shortcut icon.

[0017] The above-mentioned displaying the first shortcut icon of the target application at the third moment in response to the first operation on the second desktop icon includes: at the third moment, in response to the first operation on the second desktop icon, querying and displaying the first shortcut icon of the target application based on the first shortcut information.

[0018] That is, by querying the stored shortcut information, the shortcut icon can be correctly displayed after the target application is updated and before it is clicked to start.

[0019] In one possible design of the first aspect, the first shortcut information includes a correspondence between an application identifier of a target application, an identifier of a shortcut of the target application, and a shortcut icon, and the shortcut of the target application includes the first shortcut. The querying and displaying the first shortcut icon of the target application based on the first shortcut information includes querying the application identifier of the target application and the identifier of the first shortcut, and displaying the corresponding first shortcut icon.

[0020] In a possible design of the first aspect, the first shortcut information also includes a version number of the target application.

[0021] In a possible design of the first aspect, the method further includes: at a fifth moment between the third moment and the fourth moment, in response to a click on the second desktop icon, obtaining and storing second shortcut information for the target application, wherein the second shortcut information indicates a correspondence between the shortcut of the target application and the shortcut icon. Exemplarily, the second shortcut icon may be used to overwrite the first shortcut icon to update the shortcut information.

[0022] The above-mentioned displaying the second shortcut icon of the target application at the fourth moment in response to the first operation on the second desktop icon includes: at the fourth moment, in response to the first operation on the second desktop icon, querying and displaying the second shortcut icon of the target application based on the second shortcut information.

[0023] That is to say, after updating the target application and clicking to start it, the shortcut icon can also be correctly displayed by querying the stored shortcut information. The specific implementation principle is similar to that of displaying the first shortcut icon above, and will not be repeated here.

[0024] In a possible design method of the first aspect, at the fourth moment, in response to the first operation on the second desktop icon, the second shortcut icon of the target application is displayed, including: at the fourth moment, in response to the first operation on the second desktop icon, the second shortcut icon of the target application is obtained through an interface call and displayed.

[0025] That is, after updating the target application and clicking to start it, the shortcut icon can be obtained and displayed through an interface call, thereby improving the display efficiency of the shortcut icon.

[0026] In a possible design manner of the first aspect, the interface call includes calling the interface through the package management PM.

[0027] In a second aspect, embodiments of the present application further provide an electronic device having multiple applications installed therein, the electronic device comprising a display screen, a memory, and one or more processors. The display screen, the memory, and the processors are coupled. The memory is configured to store computer program code, the computer program code comprising computer instructions that, when executed by the processor, cause the electronic device to perform the following steps: displaying a first interface, the first interface including a first desktop icon for a target application; launching the target application at a first moment in time in response to a click on the first desktop icon; updating the target application at a second moment in time, the second moment in time being later than the first moment in time; displaying a second interface, the second interface including a second desktop icon for the target application after the target application is updated; and displaying a first shortcut icon for the target application at a third moment in time in response to a first click on the second desktop icon; the third moment in time being later than the second moment in time, and no click on the second desktop icon has been received between the second and third moments in time, and the first shortcut icon corresponds to the first shortcut for the target application.

[0028] In a possible design manner of the second aspect, the first operation includes: a long press operation, or an operation of long pressing and dragging the border of the second desktop icon.

[0029] In a possible design manner of the second aspect, the first shortcut icon corresponds to the first shortcut of the target application before updating.

[0030] In a possible design of the second aspect, when the computer instructions are executed by the processor, the electronic device further performs the following steps: displaying a third interface, the third interface including a second desktop icon for the target application. At a fourth moment, in response to a first operation on the second desktop icon, displaying a second shortcut icon for the target application. Between the third moment and the fourth moment, the target application is launched in response to a click on the second desktop icon, and the second shortcut corresponds to the first shortcut.

[0031] In a possible design manner of the second aspect, the second shortcut icon corresponds to the updated first shortcut of the target application.

[0032] In a possible design of the second aspect, when the computer instructions are executed by the processor, the electronic device further performs the following steps: in response to a click operation on the first desktop icon, obtaining and storing first shortcut information of a target application, where the first shortcut information indicates a correspondence between a shortcut of the target application and a shortcut icon. At a third moment, in response to a first operation on the second desktop icon, querying and displaying the first shortcut icon of the target application based on the first shortcut information.

[0033] In one possible design of the second aspect, the first shortcut information includes a correspondence between an application identifier of a target application, an identifier of a shortcut of the target application, and a shortcut icon, and the shortcut of the target application includes the first shortcut. When the computer instructions are executed by the processor, the electronic device further performs the following steps: querying the application identifier of the target application and the identifier of the first shortcut, and displaying the corresponding first shortcut icon.

[0034] In a possible design manner of the second aspect, the first shortcut information also includes a version number of the target application.

[0035] In a possible design of the second aspect, when the computer instructions are executed by the processor, the electronic device further performs the following steps: at a fifth moment between the third moment and the fourth moment, in response to a click operation on the second desktop icon, obtaining and storing second shortcut information of the target application, wherein the second shortcut information indicates a correspondence between the shortcut of the target application and the shortcut icon. At the fourth moment, in response to the first operation on the second desktop icon, querying and displaying the second shortcut icon of the target application based on the second shortcut information.

[0036] In a possible design of the second aspect, when the computer instruction is executed by the processor, the electronic device further performs the following steps: at a fourth moment, in response to the first operation on the second desktop icon, the second shortcut icon of the target application is obtained through an interface call and displayed.

[0037] In a possible design manner of the second aspect, the interface call includes calling the interface through the package management PM.

[0038] In a third aspect, an embodiment of the present application provides a chip system, which is applied to an electronic device including a display screen and a memory; the chip system includes one or more interface circuits and one or more processors; the interface circuit and the processor are interconnected by lines; the interface circuit is used to receive a signal from the memory of the electronic device and send the signal to the processor, the signal including computer instructions stored in the memory; when the processor executes the computer instructions, the electronic device executes the method described in the first aspect and any possible design method thereof.

[0039] In a fourth aspect, the present application provides a computer storage medium comprising computer instructions. When the computer instructions are executed on an electronic device, the electronic device executes the method described in the first aspect and any possible design thereof.

[0040] In a fifth aspect, the present application provides a computer program product, which, when executed on a computer, enables the computer to execute the method described in the first aspect and any possible design thereof.

[0041] It can be understood that the beneficial effects that can be achieved by the electronic device described in the second aspect, the chip system described in the third aspect, the computer storage medium described in the fourth aspect, and the computer program product described in the fifth aspect provided above can refer to the beneficial effects in the first aspect and any possible design method thereof, and will not be repeated here. BRIEF DESCRIPTION OF THE DRAWINGS

[0042] Figure 1 A schematic diagram of a scenario for displaying shortcut icons provided in an embodiment of the present application;

[0043] Figure 2 A schematic diagram of another scenario for displaying shortcut icons provided in an embodiment of the present application;

[0044] Figure 3 A schematic diagram of an abnormal shortcut icon display provided in an embodiment of the present application;

[0045] Figure 4 One of the interface interaction diagrams showing shortcut icons provided in an embodiment of the present application;

[0046] Figure 5 The second interactive diagram of the interface displaying shortcut icons provided in an embodiment of the present application;

[0047] Figure 6 A diagram showing the hardware architecture of a mobile phone according to an embodiment of the present application;

[0048] Figure 7 A software architecture diagram of a mobile phone provided in an embodiment of the present application;

[0049] Figure 8 One of the display principle diagrams of the shortcut icon provided in the embodiment of the present application;

[0050] Figure 9 A sequential interaction diagram of the storage and update of shortcut information provided in an embodiment of the present application;

[0051] Figure 10 The second schematic diagram of the display principle of the shortcut icon provided in the embodiment of the present application;

[0052] Figure 11 One of the sequential interaction diagrams for displaying shortcut icons provided in an embodiment of the present application;

[0053] Figure 12 The third diagram of the display principle of the shortcut icon provided in the embodiment of the present application;

[0054] Figure 13 The second sequential interaction diagram of the display of the shortcut icon provided in the embodiment of the present application;

[0055] Figure 14 This is a diagram of the chip system provided in an embodiment of the present application. DETAILED DESCRIPTION

[0056] The technical solutions in the embodiments of the present application are described below in conjunction with the drawings in the embodiments of the present application. Among them, in the description of the embodiments of the present application, the terms used in the following embodiments are only for the purpose of describing specific embodiments, and are not intended to be used as limitations on the present application. As used in the specification and claims of the present application, the singular expressions "a", "said", "above", "the" and "this" are intended to also include expressions such as "one or more", unless there is a clear contrary indication in the context. It should also be understood that in the following embodiments of the present application, "at least one", "one or more" refer to one or more (including two). The term "and / or" is used to describe the association relationship of associated objects, indicating that three relationships can exist; for example, A and / or B can represent: the existence of A alone, the existence of A and B at the same time, and the existence of B alone, where A and B can be singular or plural. The character " / " generally indicates that the associated objects before and after are in an "or" relationship.

[0057] References to "one embodiment" or "some embodiments" etc. described in this specification mean that the specific features, structures or characteristics described in conjunction with the embodiment are included in one or more embodiments of the present application. Therefore, the statements "in one embodiment", "in some embodiments", "in some other embodiments", "in some other embodiments", etc. appearing in different places in this specification do not necessarily refer to the same embodiment, but mean "one or more but not all embodiments", unless otherwise specifically emphasized in another way. The terms "including", "comprising", "having" and their variations all mean "including but not limited to", unless otherwise specifically emphasized in another way. The term "connected" includes direct and indirect connections, unless otherwise stated. "First" and "second" are used for descriptive purposes only and are not to be understood as indicating or implying relative importance or implicitly indicating the number of technical features indicated.

[0058] In the embodiments of this application, words such as "exemplarily" or "for example" are used to indicate examples, illustrations, or explanations. Any embodiment or design described as "exemplarily" or "for example" in the embodiments of this application should not be interpreted as being preferred or advantageous over other embodiments or designs. Rather, the use of words such as "exemplarily" or "for example" is intended to present the relevant concepts in a concrete manner.

[0059] The method for displaying a shortcut icon provided in the embodiment of the present application can be applied to the scenario of displaying a shortcut icon in an electronic device.

[0060] The electronic devices involved in the embodiments of the present application may also be referred to as terminals, user equipment (UE), mobile stations (MS), mobile terminals (MT), etc. The electronic devices may be mobile phones, smart TVs, wearable devices, tablet computers (Pads), computers with wireless transceiver functions, virtual reality (VR) devices, augmented reality (AR) devices, wireless terminals in industrial control, wireless terminals in self-driving, wireless terminals in remote medical surgery, wireless terminals in smart grids, wireless terminals in transportation safety, wireless terminals in smart cities, or wireless terminals in smart homes, etc. The embodiments of the present application do not limit the specific technologies and specific device forms used by the electronic devices. The following mainly takes the electronic device being a mobile phone as an example to illustrate the embodiments of the present application.

[0061] For example, several typical scenarios for displaying shortcut icons are listed here.

[0062] Scenario 1: In response to a long press operation on a desktop icon, the mobile phone displays a shortcut icon.

[0063] See also Figure 1 , the mobile phone can display interface 101, which is the mobile phone's desktop. Interface 101 includes desktop icons for multiple applications. In response to a user long-pressing any desktop icon in interface 101, the mobile phone can display a shortcut menu for the application corresponding to the desktop icon, which includes at least one shortcut icon. Taking any desktop icon as an example, if the desktop icon is desktop icon 1011 for a chat application in interface 101, in response to a user long-pressing desktop icon 1011 in interface 101, the mobile phone can display interface 102, which includes a shortcut menu 1021 for the chat application. Shortcut menu 1021 includes shortcuts and icons such as "Payment," "Start a Chat," "Add a Friend," and "Scan," such as "Payment" icon 1022, "Start a Chat" icon 1023, "Add a Friend" icon 1024, and "Scan" icon 1025.

[0064] Scenario 2: In response to an operation of long pressing a desktop icon and dragging the icon border, the mobile phone displays a shortcut icon.

[0065] In response to the user's long press operation on any desktop icon, the mobile phone can also highlight the border of the desktop icon, and then in response to the user's drag operation on the border, such as dragging up and down or left and right, the mobile phone can display the desktop icon and its shortcut icon in a folder.

[0066] Still taking the desktop icon 1011 of the chat application in the interface 101 as an example, in response to the user's long press operation on the desktop icon 1011 in the interface 101, see Figure 2 , the mobile phone may display interface 201. Based on the above interface 102, interface 201 highlights a border 2011 of desktop icon 1011. In response to the user dragging border 2011 downward and then to the right, the mobile phone may display interface 202, which includes a folder 2020. Folder 2020 includes not only desktop icon 1011, but also a "Scan" icon 2021, a "Start Chat" icon 2022, and an "Add Friend" icon 2023, that is, shortcut icons may also be displayed.

[0067] It should be noted that in the above scenario, the shortcut icon in the folder can be permanently displayed on the desktop. Subsequently, in response to the user's operation of closing the folder, the mobile phone can cancel the shortcut icon in the folder and display the desktop icon independently.

[0068] Furthermore, in response to a user triggering operation (such as a long press operation) on any shortcut icon in the above scenario 2, the mobile phone can also display a shortcut menu similar to that in scenario 1, thereby displaying the shortcut icon. In other words, the shortcut icons in scenario 1 and scenario 2 can be displayed at the same time.

[0069] Continue to see Figure 2 Taking the "Initiate Chat" icon 2022 in interface 202 as an example, in response to the user's long press operation on the "Initiate Chat" icon 2022 in interface 202, the mobile phone can display interface 203, and interface 203 includes a shortcut menu 2031. The shortcut menu 2031 includes shortcut icons, which are similar to the shortcut menu 1021 in the previous interface 102 and will not be repeated here.

[0070] Scenario 3: Add a shortcut icon to the desktop. When the phone displays the desktop, the shortcut icon can be displayed.

[0071] Shortcut icons can also be added to the mobile phone's desktop. For example, the above interface 101 includes not only desktop icons for multiple applications, but also a "Scan" icon 1012 for the chat application, meaning that a shortcut icon for the chat application has been added to the desktop. Accordingly, when the mobile phone displays interface 101, icon 1012, i.e., the shortcut icon, will be displayed.

[0072] It should be noted that the above scenarios 1 to 3 are only two typical scenario examples and are not limited to them in actual implementation.

[0073] In the above scenario of displaying shortcut icons, mobile phones (especially some that use The inability to display shortcut icons correctly includes two situations: the inability to display shortcut icons or the display of incorrect shortcut icons.

[0074] See also Figure 3 In screen 301, on Honor phones, folder 3011 in screen 301 and the "Scan" and "Start Chat" icons in shortcut menu 3012 are not displayed (indicated by a cracked image symbol in the figure, the same applies below). The "Add Friend" icon is displayed incorrectly (indicated by a black fill in the figure, the same applies below). Additionally, the "Payment" icon in shortcut menu 3012 is also not displayed.

[0075] See also Figure 3 In the interface 302, in other In the mobile phone of the framework, the icon 3021 of the shortcut 1 in the interface 302 is displayed incorrectly.

[0076] After analysis, it was found that the main reasons for the inability to display the shortcut icon correctly are as follows: some applications use dynamic shortcuts. A dynamic shortcut icon means that the resource identifier (Identity document, ID) of the shortcut icon changes dynamically, and the resource ID can be updated in each version of the application. In addition, code obfuscation technology is used when compiling the installation packages of these applications (such as APK), making it difficult to obtain the real resource ID after the update. In this case, after the application is updated and before the application is launched by clicking the desktop icon of the application (hereinafter referred to as click to launch), the mobile phone may not be able to obtain the correct shortcut icon through the obfuscated resource ID in the installation package.

[0077] It should be noted that after an application is launched, when the shortcut icon needs to be displayed, the desktop can obtain, for example, through a Package Manager (PM) callback, the correspondence between the application's shortcut icon and the new resource ID, so that the shortcut icon can be displayed correctly. Therefore, the situation where the shortcut icon cannot be displayed correctly usually occurs after the application is updated and before it is launched.

[0078] For example, after the chat application is updated, the resource ID of the "Scan" icon is changed to 2, and "2" is obfuscated as "AAA" in the installation package. After this update and before it is started, in response to the user's long press operation on the desktop icon of the chat application, the mobile phone can obtain the obfuscated "AAA" in the installation package. It is highly likely that the correct "Scan" icon cannot be obtained through "AAA".

[0079] To address the above issues, an embodiment of the present application provides a method for displaying shortcut icons. After a target application is clicked and launched, the shortcut information of the target application can be obtained and stored. The shortcut information can indicate the correspondence between the shortcut identifier and the shortcut icon. Subsequently, after the target application is updated, the shortcut icon can be displayed based on the stored shortcut information, thereby ensuring that the correct shortcut icon is displayed even after the target application is updated and before it is clicked and launched.

[0080] The target application can be an application that uses dynamic shortcuts and uses code obfuscation technology when compiling the installation package. Of course, in actual implementation, the target application can also be any application on the phone, so that the display logic of shortcut icons for all applications on the phone can be unified.

[0081] Furthermore, the shortcut information includes the following information: the identifier of the target application (such as the application package name), the identifier of the shortcut (such as the ID or name, etc.), and the corresponding relationship between the shortcut icon. For example, the shortcut information of the chat application is shown in Table 1 below:

[0082] Table 1

[0083]

[0084] Accordingly, after the target application is updated, in response to a long press operation on the desktop icon of the target application, the corresponding shortcut icon can be obtained from the stored shortcut information through the identifier of the target application and the ID of the shortcut and displayed.

[0085] For example, in response to a user long-pressing the chat application desktop icon, the chat application can be determined as the target application for which a shortcut icon should be displayed. The chat application's package name and the IDs of the shortcuts in the shortcut menu can then be used to query the application. For example, if the first shortcut in the shortcut menu is "Scan," the chat application's package name and the ID of "Scan" can be used to query and obtain icon 1, thereby displaying icon 1 in the first shortcut position in the shortcut menu. Similarly, each shortcut icon can be obtained and displayed.

[0086] In this way, the correct shortcut icon will not be displayed due to the change and confusion of the shortcut icon's resource ID.

[0087] In actual implementation, the shortcut information is not limited to the above. For example, the shortcut information may also include the application version number, icon class name, etc. This application does not make specific limitations on this.

[0088] The embodiment of the present application will combine the above-mentioned scenario 1 (i.e., displaying the shortcut icon in response to a long press operation) to provide a detailed introduction to the interface interaction process of the mobile phone after adopting the display method of the shortcut icon.

[0089] In some embodiments, after the target application is installed on the mobile phone and before it is launched for the first time, the mobile phone may not respond to a user's long press operation on the desktop icon of the target application.

[0090] See also Figure 4 After the chat application is installed, the mobile phone may display an interface 401 including a desktop icon 4011 of the chat application. Before the chat application is clicked and started for the first time, the mobile phone may not respond to a long press operation of the user on the desktop icon 4011.

[0091] It is understandable that before the first click to start, the mobile phone cannot obtain the shortcut information of the target application and cannot display the correct shortcut icon. Therefore, the mobile phone can avoid displaying an incorrect shortcut icon by not responding.

[0092] In practice, after the target application is installed on the mobile phone, before the first click to start it, the user may not perform a long press operation on the desktop icon of the target application. Accordingly, the above-mentioned unresponsive process may not occur.

[0093] After the target application is installed on the mobile phone, in response to a user clicking on the desktop icon of the target application, the mobile phone may start the target application, that is, the target application is clicked and started.

[0094] Continue to see Figure 4 In response to the user clicking on the desktop icon 4011, the mobile phone can display the interface 402, which is the application interface of the chat application, and starts the chat application.

[0095] After the target application is clicked to start, including after the first click to start or the second, third... click to start, and before the next update of the target application, in response to the user's long press operation on the desktop icon of the target application, the mobile phone can correctly display the shortcut icon of the target application.

[0096] Continue to see Figure 4After returning to the desktop (recorded as interface 403, the same as interface 401) from interface 402, if the mobile phone displays interface 403 in response to the user sliding upward from the bottom of interface 402, then in response to the user long pressing the desktop icon 4011 of the chat application in interface 403, the mobile phone can display interface 404, which includes a shortcut icon for the chat application.

[0097] Subsequently, in response to an update event, the mobile phone can update the target application. The update event can be an event manually triggered by the user or an event automatically updated by the mobile phone, such as automatically detecting a new version and then updating. This application does not make specific restrictions on this.

[0098] See also Figure 5 After updating the chat application, the phone displays interface 501, which is the phone's desktop. Interface 501 includes a desktop icon 5011 for the chat application. Desktop icon 5011 differs from desktop icon 4011, indicating that the chat application has changed since the update. It should be noted that in practice, desktop icons can remain unchanged after an application is updated; the changes shown in the figure are intended to distinguish between application updates.

[0099] After updating the target application and before clicking to start the target application after the update, in response to the user's long press operation on the desktop icon of the target application, the mobile phone can also correctly display the shortcut icon of the target application, which can improve the human-computer interaction experience compared with conventional technologies.

[0100] Continue to see Figure 5 In response to the user's long press operation on the desktop icon 5011 of the chat application in interface 501, the mobile phone can display interface 502 (the same as the previous interface 404), and the shortcut icons of the chat application in interface 502 are all correct. In conventional technology, such as the previous interface 301, they may be displayed incorrectly.

[0101] After the target application is updated, in response to a user clicking on the desktop icon of the target application, the mobile phone can also start the target application, that is, the target application is clicked and started after the target application is updated.

[0102] Continue to see Figure 5 After canceling the display of shortcut menu 5021 in interface 502, if the user clicks an area outside of shortcut menu 5021 in interface 502, the mobile phone may display interface 503 (the same as interface 501). In response to the user clicking on desktop icon 5011 of the chat application in interface 503, the mobile phone may display interface 504, which is the application interface of the chat application, that is, the chat application was clicked and started after the chat application was updated.

[0103] After the target application is updated and clicked to start after the update, in response to the user's long press operation on the desktop icon of the target application, the mobile phone can also correctly display the shortcut icon of the target application.

[0104] Furthermore, application updates may include changes to shortcuts. That is, before and after the target application is updated, shortcuts may change. Specifically, these changes may include changes to the shortcut icon's resource ID, changes to the shortcut icon's style, addition of shortcut icons, deletion of shortcut icons, etc. After the target application is updated and before it is clicked to be launched, the shortcut icon for the target application displayed on the phone, such as the shortcut icon in interface 502, may not be the latest one, but the one before the target application was updated. After the target application is updated and launched, the shortcut icon for the target application displayed on the phone will be the latest one.

[0105] Continue to see Figure 5 After returning to the desktop (referred to as interface 505) from interface 504, for example, in response to a user sliding upward from the bottom of interface 504 to display interface 505, the mobile phone may display interface 506 in response to a user long-pressing desktop icon 5011 of the chat application in interface 505. Interface 506 includes shortcut icons for the chat application, but the "Scan" icon 5061 in interface 506 is different from the "Scan" icon 5022 in interface 502. Interface 506 displays the latest shortcut icon.

[0106] It should be noted that the above interface 506 shows the situation where the style of the shortcut icon has changed. In addition, if a shortcut icon is added, the interface 506 may include shortcut icons that are not included in the interface 502. If a shortcut icon is deleted, the interface 506 may not include some shortcut icons in the interface 502.

[0107] In addition, if the shortcut icon has not changed, the shortcut icon in interface 505 is the same as the shortcut icon in interface 502.

[0108] At this point, it should be noted that the above Figure 5 Only the interface interaction process after the target application is updated once is shown. In practice, each time the target application is updated, the interface interaction process can be updated according to the Figure 5 Similar interactive process responses will not be described in detail in this article.

[0109] The specific implementation of the above interface interaction process will be further explained below in conjunction with the software and hardware structure of the mobile phone.

[0110] See also Figure 6The mobile phone may include a processor 110, an internal memory 121, a universal serial bus (USB) interface 130, a charging management module 140, a power management module 141, a battery 142, an antenna 1, an antenna 2, a mobile communication module 150, a wireless communication module 160, a speaker, a receiver, a microphone, an earphone interface, a sensor 180, a camera 193, a display screen 194, etc.

[0111] It should be understood that the structures illustrated in the embodiments of the present invention do not constitute a specific limitation on mobile phones. In other embodiments of the present application, the mobile phone may include more or fewer components than shown in the figure, or some components may be combined or separated, or the components may be arranged differently. The components shown in the figure may be implemented in hardware, software, or a combination of software and hardware.

[0112] The processor 110 may include one or more processing units. For example, the processor 110 may include an application processor (AP), a modem processor, a graphics processing unit (GPU), an image signal processor (ISP), a controller, a memory, a video codec, a digital signal processor (DSP), a baseband processor, and / or a neural-network processing unit (NPU). Different processing units may be independent devices or integrated into one or more processors.

[0113] In a specific implementation, the mobile phone can execute the method for displaying the shortcut icon through the processor 110, so that the shortcut icon is still correctly displayed after the application is updated.

[0114] The wireless communication function of the mobile phone can be realized through antenna 1, antenna 2, mobile communication module 150, wireless communication module 160, modem processor and baseband processor.

[0115] The mobile phone implements its display functionality through a GPU, display 194, and an application processor. The GPU is a microprocessor for image processing that connects display 194 and the application processor. The GPU is used to perform mathematical and geometric calculations for graphics rendering. Processor 110 may include one or more GPUs that execute program instructions to generate or modify display information.

[0116] The display screen 194 is used to display images, videos, etc. In a specific implementation, the mobile phone can display desktop icons, shortcut icons, etc. through the display screen 194.

[0117] The mobile phone can realize the shooting function through the ISP, camera 193, video codec, GPU, display 194 and application processor.

[0118] The software system of the mobile phone can adopt a layered architecture, event-driven architecture, micro-kernel architecture, micro-service architecture, or cloud architecture. This embodiment of the application does not specifically limit this. In addition, the operating system of the mobile phone can be In the following embodiments, the Android system with a layered architecture is mainly used as an example to illustrate the software architecture of a mobile phone.

[0119] The layered architecture divides the software into several layers, each with a clear role and division of labor. The layers communicate with each other through software interfaces. In some embodiments, see Figure 7 , the Android system may include an application layer and an application framework layer. Of course, the Android system may also include an Android runtime (Android runtime), a system library, a kernel layer, etc., which are not shown in the figure.

[0120] Among them, the application layer can be installed with applications (APPs) such as calls, memos, browsers, contacts, cameras, galleries, calendars, maps, Bluetooth, music, videos, and chats, among which only some are shown in the figure.

[0121] Some or all of these applications may provide shortcut icons. The target applications are some or all of the applications in the application layer.

[0122] Furthermore, the application layer also includes desktop applications, which can be used to display desktop icons and shortcut icons.

[0123] The application framework layer provides an application programming interface (API) and a programming framework for applications in the application layer.

[0124] The application framework layer may include system services such as a window manager, a resource manager, and a notification manager, which are not shown in the figure.

[0125] The application framework layer may also include a package management service (PackageManagerService, PMS). The PMS can be used to manage the installation package of the application, such as scanning and installation, and can also be used to manage the display of shortcut icons.

[0126] Furthermore, the PMS may include shortcut management (such as android.content.pm.ShortcutManager) and shortcut services (android.server.pm.ShortcutService).

[0127] Shortcut management is used to manage shortcut changes. For example, shortcut management can notify the shortcut service when a shortcut changes. For another example, shortcut management can identify and differentiate between scenarios in which shortcuts change, such as changes in the context of installing a target application or in the context of launching a target application.

[0128] The shortcut service manages registered services. This includes registering a target service for package shortcut change events (e.g., packageShortcutsChanged). When a target service needs to monitor, it can register with the shortcut service. Subsequently, the shortcut service can notify the registered target service of shortcut changes.

[0129] The application framework layer also includes a desktop application service (android.server.pm.LauncherAppsService), which is a target service. Specifically, the desktop application service can register with the shortcut service to listen for package shortcut change events, allowing it to promptly detect shortcut changes. Furthermore, the desktop application service can notify the desktop application of shortcut changes, allowing the desktop application to perform appropriate processing, such as storing shortcut information to ensure the correct display of the shortcut icon.

[0130] The display method of the shortcut icon provided in the embodiment of the present application can be implemented in a mobile phone having the above-mentioned software and hardware structure.

[0131] After installing the target application and clicking to start it for the first time, the mobile phone (such as a desktop application) can obtain and store the shortcut information of the target application, such as storing it in the shortcut icon database. Subsequently, each time the target application is updated and clicked to start after the update, the mobile phone (such as a desktop application) can obtain and update the stored shortcut information. In other words, the mobile phone can store shortcut information in a timely manner. Under this premise, the mobile phone (such as a desktop application) can obtain the shortcut icon by querying the stored information. In this way, even after the target application is updated and before clicking to start, the shortcut icon can be correctly displayed by querying the stored information.

[0132] See also Figure 8After installing version 1.0 (denoted as V1.0 in the figure) of the target application and clicking to start it for the first time (denoted as Click to Start 1 in the figure), if the user clicks on the desktop icon 4011 in the above interface 401, the mobile phone can store the shortcut information corresponding to version 1.0 in the shortcut icon database. Before the target application is updated to version 2.0 (denoted as V2.0 in the figure) and clicks to start it (denoted as Click to Start 2 in the figure), in response to a long press operation on the desktop icon of the target application (denoted as Long Press 20 in the figure), the mobile phone can query the shortcut information of the target application from the shortcut icon database, and can query and display the shortcut icon corresponding to version 1.0, as shown in the shortcut icon in the above interface 502, thereby ensuring that the shortcut icon can be correctly displayed after the target application is updated and before clicking to start it after this update. After the target application is updated to version 2.0 and clicks to start it (such as Click to Start 2), the mobile phone can update the shortcut information corresponding to version 1.0 in the shortcut icon database to the shortcut information corresponding to version 2.0. Subsequently, after the target application is updated to version 3.0, it can be processed according to a process similar to the aforementioned version 2.0... and so on. The mobile phone can ensure that the shortcut icon can be correctly displayed each time the target application is updated and before clicking to start the application after the update.

[0133] For example, the mobile phone can use Figure 9 The process shown in FIG. 1 realizes the storage and update of shortcut information.

[0134] S901: When a shortcut of a target application is changed, in response to a click operation on a desktop icon of the target application, the target application sends a first notification to a shortcut management system.

[0135] It is understandable that in response to a click operation on the desktop icon of the target application, the target application will first be started, as shown in the response process of interface 401-interface 402 and interface 503-interface 504 above, which will not be repeated here.

[0136] Among them, the situations in which the shortcut of the target application changes mainly include the following two situations:

[0137] The first one is the change after the first click, as mentioned above Figure 8 The corresponding situation of Click to Launch 1. After the first click to launch, all shortcuts of the target application are new. The change in this case is equivalent to adding all shortcuts of the target application.

[0138] The second type is to update the target application and then click Start to change, as mentioned above Figure 8The situation corresponding to clicking Start 2 in the middle. After updating the target application, the shortcuts may change compared to the version before the update. The changes in this case include at least one of the following: adding, updating, and removing. Adding means adding a shortcut icon compared to the version before the update. Updating means updating the shortcut icon and / or the resource ID of the shortcut icon compared to the version before the update, such as changing the style of the shortcut icon, changing the resource ID, etc. Removing means deleting the shortcut icon compared to the version before the update.

[0139] It should be noted that in cases other than the above two cases, such as the second, third, etc. clicks to start after the first click to start and before the next update target application, or the second, third, etc. clicks to start between two update target applications, the shortcut will usually not change, so the first notification may not be sent.

[0140] S902: The shortcut manager recognizes that the target application is clicked to start, adds a first identifier to the first notification, and generates a second notification.

[0141] The first identifier is used to identify the click to start. By adding the first identifier, it is easy to subsequently identify the situation where the target application is clicked to start and complete the storage and update of the shortcut information for this situation. For details, please refer to the description of S906 and S907 below.

[0142] In one specific implementation, the target application may also include a triggering event when sending the first notification to the shortcut manager. For example, in the case of a click-to-launch notification, the triggering event is a click on the target application's desktop icon. In this way, the shortcut manager can identify whether the target application was clicked to launch based on the triggering event.

[0143] If the triggering event is clicking the target application's desktop icon, the target application can be identified as being launched by clicking on it. If the triggering event is not clicking the target application's desktop icon, the target application can be identified as not being launched by clicking on it. For example, when installing a target application, if the shortcut changes, the target application will also send a shortcut change notification to the shortcut manager. In this case, if the triggering event is not clicking the target application's desktop icon, the target application can be identified as not being launched by clicking on it.

[0144] S903: The shortcut management sends a second notification to the shortcut service.

[0145] S904: The shortcut service sends a second notification to the desktop application service.

[0146] Exemplarily, when the shortcut service receives the second notification, it detects a package shortcut change event (such as packageShortcutsChanged). The shortcut service can notify the target service that has registered a listener for the event so that the target service can be informed that the shortcut of the target application has changed.

[0147] For example, the desktop application service registers a listener for packageShortcutsChanged. After receiving the second notification, the shortcut service notifies the desktop application service so that the desktop application service is informed that the shortcut of the target application has changed.

[0148] S905. The desktop application service sends a second notification to the desktop application.

[0149] Exemplarily, the desktop application service receives the second notification, which can be understood as receiving a callback (such as onShortcutChanged) of the PM shortcut change, and further notifies the desktop application so that the desktop application can be informed that the shortcut of the target application has changed.

[0150] S906: The desktop application detects, based on the first identifier, that the application is started by clicking on the desktop application.

[0151] Typically, both the click-to-launch and installation scenarios trigger a callback for changing the PM's shortcut. In this embodiment of the present application, for the click-to-launch scenario, the target application's shortcut information is obtained and stored in a database. Therefore, the desktop application can first detect whether it is a click-to-launch scenario. If the first identifier is obtained, indicating that it is a click-to-launch scenario, the application can proceed to S907 below to complete the storage of the shortcut information.

[0152] In addition, if the first identifier is not obtained, it indicates that it is an installation situation. In this case, since the target application is not started, the desktop application cannot obtain accurate shortcut information, and it is difficult to store the shortcut information, so the following S907 is not executed.

[0153] S907: The desktop application obtains and stores shortcut information of the target application.

[0154] Exemplarily, the second notification carries an application identifier of the target application, such as an application package name, and the desktop application can obtain shortcut information of the target application based on the application identifier.

[0155] In a specific implementation, the desktop application can obtain the shortcut information of the target application through the PM interface. It should be noted that since the target application is clicked and launched, the PM interface can obtain accurate shortcut information, such as the updated, real (unobfuscated) resource ID.

[0156] After obtaining the shortcut information of the target application, the desktop application stores the shortcut information in a database for subsequent display of the shortcut icon.

[0157] If the desktop application finds that the database contains shortcut information for the target application, it can update the shortcut information for the target application in the database, such as overwriting the shortcut information for the target application in the database with the newly obtained shortcut information. This situation mainly occurs after the target application is updated. In this scenario, the desktop application has already written the shortcut information for the target application to the database when it was previously clicked and launched, so the database contains the shortcut information for the target application.

[0158] If the desktop application finds that the database does not contain the target application's shortcut information, it can directly write the target application's shortcut information into the database. This situation mainly occurs when the target application is first installed and then clicked to launch. In this scenario, the target application's shortcut information has not yet been written to the database, so the database does not contain the target application's shortcut information.

[0159] In some scenarios, a shortcut icon of the target application may be permanently displayed on the mobile phone desktop, such as the shortcut icon in the folder in Scenario 2 and the shortcut icon in Scenario 3. After obtaining the shortcut information of the target application, the desktop application may further execute S908 below to ensure that the shortcut icon of the target application permanently displayed on the desktop is correct.

[0160] S908: The desktop application refreshes the shortcut icon permanently displayed on the desktop based on the acquired shortcut information of the target application.

[0161] For example, a "Scan" icon of a chat application is permanently displayed on the desktop, such as icon 1012 in the above interface 101. After obtaining the shortcut information of the chat application, the desktop application can refresh the "Scan" icon in the shortcut information to the location of the "Scan" icon on the desktop.

[0162] In this way, the desktop application can update the permanently displayed shortcut icon in a timely manner after the shortcut of the target application is changed. While ensuring that the shortcut icon of the target application permanently displayed on the desktop is correct, the shortcut icon can also be pre-refreshed, and the shortcut icon can be quickly displayed when the desktop is displayed subsequently.

[0163] It should be noted that if there is no shortcut icon of the target application permanently displayed on the desktop, the above S908 may be omitted.

[0164] Of course, desktop applications can also use the following method (as shown below Figure 10-13 As shown) to realize the display of permanent shortcut icons.

[0165] Using the above Figure 9 According to the process shown, the mobile phone can store the latest shortcut information in the database in a timely manner.

[0166] In some embodiments, each time a shortcut icon needs to be displayed, as shown in scenarios 1 to 3, the mobile phone may query a database, such as a shortcut icon database, to obtain shortcut information and use it to display the shortcut icon.

[0167] See also Figure 10 , in the previous article Figure 8 On the basis of, after the first click to start (such as click to start 1), in response to the long press operation on the desktop icon of the target application (denoted as long press 11 in the figure), the mobile phone can query the shortcut information of the target application from the shortcut icon database, query the shortcut icon corresponding to version 1.0 and display it, as shown in the previous interface 404, so that after the first click to start and before the next update of the target application, the shortcut icon can also be displayed by querying the shortcut information in the database. After updating to version 2.0 and clicking to start (such as clicking to start 2), in response to the long press operation on the desktop icon of the target application (denoted as long press 21 in the figure), the mobile phone can query the shortcut information of the target application from the shortcut icon database, query the shortcut icon corresponding to version 2.0 and display it, as shown in the previous interface 506, so that after updating the target application and clicking to start, the shortcut icon can also be displayed by querying the shortcut information in the database.

[0168] In this way, the mobile phone can uniformly query the database to achieve the correct display of shortcut icons.

[0169] Taking the above scenario 1 as an example, the mobile phone can use Figure 11 The process shown in FIG. 1 realizes the display of the shortcut icon.

[0170] S1101 : In response to a long press operation on a desktop icon of a target application, the desktop application displays a shortcut menu of the target application.

[0171] Exemplarily, the long press operation may be a long press operation of the user on the desktop icon 5011 in the previous interface 501 , and the shortcut menu may be the shortcut menu 5021 in the interface 502 .

[0172] As another example, the long press operation may be a long press operation of the user on the desktop icon 5011 in the previous interface 505 , and the shortcut menu may be a shortcut menu in the interface 506 .

[0173] S1102: The desktop application queries the shortcut information of the target application and obtains the shortcut icon of the target application.

[0174] S1103: The desktop application displays a shortcut icon of the target application in a shortcut menu.

[0175] In a specific implementation, only some shortcut icons of the target application are displayed in the shortcut menu. The desktop application can obtain and display the corresponding icon from the shortcut icon of the target application based on the identifier of the shortcut icon to be displayed in the shortcut menu, such as the class name.

[0176] In a specific implementation, the shortcut icons to be displayed in the shortcut menu have a strict arrangement order. The desktop application can obtain the corresponding icon from the shortcut icon of the target application based on the identifier of the shortcut icon to be displayed in each position in the shortcut menu, such as the class name, and display it in the corresponding position of the shortcut menu.

[0177] use Figure 11 In the process of step S1101, the long press operation after clicking to start and the long press operation before clicking to start are not distinguished. This ensures that the correct display of the shortcut icon is achieved by uniformly querying the database.

[0178] The long press operation after clicking to start includes: the long press operation from the first click to start to the next update of the target application, and the long press operation after the last click to start from the update of the target application to the next update of the target application. The same applies to the following.

[0179] The "long press before click to start" operation primarily refers to the long press operation between the time the target app is updated and the time before the next update of the target app, but before the click to start. It should be noted that before the first click to start, the phone does not respond to the user's long press operation on the target app's desktop icon. Therefore, "before click to start" generally does not include the time before the first click to start. The same applies to the following text.

[0180] In some embodiments, after clicking to start, the mobile phone can directly obtain and display the shortcut icon of the target application through an interface, such as a PM interface. Before clicking to start, the mobile phone can query a database to obtain the shortcut information of the target application and use it to display the shortcut icon, ensuring that the shortcut icon is correctly displayed from the time the target application is updated until the time the update is clicked to start.

[0181] Among them, the method of obtaining through the interface can obtain the shortcut icon more efficiently than the method of querying the database. Therefore, after clicking to start, obtaining the shortcut icon through the interface can improve the efficiency of displaying the shortcut icon.

[0182] See also Figure 12 , in the previous article Figure 8 On the basis of, after the first click to start (such as click to start 1), in response to the long press operation on the desktop icon of the target application (denoted as long press 11 in the figure), the mobile phone can directly obtain the shortcut icon of the target application through the interface and display it, as shown in the previous interface 404, thereby improving the efficiency of displaying the shortcut icon after the first click to start and before the next update of the target application. After updating to version 2.0 and clicking to start (such as clicking to start 2), in response to the long press operation on the desktop icon of the target application (denoted as long press 21 in the figure), the mobile phone can query the shortcut information of the target application from the shortcut icon database, query the shortcut icon corresponding to version 2.0 and display it, as shown in the previous interface 506, so that after updating the target application and clicking to start, the shortcut icon can also be displayed by querying the shortcut information in the database.

[0183] In this way, the mobile phone can not only ensure that the shortcut icon is displayed correctly before clicking to start, but also improve the efficiency of displaying the shortcut icon after clicking to start.

[0184] Still taking the above scenario 1 as an example, the mobile phone can use Figure 13 The process shown in FIG. 1 realizes the display of the shortcut icon.

[0185] S1301: In response to a long press operation on a desktop icon of a target application, the desktop application displays a shortcut menu of the target application.

[0186] S1302: Before clicking to start, the desktop application queries the shortcut information of the target application and obtains the shortcut icon of the target application.

[0187] For example, the user's long press operation on the desktop icon 5011 in the previous interface 501 is before clicking to start.

[0188] S1303: After clicking to start, the desktop application obtains the shortcut icon of the target application through the PM interface.

[0189] For example, the user's long press operation on the desktop icon 5011 in the previous interface 505 is performed after clicking to start.

[0190] At this point, it should be noted that in the embodiments of the present application, the specific implementation of detecting whether the situation is before or after a click to start is not limited, and those skilled in the art can flexibly choose according to actual needs. For example, the desktop application can record the click timestamp of the desktop icon of the target application and the timestamp of the target application update, and detect whether it is before or after a click to start by comparing the timestamps.

[0191] S1304: The desktop application displays a shortcut icon of the target application in a shortcut menu.

[0192] It should be noted that Figure 13 For details about the implementation of Figure 11 The relevant instructions will not be repeated here.

[0193] use Figure 13 In the process, in S1302 and S1303, the long press operation after clicking to start and the long press operation before clicking to start are distinguished, so that different methods can be used to obtain shortcut icons according to different situations.

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

[0195] like Figure 14 As shown, an embodiment of the present application also provides a chip system. The chip system 1400 includes at least one processor 1401 and at least one interface circuit 1402. The at least one processor 1401 and the at least one interface circuit 1402 can be interconnected via lines. The processor 1401 is used to support the electronic device to implement the various steps in the above method embodiment, and the at least one interface circuit 1402 can be used to receive signals from other devices (such as a memory) or send signals to other devices (such as a communication interface). The chip system may include a chip and may also include other discrete devices.

[0196] An embodiment of the present application further provides a computer storage medium, which includes instructions. When the instructions are executed on the above-mentioned electronic device, the electronic device executes each step in the above-mentioned method embodiment.

[0197] An embodiment of the present application further provides a computer program product comprising instructions, which, when executed on the electronic device, causes the electronic device to execute each step in the method embodiment.

[0198] Regarding the technical effects of the chip system, computer storage medium, and computer program product, refer to the technical effects of the previous method embodiments.

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

[0200] Those skilled in the art will appreciate that the modules and algorithm steps of each example 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 performed in hardware or software depends on the specific application and design constraints of the technical solution. Professional and technical personnel 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.

[0201] Those skilled in the art will clearly understand that, for the convenience and brevity of description, the specific working processes of the systems, devices and modules described above can refer to the corresponding processes in the aforementioned method embodiments and will not be repeated here.

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

[0203] The modules described as separate components may or may not be physically separate, and the components shown as modules may or may not be physical modules, that is, they may be located on a single device or distributed across multiple devices. Some or all of the modules may be selected to achieve the purpose of this embodiment based on actual needs.

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

[0205] In the above embodiments, all or part of the embodiments can be implemented by software, hardware, firmware, or any combination thereof. When implemented using a software program, all or part of the embodiments can be implemented in the form of a computer program product. The computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on a computer, all or part of the processes or functions described in the embodiments of the present application are generated. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer instructions can be stored in a computer storage medium or transmitted from one computer storage medium to another. For example, the computer instructions can be transmitted from one website, computer, server, or data center to another website, computer, server, or data center via a wired (e.g., coaxial cable, optical fiber, digital subscriber line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) method. The computer storage medium can be any available medium that can be accessed by a computer or a data storage device such as a server or data center that includes one or more media integrated therein. The available medium can be a magnetic medium (e.g., a floppy disk, a hard disk, a tape), an optical medium (e.g., a DVD), or a semiconductor medium (e.g., a solid state drive (SSD)).

[0206] The above description is merely a specific embodiment of the present application, but the scope of protection of the present application is not limited thereto. Any changes or substitutions that can be easily conceived by a person skilled in the art within the technical scope disclosed in this application should be included in the scope of protection of this application. Therefore, the scope of protection of this application should be based on the scope of protection of the claims.

Claims

1. A method for displaying a shortcut icon, characterized in that: Applied to electronic equipment, the method includes: Displaying a first interface, wherein the first interface includes a first desktop icon of a target application; At a first moment, in response to a click operation on the first desktop icon, starting the target application; updating the target application at a second moment, where the second moment is after the first moment; After the target application is updated, a second interface is displayed, wherein the second interface includes a second desktop icon of the target application; At a third moment, in response to a first operation on the second desktop icon, a first shortcut icon of the target application is displayed; the third moment is after the second moment, and no click operation on the second desktop icon is received between the second moment and the third moment, and the first shortcut icon corresponds to the first shortcut of the target application.

2. The method according to claim 1, characterized in that The first operation includes: a long press operation, or an operation of long press and dragging the border of the second desktop icon.

3. The method according to claim 1 or 2, characterized in that The first shortcut icon corresponds to the first shortcut of the target application before updating.

4. The method according to any one of claims 1 to 3, characterized in that At the third moment, in response to the first operation on the second desktop icon, after displaying the first shortcut icon of the target application, the method further includes: displaying a third interface, wherein the third interface includes the second desktop icon of the target application; At a fourth moment, in response to the first operation on the second desktop icon, displaying a second shortcut icon of the target application; Wherein, between the third moment and the fourth moment, the target application is started in response to a click operation on the second desktop icon, and the second shortcut corresponds to the first shortcut.

5. The method according to claim 4, characterized in that The second shortcut icon corresponds to the updated first shortcut of the target application.

6. The method according to any one of claims 1 to 5, characterized in that The method further comprises: In response to a click operation on the first desktop icon, obtaining and storing first shortcut information of the target application, wherein the first shortcut information indicates a correspondence between a shortcut of the target application and a shortcut icon; The step of displaying the first shortcut icon of the target application in response to the first operation on the second desktop icon at the third moment includes: At the third moment, in response to a first operation on the second desktop icon, a first shortcut icon of the target application is queried and displayed based on the first shortcut information.

7. The method according to claim 6, characterized in that The first shortcut information includes a correspondence between an application identifier of the target application, an identifier of a shortcut of the target application, and a shortcut icon, and the shortcut of the target application includes the first shortcut; The querying and displaying the first shortcut icon of the target application based on the first shortcut information includes: The first shortcut icon corresponding to the application identifier of the target application and the identifier of the first shortcut is searched and displayed.

8. The method according to claim 7, characterized in that The first shortcut information also includes the version number of the target application.

9. The method according to claim 4 or 5, characterized in that The method further comprises: At a fifth moment between the third moment and the fourth moment, in response to a click operation on the second desktop icon, obtaining and storing second shortcut information of the target application, wherein the second shortcut information indicates a correspondence between a shortcut of the target application and a shortcut icon; The step of displaying the second shortcut icon of the target application at the fourth moment in response to the first operation on the second desktop icon includes: At the fourth moment, in response to the first operation on the second desktop icon, a second shortcut icon of the target application is queried and displayed based on the second shortcut information.

10. The method according to claim 4 or 5, characterized in that The step of displaying the second shortcut icon of the target application at the fourth moment in response to the first operation on the second desktop icon includes: At the fourth moment, in response to the first operation on the second desktop icon, the second shortcut icon of the target application is acquired through an interface call and displayed.

11. The method according to claim 10, characterized in that The interface call includes calling through the package management PM interface.

12. An electronic device, characterized in that: The electronic device comprises one or more processors and a memory coupled to the processor; the memory stores computer program code, which includes instructions; when the instructions are executed by the processor, the electronic device executes the method according to any one of claims 1 to 11.

13. A computer-readable storage medium, characterized in that The method comprises instructions, which, when executed on an electronic device, cause the electronic device to execute the method according to any one of claims 1 to 11.

14. A computer program product, characterized in that The method comprises instructions, which, when executed on an electronic device, cause the electronic device to execute the method according to any one of claims 1 to 11.

Images