Application icon display method, electronic equipment and storage medium
By verifying the legality and effectiveness of the application icon, using PMS query startup interface logos, the problem of the disappearance of the icon of the clone application is solved, the normal display of the application icon is realized, and the user experience is improved.
Patent Information
- Application Number
- CN202410116198.3
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2024-01-26
- Publication Date
- 2025-08-05
AI Technical Summary
In electronic devices, after the user enables the app clone function, the application icon of the clone application may disappear for no reason, affecting the user's use.
By verifying the application icon associated with the application icon, ensuring the legality and effectiveness of the application icon, the PMS query startup interface logo is used to achieve accurate display.
Make sure the application icons are displayed normally on the desktop, avoid the problem of disappearing for no reason, and improve the user experience.
Smart Images

Figure CN120429856A_ABST
Abstract
Description
Technical Field
[0001] The present application relates to the field of computer technology, and in particular to an application icon display method, electronic device, and storage medium. Background Art
[0002] With the development of computer technology, electronic devices such as mobile phones and tablet computers have become increasingly popular and have become an indispensable part of people's daily lives. Users can install various applications on electronic devices to meet their needs.
[0003] Currently, users can use various features of an application by logging in to their account. In some cases, users may set up multiple accounts for the same application. To support users logging in to multiple accounts in the same application, the App Clone feature is provided.
[0004] After a user enables the app clone feature, the electronic device's desktop displays an icon for both the main application and the cloned application. The user can access the corresponding application through either icon and log in to their account to use it. However, in some cases, the cloned application's icon may disappear from the electronic device's desktop, which can affect user experience. Summary of the Invention
[0005] This application provides an application icon display method, electronic device, and storage medium, which can achieve normal display of application icons and avoid the problem of application icons disappearing on the desktop for no reason. The technical solution is as follows:
[0006] In a first aspect, a method for displaying an application icon is provided. In this method, an electronic device launches a desktop application. For any one of a plurality of application icons, the application icon is verified based on an application identifier associated with the application icon and a user identifier associated with the application icon. If the application icon passes verification, the application icon is displayed on the desktop; if the application icon fails verification, the application icon is not displayed on the desktop.
[0007] The multiple application icons are application icons that need to be displayed on the desktop. For example, the multiple application icons can be application icons in the target information of multiple applications saved by the desktop application. For example, the multiple application icons can include the application icon of the main application and the application icons of the clone applications corresponding to the main application.
[0008] The target information of an application may include the association relationship between the application ID, application icon, startup interface ID of the application and the user ID assigned to the application.
[0009] For an application icon in the target information of an application saved by a desktop application, the application identifier associated with the application icon is the application identifier in the target information, and the user identifier associated with the application icon is the user identifier in the target information.
[0010] In this application, the application icon can be verified based on the application program identifier associated with the application icon and the user identifier associated with the application icon. In this way, accurate verification of the application icon can be achieved, which helps to display the application icon normally and avoids the problem of application icons disappearing without reason on the desktop, thereby facilitating users to use the application normally and improving user experience.
[0011] For example, the verification of the application icon may be to verify the legitimacy and validity of the application icon.
[0012] In one possible implementation, the operation of the electronic device verifying the application icon based on the application identifier associated with the application icon and the user identifier associated with the application icon may be as follows: querying the startup interface identifier from the PMS based on the application identifier associated with the application icon and the user identifier associated with the application icon. If the startup interface identifier is not found, it is determined that the verification of the application icon has failed. If the startup interface identifier is found, then if the queried startup interface identifier is the same as the startup interface identifier associated with the application icon saved by the desktop application, it is determined that the verification of the application icon has passed; if the queried startup interface identifier is different from the startup interface identifier associated with the application icon saved by the desktop application, it is determined that the verification of the application icon has failed.
[0013] In this application, the startup interface identifier can be queried from the PMS based on the application identifier associated with the application icon and the user identifier associated with the application icon. This can achieve accurate query and then accurately verify the application icon.
[0014] In one possible implementation, the operation of the electronic device verifying the application icon based on the application identifier associated with the application icon and the user identifier associated with the application icon may be as follows: determining whether there is a corresponding application for the application icon based on the application identifier associated with the application icon and the user identifier associated with the application icon. If there is no corresponding application for the application icon, it is determined that the verification of the application icon has failed. If there is a corresponding application for the application icon, the startup interface identifier is queried from the PMS based on the application identifier associated with the application icon and the user identifier associated with the application icon; if the queried startup interface identifier is the same as the startup interface identifier associated with the application icon saved by the desktop application, it is determined that the verification of the application icon has passed; if the queried startup interface identifier is different from the startup interface identifier associated with the application icon saved by the desktop application, it is determined that the verification of the application icon has failed.
[0015] In this application, based on the application identifier and the user identifier associated with the application icon, it can be first determined whether the application icon has a corresponding application. If it is determined that the application icon has a corresponding application, the launch interface identifier is then queried from the PMS. This can save processing resources and improve verification efficiency. Furthermore, based on the application identifier and the user identifier associated with the application icon, the launch interface identifier is queried from the PMS, which can achieve accurate query and then accurately verify the application icon.
[0016] In one possible implementation, in response to an installation request for a first application, the electronic device assigns a first user identifier to the first application, and installs the first application in a user space corresponding to the first user identifier according to an installation package of the first application; the target information of the first application is saved in the PMS and the desktop application, and the target information of the first application includes the association between the application identifier, application icon, startup interface identifier and the first user identifier of the first application.
[0017] In this application, after the first application is installed, the target information of the first application is saved in both the PMS and the desktop application. This helps the desktop application to accurately verify the application icon of the first application when it is displayed on the desktop, thereby ensuring the legitimacy and validity of the displayed application icon.
[0018] In one possible implementation, in response to a received instruction to activate the application clone function of a first application, the electronic device uses the first application as the main application, assigns a second user identifier to the clone application of the main application, and installs the clone application in the user space corresponding to the second user identifier; the target information of the clone application is saved in the PMS and the desktop application, and the target information of the clone application includes the association between the application identifier, application icon, startup interface identifier and the second user identifier of the clone application.
[0019] In this application, after enabling the app clone feature for a first application, the PMS and desktop applications will both save the clone application's target information. This helps the desktop application accurately verify the clone application's app icon when displaying the desktop, thereby ensuring the legitimacy and validity of the displayed app icon.
[0020] In one possible implementation, in response to a received instruction to replace the application icon of a second application, the electronic device changes the application icon and startup interface identifier of the second application, where the second application is a main application or a clone application; and updates the target information of the second application saved in the PMS and the desktop application.
[0021] In this application, after the second application's application icon is replaced, the target information of the second application stored in the PMS and the desktop application is updated synchronously. This helps the desktop application to accurately verify the second application's application icon when displaying the desktop, thereby ensuring the legitimacy and validity of the displayed application icon.
[0022] In a possible implementation, after launching the desktop application, the electronic device may further determine whether there is an application icon of the clone application among the multiple application icons.
[0023] If there is an application icon of a clone application among the multiple application icons, each application icon can be verified based on the application identifier and user identifier associated with each application icon in the multiple application icons. Alternatively, if there is an application icon of a clone application among the multiple applications, the application icon of the clone application can be verified based on the application identifier and user identifier associated with the clone application icon. For application icons other than the application icon of the clone application, the application icon can be verified based on the user identifier associated with the desktop application and the application identifier associated with the application icon.
[0024] In the case that there is no application icon of the clone application in the multiple application icons, each application icon can be verified based on the user identifier associated with the desktop application and the application identifier associated with each application icon in the multiple application icons.
[0025] In this application, the verification method of the application icon can be flexibly selected according to the presence or absence of the application icon of the clone application, thereby improving the verification flexibility while ensuring the accuracy of the verification.
[0026] In a second aspect, an application icon display device is provided, wherein the application icon display device has the function of implementing the application icon display method described in the first aspect. The application icon display device includes at least one module, and the at least one module is used to implement the application icon display method described above.
[0027] In a third aspect, an electronic device is provided, which includes: one or more processors, and a memory; the memory is coupled to the one or more processors, the memory is used to store computer program code, the computer program code includes computer instructions, and the one or more processors call the computer instructions to enable the electronic device to execute the above-mentioned application icon display method.
[0028] In a fourth aspect, a chip system is provided, which is applied to an electronic device. The chip system includes one or more processors, and the one or more processors are used to call computer instructions to enable the electronic device to execute the above-mentioned application icon display method.
[0029] In a fifth aspect, a computer-readable storage medium is provided, which includes instructions. When the instructions are executed on an electronic device, the electronic device executes the above-mentioned application icon display method.
[0030] In a sixth aspect, a computer program product comprising instructions is provided, which, when executed on a computer, enables the computer to execute the above-mentioned application icon display method.
[0031] The technical effects obtained by the above-mentioned second, third, fourth, fifth and sixth aspects are similar to the technical effects obtained by the corresponding technical means in the above-mentioned first aspect, and will not be repeated here. BRIEF DESCRIPTION OF THE DRAWINGS
[0032] Figure 1 This is a schematic diagram of the structure of an electronic device provided in an embodiment of the present application;
[0033] Figure 2 This is a block diagram of a software system of an electronic device provided in an embodiment of the present application;
[0034] Figure 3This is a schematic diagram of a process for activating an application clone function provided in an embodiment of the present application;
[0035] Figure 4 This is a schematic diagram of a process for replacing an application icon provided in an embodiment of the present application;
[0036] Figure 5 This is a flowchart of an application icon display method provided in an embodiment of the present application. DETAILED DESCRIPTION
[0037] In the following description, specific details such as specific system structures and technologies are provided for illustration rather than limitation to facilitate a thorough understanding of the embodiments of the present application. However, it should be clear to those skilled in the art that the present application may also be implemented in other embodiments without these specific details.
[0038] It should be understood that when used in the specification and appended claims of this application, the term "comprising" indicates the presence of the described features, integers, steps, operations, elements and / or components, but does not exclude the presence or addition of one or more other features, integers, steps, operations, elements, components and / or their collections. The terms "including", "comprising", "having" and their variations all mean "including but not limited to", unless otherwise specifically emphasized.
[0039] It should be understood that the "one or more" mentioned in this application refers to one, two or more, and the "multiple" mentioned in this application refers to two or more. In the description of this application, unless otherwise specified, " / " means or, for example, A / B can mean A or B. The "and / or" in this article is only a way to describe the association relationship of associated objects, indicating that there can be three relationships. For example, A and / or B can mean: A exists alone, A and B exist at the same time, and B exists alone.
[0040] In addition, to facilitate a clear description of the technical solution of this application, the words "first" and "second" are used to distinguish between identical or similar items with substantially the same functions and effects. Those skilled in the art will understand that the words "first" and "second" do not limit the quantity or execution order, and the words "first" and "second" do not necessarily mean different.
[0041] The phrases "one embodiment" or "some embodiments" described in this application mean that the specific features, structures, or characteristics described in the embodiment are included in one or more embodiments of the application. Therefore, the phrases "in one embodiment," "in some embodiments," "in other embodiments," "in other embodiments," etc. that appear in different places in this application do not necessarily refer to the same embodiment, but rather mean "one or more but not all embodiments," unless otherwise specifically emphasized.
[0042] The application icon display method provided in the embodiments of the present application can be applied to electronic devices. The electronic devices can be mobile phones, tablet computers, wearable devices, digital cameras, vehicle-mounted devices, augmented reality (AR) devices, virtual reality (VR) devices, notebook computers, ultra-mobile personal computers (UMPCs), netbooks, personal digital assistants (PDAs), laptop computers, etc., and the embodiments of the present application are not limited thereto.
[0043] Figure 1 This is a schematic diagram of the structure of an electronic device provided by an embodiment of the present application. Figure 1 The electronic device 100 may include a processor 110, an external memory interface 120, an internal memory 121, a universal serial bus (USB) interface 130, a charging management module 140, a power management module 141, a battery 142, an antenna 1, an antenna 2, a mobile communication module 150, a wireless communication module 160, an audio module 170, a speaker 170A, a receiver 170B, a microphone 170C, an earphone interface 170D, a sensor module 180, a button 190, a motor 191, an indicator 192, a camera 193, a display screen 194, and a subscriber identification module (SIM) card interface 195, etc. Among them, the sensor module 180 can include a pressure sensor 180A, a gyroscope sensor 180B, an air pressure sensor 180C, a magnetic sensor 180D, an acceleration sensor 180E, a distance sensor 180F, a proximity light sensor 180G, a fingerprint sensor 180H, a temperature sensor 180J, a touch sensor 180K, an ambient light sensor 180L, a bone conduction sensor 180M, etc.
[0044] It should be understood that the structures illustrated in the embodiments of the present application do not constitute a specific limitation on the electronic device 100. In other embodiments of the present application, the electronic device 100 may include more or fewer components than shown, or may combine or separate certain components, or arrange the components differently. The illustrated components may be implemented in hardware, software, or a combination of software and hardware.
[0045] The processor 110 may include one or more processing units, for example, 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.
[0046] The controller may be the nerve center and command center of the electronic device 100. The controller may generate an operation control signal according to the instruction operation code and the timing signal to complete the control of fetching and executing instructions.
[0047] Processor 110 may also include a memory for storing instructions and data. In some embodiments, the memory in processor 110 is a cache memory. This memory can store instructions or data that have just been used or are being recycled by processor 110. If processor 110 needs to use the same instruction or data again, it can directly access the memory. This avoids duplicate accesses, reduces processor 110 latency, and thus improves system efficiency.
[0048] The external memory interface 120 can be used to connect an external memory card, such as a Micro SD card, to expand the storage capacity of the electronic device 100. The external memory card communicates with the processor 110 via the external memory interface 120 to implement data storage functions. For example, files such as music and videos can be stored on the external memory card.
[0049] The internal memory 121 can be used to store computer executable program codes, which include instructions. The processor 110 executes various functional applications and data processing of the electronic device 100 by running the instructions stored in the internal memory 121. The internal memory 121 may include a program storage area and a data storage area. Among them, the program storage area can store an operating system, an application required for at least one function (such as a sound playback function, an image playback function, etc.), etc. The data storage area can store data created by the electronic device 100 during use (such as audio data, a phone book, etc.), etc. In addition, the internal memory 121 may include a high-speed random access memory, and may also include a non-volatile memory, such as at least one disk storage device, a flash memory device, a universal flash storage (UFS), etc.
[0050] The wireless communication function of the electronic device 100 can be implemented through the antenna 1, the antenna 2, the mobile communication module 150, the wireless communication module 160, the modem processor and the baseband processor.
[0051] The mobile communication module 150 can provide solutions for wireless communications such as 2G / 3G / 4G / 5G applied to the electronic device 100. The wireless communication module 160 can provide solutions for wireless communications such as wireless local area networks (WLAN) (such as wireless fidelity (Wi-Fi) networks), Bluetooth (BT), global navigation satellite system (GNSS), frequency modulation (FM), near field communication (NFC), infrared technology (IR), etc. applied to the electronic device 100.
[0052] The electronic device 100 can implement audio functions, such as music playback and recording, through the audio module 170, the speaker 170A, the receiver 170B, the microphone 170C, the headphone jack 170D and the application processor.
[0053] The electronic device 100 can implement a shooting function through an ISP, a camera 193, a video codec, a GPU, a display screen 194, and an application processor.
[0054] The electronic device 100 implements the display function through a GPU, a display screen 194, and an application processor.
[0055] The GPU is a microprocessor for image processing that connects display screen 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. Display screen 194 is used to display images, videos, and the like.
[0056] The touch sensor 180K is also called a "touch panel." The touch sensor 180K can be disposed on the display screen 194. The touch sensor 180K and the display screen 194 form a touch screen, also called a "touch screen." The touch sensor 180K is used to detect touch operations applied thereto or in the vicinity thereof. The touch sensor 180K can transmit the detected touch operations to the application processor to determine the type of touch event. Visual output related to the touch operations can be provided via the display screen 194. In other embodiments, the touch sensor 180K can also be disposed on the surface of the electronic device 100, at a location different from that of the display screen 194.
[0057] Next, the software system of the electronic device 100 will be described.
[0058] The software system of the electronic device 100 can adopt a layered architecture, an event-driven architecture, a micro-kernel architecture, a microservice architecture, or a cloud architecture. In the embodiment of the present application, the software system of the electronic device 100 is exemplarily described by taking the Android system of the layered architecture as an example.
[0059] Figure 2 This is a block diagram of a software system of an electronic device 100 provided in an embodiment of the present application. Figure 2 The layered architecture divides software into several layers, each with distinct roles and responsibilities. Layers communicate with each other via software interfaces. In some embodiments, the Android system is divided into an application layer, an application framework layer, an Android runtime (Android Runtime), a system layer, and a kernel layer.
[0060] The application layer can include a series of applications (APPs). Figure 2 As shown, the application layer may include applications such as camera, calendar, gallery, Bluetooth, call, short message, desktop, settings, social, shopping, etc.
[0061] The application framework layer provides an application programming interface (API) and programming framework for the applications in the application layer. The application framework layer includes some predefined functions.
[0062] In some embodiments, as Figure 2As shown, the application framework layer may include a window manager, a content provider, a view system, a phone manager, a resource manager, a notification manager, and the like.
[0063] The window manager is used to manage window programs. It can obtain the display size, determine whether a status bar exists, lock the screen, take screenshots, and more. The content provider is used to store and retrieve data and make it accessible to applications. This data can include video, images, audio, incoming and outgoing calls, browsing history and bookmarks, and the phone book. The view system includes visual controls, such as those for displaying text and images. The view system can be used to construct the application's display interface, which can be composed of one or more views, such as a view that displays a text message notification icon, a view that displays text, and a view that displays images. The phone manager is used to provide communication functions for the electronic device 100, such as managing call status (including answering and hanging up). The resource manager provides various resources to applications, such as localized strings, icons, images, layout files, and video files. The notification manager enables applications to display notification information in the status bar. This can be used to convey notification-type messages and can remain on the screen for a short time before disappearing automatically, without requiring user interaction. For example, the notification manager is used to notify download completion, message reminders, and more. A notification manager can also be a notification that appears in the system's top status bar as an icon or scrolling text bar, such as a notification from an application running in the background. A notification manager can also be a notification that appears on the screen as a dialog window, such as a text message in the status bar, a beep, a vibration on an electronic device, a flashing indicator light, etc.
[0064] In some embodiments, as Figure 2 As shown, the application framework layer may include a user management service (UserManagerService, UMS), an activity management service (ActivityManagerService, AMS), and a package management service (PackageManagerService, PMS).
[0065] The UMS is a key component for implementing multi-user mechanisms. It handles the core logic of user management, including operations such as creating, deleting, and switching users. The AMS primarily manages the application lifecycle and task stack. It also schedules the launch and destruction of Activities and manages application processes and memory. Activities are components used to manage the user interface and handle user interactions. The PMS primarily manages application installation and uninstallation, as well as managing application permissions. It also provides detailed application information.
[0066] The Android Runtime consists of core libraries and a virtual machine (VM). The Android Runtime is responsible for scheduling and management of the Android system. The core libraries consist of two parts: one containing the Java language's callable functions and the other the Android core library. The application layer and the application framework layer run in the VM. The VM executes the Java files in the application layer and application framework layer as binary files. The VM is responsible for performing functions such as object lifecycle management, stack management, thread management, security and exception management, and garbage collection.
[0067] The system layer can include multiple functional modules, such as: surface manager, media library, 3D graphics processing library (such as OpenGL ES), 2D graphics engine (such as SGL), etc. The surface manager is used to manage the display subsystem and provides the fusion of 2D and 3D layers for multiple applications. The media library supports playback and recording of a variety of common audio and video formats, as well as static image files. The media library can support a variety of audio and video encoding formats, such as MPEG4, H.264, MP3, AAC, AMR, JPG, PNG, etc. The 3D graphics processing library is used to implement 3D graphics drawing, image rendering, synthesis, and layer processing. The 2D graphics engine is a drawing engine for 2D drawing.
[0068] The kernel layer is the layer between hardware and software. The kernel layer may include display drivers, camera drivers, audio drivers, sensor drivers, etc.
[0069] It should be noted that the embodiments of the present application do not particularly limit the specific structure of the execution subject of the application icon display method. As long as the code recording the application icon display method provided by the embodiments of the present application can be executed to perform processing according to the application icon display method provided by the embodiments of the present application. For example, the execution subject of the application icon display method provided by the embodiments of the present application can be a functional module in an electronic device that can call and execute a program, or it can be a processing device applied to the electronic device, such as a chip.
[0070] Next, the multi-user mechanism involved in the application icon display method provided in the embodiment of the present application is explained.
[0071] The multi-user mechanism allows an electronic device to be used by multiple different users, each with independent applications, settings, and data to ensure isolation between users.
[0072] Each user has a unique user identifier (ID) and a corresponding user space. Each user's application is installed in its own independent user space, and different users of the same application will not affect each other.
[0073] In the embodiments of the present application, the user space may refer to an independent storage space and operating environment allocated to a user. For example, each user's user space may include independent applications, application data, system settings, etc.
[0074] In some embodiments, when the electronic device is powered on for the first time, a master user identifier and a corresponding user space are created. During the operation of the electronic device, the electronic device may create slave user identifiers and corresponding user spaces as needed.
[0075] The embodiment of the present application can implement the application clone function based on the multi-user mechanism. The application clone function can support users to log in to multiple accounts of the same application in the electronic device.
[0076] Specifically, after a user turns on the app clone feature for an application, the electronic device can use the application as the main application and create a clone application for the main application. In this way, the user can log in to one account in the main application and log in to another account in the clone application.
[0077] Typically, when an electronic device installs an application, it assigns a default primary user ID to the application. Later, when the user enables the application's clone feature, the electronic device assigns a secondary user ID to the cloned application. In this case, the primary application runs in the user space corresponding to the primary user ID, while the clone runs in the user space corresponding to the secondary user ID. The two applications do not interfere with each other, allowing users to use both the primary and clone applications simultaneously.
[0078] Next, Figure 3 Take the example to illustrate the process of enabling the application clone function.
[0079] Figure 3 This is a schematic diagram of the process of activating the application clone function provided in an embodiment of the present application.
[0080] like Figure 3 As shown in FIG. 3 (a), the electronic device displays a desktop 301, and an application icon 31 of a social application and an application icon 32 of a setting application are displayed on the desktop 301. Assuming that the user clicks the application icon 32 of the setting application, then in response to the click operation, as shown in FIG. Figure 3As shown in FIG. 3 (b), the electronic device displays a setting interface 302, and an application setting item 33 is displayed in the setting interface 302. Afterwards, if the user clicks on the application setting item 33, then in response to the click operation, as shown in FIG. Figure 3 As shown in FIG. 3 (c), the electronic device displays an application setting interface 303, and an application clone setting item 34 is displayed in the application setting interface 303. Afterwards, if the user clicks on the application clone setting item 34, then in response to the click operation, Figure 3 As shown in FIG. 3 (d), the electronic device displays an application clone interface 304, which displays application clone switches for multiple applications, including an application clone switch 35 for a social application. Afterwards, assuming that the user turns on the application clone switch 35 for the social application, the electronic device turns on the application clone function of the social application in response to the turning-on operation, creates a clone application for the social application, and, as shown in FIG. Figure 3 As shown in Figure (e), the electronic device can display the application icon 31 of the main application and the application icon 36 of the clone application on the desktop 301.
[0081] In this case, the user can access the main application through the main application's application icon 31 and then log in to one account in the main application for use. Furthermore, the user can access the clone application through the clone application icon 36 and then log in to another account in the clone application for use. In this way, the user can log in to two accounts in the same social application for use.
[0082] It should be noted that the application icon 31 of the main application and the application icon 36 of the clone application can be exactly the same or slightly different. Figure 3 As shown in Figure (e), compared with the application icon 31 of the main application, the application icon 36 of the clone application has an additional mark 2 in the lower right corner, so that the user can clearly know which is the main application and which is the clone application.
[0083] It should be noted that the above Figure 3 The process shown is only an exemplary description of a possible implementation method for enabling the application clone function of an application, and does not constitute a limitation on the embodiments of the present application. In actual applications, the application clone function of an application can also be enabled through other methods.
[0084] In some cases, when the user does not turn off the application clone function of the application, the application icon of the clone application displayed on the desktop will disappear, seriously affecting the user's normal use.
[0085] For example, in some scenarios, social applications provide users with icon replacement functions. Figure 4As shown in FIG. 3 (a), a user can change the application icon of a social application in the icon setting interface 305 of the social application. The icon setting interface 305 displays multiple icons, including a default icon and other icons that can be changed. If the user chooses to change the default icon to icon 37 in the icon setting interface 305, the application icon of the social application displayed on the desktop 301 will be icon 37.
[0086] When the app clone function of a social application is enabled, if the user changes the app icon in the main application but not in the clone application, then Figure 4 As shown in FIG. 3( b ), the main application's application icon displayed on desktop 301 is the replaced icon 37, while the clone application's application icon remains the default icon 36. If the user changes the application icon in the clone application but does not change the application icon in the main application, the main application's application icon displayed on desktop 301 remains the default icon 31, while the clone application's application icon is the replaced icon 37.
[0087] In the case where the user changes the application icon of the main application or the application icon of the clone application, if the desktop 301 is restarted due to reasons such as restarting the electronic device, then Figure 4 As shown in Figure (c) in the figure, the application icon of the clone application displayed on the desktop 301 will disappear. This will cause the user to be unable to use the clone application. The cause of this problem will be analyzed below.
[0088] In some embodiments, the PMS includes detailed information about an application. The detailed information about an application may include information such as the application identifier (including but not limited to the application package name), the application icon, interface information, the user identifier associated with the application (i.e., the user identifier assigned to the application), and so on. The interface information may include a launcher interface identifier. For example, the launcher interface identifier may be the name of a launcher activity, such as the class name of MainActivity. The launcher interface is the entry point for the application. The launcher interface is typically the main interface of the application and the starting point for user interaction with the application.
[0089] In some embodiments, the database of the desktop application contains relevant information of the application icons on the desktop. The relevant information of an application icon may include the application icon and the application identifier, startup interface identifier, user identifier, etc. associated with the application icon.
[0090] Each time the desktop is started, the desktop application needs to load all application icons on the desktop. In related technologies, for each application icon, the desktop application uses the user ID associated with the desktop application (generally the primary user ID) and the application ID associated with the application icon to query the startup interface ID from the PMS. Afterwards, the desktop application determines whether the startup interface ID retrieved from the PMS is the same as the startup interface ID associated with the application icon in the desktop application database; if they are the same, it is determined that the application icon has passed verification and the application icon is displayed on the desktop; if they are different, it is determined that the application icon has failed verification and the application icon is not displayed on the desktop.
[0091] After enabling the app clone feature for an app, the main app's app ID and the clone's app ID are identical, their launcher interface IDs are also identical, and their app icons may be identical or slightly different. However, their associated user IDs are different. The user ID associated with the main app is typically the primary user ID, while the user ID associated with the clone is typically the secondary user ID.
[0092] However, when a user changes the app icon in an application (either the main app or a clone), the app not only changes the app icon but also changes the startup screen logo accordingly. It should be noted that the startup screen logo after the change is different from the startup screen logo before the change, and the screens identified by the two can be the same or slightly different.
[0093] If the user does not change the application icons of the main application and the clone application, the main application's startup interface identifier and the clone application's startup interface identifier are the same. Assume that the information about the applications included in the PMS is as shown in Table 1 below. The second row of data in Table 1 is information about the main application; the third row of data in Table 1 is information about the clone application. User ID 0 in Table 1 is the main user ID.
[0094] Table 1
[0095] Application ID App Icon Startup interface logo User ID Application ID A Application Icon A Startup interface logo A User ID 0 Application ID A Application Icon B Startup interface logo A User ID 1 …… …… …… ……
[0096] In the embodiment of the present application, only the relevant information of the application included in the PMS is exemplarily described by taking Table 1 above as an example. Table 1 above does not limit the embodiment of the present application.
[0097] Accordingly, the relevant information of the application icons contained in the database of the desktop application is shown in Table 2 below.
[0098] Table 2
[0099] App Icon Application ID Startup interface logo User ID Application Icon A Application ID A Startup interface logo A User ID 0 Application Icon B Application ID A Startup interface logo A User ID 1 …… …… …… ……
[0100] In the embodiment of the present application, only the above Table 2 is used as an example to exemplify the relevant information of the application icon contained in the database of the desktop application. The above Table 2 does not limit the embodiment of the present application.
[0101] Assuming that the user identifier associated with the desktop application is the primary user identifier, that is, user identifier 0, when the desktop is started, the desktop application queries the startup interface identifier from the PMS based on the user identifier 0 associated with the desktop application and the application identifier associated with each application icon. Specifically, for application icon A in Table 2 above, the desktop application queries the startup interface identifier A from Table 1 in the PMS based on the user identifier 0 and the application identifier A associated with application icon A in Table 2. If the startup interface identifier A is the same as the startup interface identifier A associated with application icon A in Table 2, the desktop application determines that application icon A has been verified successfully and displays application icon A on the desktop. For application icon B in Table 2 above, the desktop application queries the startup interface identifier A from Table 1 in the PMS based on the user identifier 0 and the application identifier A associated with application icon B in Table 2. If the startup interface identifier A is the same as the startup interface identifier A associated with application icon B in Table 2, the desktop application determines that application icon B has been verified successfully and displays application icon B on the desktop.
[0102] However, after the user changes the main application's app icon or the clone's app icon, the main application's startup interface identifier and the clone's startup interface identifier become different. Assuming the user changes the main application's app icon, the relevant information about the applications included in the PMS is shown in Table 3 below. The second row of data in Table 3 contains relevant information about the main application, whose app icon changes from App Icon A to App Icon C, and whose startup interface identifier changes from Startup Interface Identifier A to Startup Interface Identifier C. The third row of data in Table 3 contains relevant information about the clone. User ID 0 in Table 3 is the main user ID.
[0103] Table 3
[0104] Application ID App Icon Startup interface logo User ID Application ID A Application Icon C Startup interface logo C User ID 0 Application ID A Application Icon B Startup interface logo A User ID 1 …… …… …… ……
[0105] In the embodiment of the present application, only the relevant information of the application included in the PMS is exemplified by taking Table 3 above as an example. Table 3 above does not limit the embodiment of the present application.
[0106] Accordingly, the relevant information of the application icons contained in the database of the desktop application is shown in Table 4 below.
[0107] Table 4
[0108] App Icon Application ID Startup interface logo User ID Application Icon C Application ID A Startup interface logo C User ID 0 Application Icon B Application ID A Startup interface logo A User ID 1 …… …… …… ……
[0109] In the embodiment of the present application, only the above Table 4 is used as an example to exemplify the relevant information of the application icon contained in the database of the desktop application. The above Table 4 does not limit the embodiment of the present application.
[0110] Then, when the desktop is started, the desktop application queries the startup interface identifier from the PMS based on the user identifier 0 associated with the desktop application and the application identifier associated with each application icon. Specifically, for application icon C in Table 4 above, the desktop application queries the startup interface identifier C from Table 3 in the PMS based on the user identifier 0 and the application identifier A associated with application icon C in Table 4. If the startup interface identifier C is the same as the startup interface identifier C associated with application icon C in Table 4, the desktop application determines that application icon C has passed verification and displays application icon C on the desktop. For application icon B in Table 4 above, the desktop application queries the startup interface identifier C from Table 3 in the PMS based on the user identifier 0 and the application identifier A associated with application icon B in Table 4. If the startup interface identifier C is different from the startup interface identifier A associated with application icon B in Table 4, the desktop application determines that application icon B has failed verification and does not display application icon B on the desktop. This causes the application icon B of the clone application to disappear from the desktop after the desktop is started, thereby preventing the user from using the clone application.
[0111] To this end, an embodiment of the present application provides an application icon display method to solve the problem of application icons disappearing when the desktop is started, so that the application icons can be displayed normally on the desktop, facilitating users to use the application normally and improving the user experience.
[0112] The following combination Figure 2 The software system of the electronic device shown is used to explain the embodiments of the present application in detail.
[0113] In some embodiments, an electronic device receives an installation request for a first application. In response to the installation request, the electronic device may assign a first user identifier to the first application and then install the first application in the user space corresponding to the first user identifier using the installation package of the first application. After the first application is installed, the PMS and the desktop application store target information for the first application. The target information for the first application may include an association between the first application identifier, application icon, and launch interface identifier of the first application and the first user identifier.
[0114] The first application may be an application installed by a user during the use of the electronic device, or may be a system application preset by the electronic device, which is not limited in this embodiment of the present application.
[0115] The installation package of the first application may be an Android application package (APK), etc., which is not limited in this embodiment of the present application.
[0116] The installation request for the first application can be triggered in a variety of ways. For example, the user can search and select the first application to be installed in the application market application, and then click the install button to trigger the installation request for the first application. In this case, the application market application will automatically download the installation package of the first application after receiving the installation request. Alternatively, the user can download the installation package of the first application from a website, etc., and then start the installation process to trigger the installation request for the first application. Alternatively, in the case where the first application is a system application, the electronic device is pre-installed with the installation package of the first application when it leaves the factory. In this case, the electronic device can automatically trigger the installation request for the first application when it is turned on for the first time.
[0117] For example, the first user identifier may be a primary user identifier.
[0118] In some cases, the first user identifier can also be another user identifier. For example, when the electronic device has a privacy space enabled, the user identifier corresponding to the main space can be the primary user identifier, and the user identifier corresponding to the privacy space can be the privacy user identifier. In this case, if the installation request for the first application is triggered in the main space, the first user identifier can be the primary user identifier; if the installation request for the first application is triggered in the privacy space, the first user identifier can be the privacy user identifier.
[0119] For example, after the electronic device receives an installation request for the first application, the UMS can assign a first user identifier to the first application. The PMS can decompress the installation package of the first application to obtain the installation file of the first application, and then install the first application in the user space corresponding to the first user identifier according to the installation file of the first application. The PMS can obtain the target information of the first application during the installation of the first application. After the installation of the first application is completed, the PMS can notify the desktop application of the target information of the first application. After the desktop application receives the target information of the first application, it can save the target information of the first application in the database of the desktop application. In this case, if Figure 3 As shown in FIG. 5( a ) , the desktop application can display an application icon 31 of the first application on the desktop 301 .
[0120] In the embodiment of the present application, after the first application is installed, the target information of the first application is saved in both the PMS and the desktop application. This helps the desktop application to accurately verify the application icon of the first application when it is subsequently displayed on the desktop, thereby ensuring the legitimacy and validity of the displayed application icon.
[0121] In some embodiments, the electronic device receives an uninstall request for the first application and, in response to the uninstall request, uninstalls the first application from the user space corresponding to the first user identifier. After the first application is uninstalled, target information of the first application stored in the PMS and the desktop application is also deleted.
[0122] For example, after the electronic device receives an uninstall request for the first application, the PMS can uninstall the first application from the user space corresponding to the first user identifier. Afterwards, the PMS can notify the desktop application of the uninstall message of the first application (which can carry the application identifier of the first application and the first user identifier) and delete the relevant information of the first application (including the target information of the first application). After receiving the uninstall message of the first application, the desktop application can delete the target information of the first application in the database, and the desktop application no longer displays the application icon of the first application on the desktop.
[0123] In some embodiments, the electronic device receives an instruction to enable the application clone function of a first application. In response to the instruction, the electronic device uses the first application as the primary application, assigns a second user identifier to the primary application's clone, and installs the clone in the user space corresponding to the second user identifier. After the clone is installed, the PMS and desktop application store target information for the clone, which may include an association between the clone's application identifier, application icon, and launch interface identifier, and the second user identifier.
[0124] The instruction to enable the application clone function of the first application can be triggered in a variety of ways. For example, Figure 3 As shown in Figure (d), when the user turns on the application clone switch 35 of the first application in the electronic device, it will trigger an instruction to turn on the application clone function of the first application.
[0125] The second user identifier is different from the first user identifier. For example, if the first user identifier is a primary user identifier, the second user identifier may be a secondary user identifier. Alternatively, if the first user identifier is a private user identifier, the second user identifier may be a private secondary user identifier.
[0126] For example, after the electronic device receives an instruction to enable the application clone function of the first application, the UMS can assign a second user identifier to the clone application of the first application. The PMS can install the clone application in the user space corresponding to the second user identifier based on the installation file of the first application. The PMS can obtain the target information of the clone application during the installation of the clone application. After the installation of the clone application is completed, the PMS can notify the desktop application of the target information of the clone application. After the desktop application receives the target information of the clone application, it can save the target information of the clone application in the database of the desktop application. In this case, if Figure 3 As shown in Figure (e), the desktop application can display the application icon 36 of the clone application on the desktop 301.
[0127] In this embodiment of the present application, after the first application's app clone function is enabled, the PMS and desktop applications will both save the clone application's target information. This helps the desktop application accurately verify the clone application's app icon when it is subsequently displayed on the desktop, thereby ensuring the legitimacy and validity of the displayed app icon.
[0128] In some embodiments, the electronic device receives a command to disable the application clone function of the first application. In response to the command, the electronic device uninstalls the clone application from the user space corresponding to the second user identifier. After the clone application is uninstalled, the target information of the clone application stored in the PMS and desktop application is also deleted.
[0129] The instruction to turn off the application clone function of the first application can be triggered in a variety of ways. For example, the user can turn off the application clone switch of the first application in the electronic device to trigger the instruction to turn off the application clone function of the first application.
[0130] For example, after the electronic device receives a command to close the application clone function of the first application, the PMS can uninstall the clone application from the user space corresponding to the second user identifier. Afterwards, the PMS can notify the desktop application of the uninstall message of the clone application (which can carry the application identifier of the clone application and the second user identifier) and delete the relevant information of the clone application (including the target information of the clone application). After the desktop application receives the uninstall message of the clone application, it can delete the target information of the clone application in the database, and the desktop application no longer displays the application icon of the clone application on the desktop.
[0131] For example, if the main app is uninstalled, its clone app will also be uninstalled. However, uninstalling the clone app will not affect the main app, that is, even if the clone app is uninstalled, the main app will continue to exist and run normally.
[0132] As an example, the electronic device can distinguish the identifier (including but not limited to the icon name, etc.) of the clone application's application icon from the identifiers of other application icons (such as the main application or other applications that do not have the clone function enabled). The desktop application can thus distinguish which application icons are the clone application's application icons.
[0133] For example, the identifier of the application icon of the clone application may include a preset string, while the identifiers of the application icons of other applications may not include the preset string. The preset string can be pre-set, such as the preset string "clone", etc., which is not limited in this embodiment of the application. Then, the desktop application can determine that the application icon whose identifier includes the preset string is the application icon of the clone application.
[0134] In some embodiments, the electronic device receives an instruction to replace the application icon of the second application. In response to the instruction, the electronic device changes the application icon and launch interface identifier of the second application, and updates the target information of the second application saved by the PMS and the desktop application.
[0135] The second application can be the main application, or can be a clone application, or can be other applications that do not have the application clone function enabled. This embodiment of the present application does not limit this.
[0136] The instruction to replace the application icon of the second application can be triggered in a variety of ways. For example, if the user wants to replace the application icon of the second application, Figure 4 As shown in FIG. 3 , the user can select the icon 37 that he wants to replace in the icon setting interface 305 of the second application to trigger a replacement instruction, which is used to instruct to replace the application icon of the second application with the icon 37 .
[0137] The target information of the second application includes an application identifier, an application icon, a startup interface identifier of the second application, and an association relationship among a user identifier allocated to the second application.
[0138] In this embodiment of the present application, after the second application's application icon is replaced, the target information of the second application stored in the PMS and the desktop application is updated synchronously. This helps the desktop application accurately verify the second application's application icon when it is subsequently displayed on the desktop, thereby ensuring the legitimacy and validity of the displayed application icon.
[0139] For example, after the electronic device receives an instruction to replace the application icon of the second application, the second application can update the application icon of the second application to the icon indicated by the replacement instruction, and can update the startup interface identifier of the second application to the target interface identifier. The target interface identifier can be set in advance. For example, the target interface identifier can be a pre-set interface identifier corresponding to the icon indicated by the replacement instruction. Afterwards, the second application can notify the PMS of the updated application icon and startup interface identifier. After the PMS receives the application icon and startup interface identifier of the second application sent by the second application, it can update the target information of the second application accordingly, and notify the desktop application of the updated target information of the second application. After the desktop application receives the target information of the second application, it can update the target information of the second application in the database accordingly. In this case, if Figure 4 As shown in FIG. 5( b ) , the desktop application may display the replaced application icon of the second application on the desktop, which is icon 37 in this case.
[0140] It can be understood that the above is only an exemplary description of a possible implementation method of the application installation and uninstallation process, the application clone function activation and deactivation process, and the application icon replacement process. In actual applications, the installation and uninstallation of the application, the activation and deactivation of the application clone function, and the application icon replacement process can also be achieved through other methods. The embodiments of the present application do not limit this.
[0141] Regardless of the method used, after installing or uninstalling an application, or after turning on or off the application clone function of an application, or after changing the application icon of an application, the target information of the application saved by the PMS and the target information of the application saved by the desktop application will be updated synchronously, and the desktop application can display the application icon on the desktop accordingly.
[0142] Figure 5 This is a flow chart of an application icon display method provided by an embodiment of the present application. Figure 5 , the method may include the following steps:
[0143] Step 501: The electronic device starts a desktop application.
[0144] The desktop application can be started in a variety of situations. For example, the desktop application can be started when the electronic device is restarted, or when the system is updated, or when the desktop application stops responding. Of course, the desktop application can also be started in other situations, and the embodiments of the present application are not limited to this.
[0145] Step 502: For any one of the multiple application icons, the electronic device verifies the application icon according to the application program identifier associated with the application icon and the user identifier associated with the application icon.
[0146] By way of example, step 502 may be performed by a desktop application.
[0147] The multiple application icons are application icons that need to be displayed on the desktop. For example, the multiple application icons can be application icons in the target information of multiple applications saved by the desktop application. For example, the multiple application icons can include the application icon of the main application and the application icons of the clone applications corresponding to the main application.
[0148] For the application icon in the target information of an application saved by a desktop application, the application identifier associated with the application icon is the application identifier in the target information, and the user identifier associated with the application icon is the user identifier in the target information, which is the user identifier assigned to the application.
[0149] For example, the verification of the application icon may be to verify the legitimacy and validity of the application icon.
[0150] In some embodiments, step 502 may be implemented in the following two ways:
[0151] The first possible method is: the electronic device queries the startup interface identifier from the PMS based on the application identifier associated with the application icon and the user identifier associated with the application icon. If the startup interface identifier is not found, it is determined that the application icon verification has failed. If the startup interface identifier is found, then if the queried startup interface identifier is the same as the startup interface identifier associated with the application icon saved by the desktop application, it is determined that the application icon verification has passed; if the queried startup interface identifier is different from the startup interface identifier associated with the application icon saved by the desktop application, it is determined that the application icon verification has failed.
[0152] The PMS stores detailed information about applications installed in the electronic device.
[0153] For example, after obtaining the application identifier and user identifier associated with the application icon from its own database, the desktop application can send a query message to the PMS, carrying the application identifier and user identifier. Upon receiving the query message, the PMS can search for the launch screen identifier associated with the application identifier and user identifier from the detailed information of installed applications. If the PMS fails to find the launch screen identifier, it returns a query failure message to the desktop application, indicating that the launch screen identifier was not found. If the PMS finds the launch screen identifier, it returns a query result to the desktop application, carrying the found launch screen identifier.
[0154] If the startup interface identifier is not queried from the PMS based on the application identifier associated with this application icon and the user identifier associated with this application icon, it means that the PMS has not saved the startup interface identifier associated with the application identifier and the user identifier, which means that the application corresponding to this application icon does not exist. Then it can be determined that this application icon is illegal, and then it can be determined that this application icon verification has failed.
[0155] If the startup interface identifier is queried from the PMS based on the application identifier associated with this application icon and the user identifier associated with this application icon, it means that the PMS has saved the startup interface identifier associated with the application identifier and the user identifier, which means that the application corresponding to this application icon exists. Then it can be determined that this application icon is legal, and then it can be determined whether this application icon is valid.
[0156] If the startup interface identifier queried from the PMS is the same as the startup interface identifier associated with this application icon in the desktop application database, it means that the startup interface identifier associated with this application icon saved by the PMS and the desktop application is consistent, then it can be determined that this application icon is valid, and then it can be determined that this application icon has passed the verification.
[0157] If the startup interface identifier queried from the PMS is different from the startup interface identifier associated with the application icon in the desktop application database, it means that the startup interface identifier associated with the application icon saved by the PMS and the desktop application is inconsistent. Then it can be determined that the application icon is invalid and there is an abnormality, and then it can be determined that the application icon verification has failed.
[0158] In an embodiment of the present application, the startup interface identifier can be queried from the PMS based on the application identifier associated with the application icon and the user identifier associated with the application icon. In this way, accurate query can be achieved, and then accurate verification of the application icon can be achieved.
[0159] The second possible way: The electronic device determines whether there is a corresponding application for this application icon based on the application identifier associated with this application icon and the user identifier associated with this application icon. If there is no corresponding application for this application icon, it is determined that the verification of this application icon has failed. If there is a corresponding application for this application icon, the startup interface identifier is queried from the PMS based on the application identifier associated with this application icon and the user identifier associated with this application icon; if the queried startup interface identifier is the same as the startup interface identifier associated with this application icon saved by the desktop application, it is determined that the verification of this application icon has passed; if the queried startup interface identifier is different from the startup interface identifier associated with this application icon saved by the desktop application, it is determined that the verification of this application icon has failed.
[0160] As an example, the operation of the electronic device to determine whether there is a corresponding application for the application icon based on the application identifier associated with the application icon and the user identifier associated with the application icon may be as follows: after the desktop application obtains the application identifier associated with the application icon and the user identifier associated with the application icon in its own database, it sends an inquiry message to the PMS, where the inquiry message carries the application identifier and the user identifier, inquiring whether there is a corresponding application for the application identifier and the user identifier. After receiving the inquiry message, the PMS determines whether there is an application among the installed applications that corresponds to the application identifier and the user identifier; if there is an application that corresponds to the application identifier and the user identifier, a first inquiry result is returned to the desktop application to indicate that a corresponding application exists; if there is no application that corresponds to the application identifier and the user identifier, a second inquiry result is returned to the desktop application to indicate that there is no corresponding application.
[0161] In an embodiment of the present application, based on the application ID and the user ID associated with the application icon, it is first determined whether the application icon corresponds to an application. If it is determined that the application icon corresponds to an application, the launch interface ID is then queried from the PMS. This saves processing resources and improves verification efficiency. Furthermore, based on the application ID and the user ID associated with the application icon, the launch interface ID is queried from the PMS, which enables accurate query and, subsequently, accurate verification of the application icon.
[0162] In some embodiments, after launching the desktop application, the electronic device may also determine whether there is an application icon for the clone application among the multiple application icons.
[0163] If an application icon of a clone application exists among the multiple application icons, each of the multiple application icons may be verified according to the aforementioned step 502. Alternatively, if an application icon of a clone application exists among the multiple applications, the application icon of the clone application may be verified according to the aforementioned step 502. For application icons other than the application icon of the clone application, the application icon may be verified based on the user identifier associated with the desktop application and the application identifier associated with the application icon. The specific process is similar to the aforementioned step 502 and will not be further described in this embodiment of the application.
[0164] In the case that there is no application icon of the clone application among the multiple application icons, each application icon can be verified based on the user identifier associated with the desktop application and the application identifier associated with each application icon in the multiple application icons. The specific process is similar to the above step 502 and will not be repeated in this embodiment of the present application.
[0165] In the embodiment of the present application, the verification method of the application icon can be flexibly selected according to the presence or absence of the application icon of the clone application, thereby improving the verification flexibility while ensuring the verification accuracy.
[0166] Step 503: If the application icon passes the verification, the electronic device displays the application icon on the desktop; if the application icon fails the verification, the electronic device does not display the application icon on the desktop.
[0167] For example, step 503 may be performed by a desktop application.
[0168] For example, the desktop application can also save the position information of the application icon on the desktop. The desktop application can display the application icon at a corresponding position on the desktop according to the position information of the application icon.
[0169] In an embodiment of the present application, the application icon can be verified based on the application program identifier associated with the application icon and the user identifier associated with the application icon. In this way, accurate verification of the application icon can be achieved, which helps to display the application icon normally and avoids the problem of application icons disappearing without reason on the desktop, thereby facilitating users to use the application normally and improving user experience.
[0170] The electronic device displays multiple application icons on the desktop, and the user can use corresponding application programs based on each displayed application icon.
[0171] In some embodiments, after displaying the desktop, the electronic device may receive a click operation on an application icon on the desktop. In response to the click operation, the electronic device may display the interface of the application corresponding to the application icon.
[0172] For example, after a desktop application receives a click operation on an application icon on the desktop, it can obtain the application identifier, startup interface identifier, and user identifier associated with the application icon stored in the database of the desktop application, and then send an application startup message to the AMS. The application startup message carries the application identifier, startup interface identifier, and user identifier.
[0173] After receiving the application start message, AMS can determine whether the application identified by the application identifier in the user space corresponding to the user identifier has been started based on the application identifier and the user identifier. For example, it can determine whether the process of the application is running in the user space corresponding to the user identifier.
[0174] If the application is not started, the AMS can create a process for the application in the user space corresponding to the user ID to start the application. The AMS can then display the corresponding startup interface through the application based on the startup interface identifier. For example, the AMS can create a corresponding activity in the application process based on the startup interface identifier to display the startup interface.
[0175] If the application has been started and is running in the background, the AMS may switch the application to the foreground and display a corresponding startup interface through the application according to the startup interface identifier.
[0176] It should be understood that the size of the serial numbers of the steps in the above embodiments 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 this application.
[0177] In the above embodiments, the description of each embodiment has its own focus. For parts that are not described or recorded in detail in a certain embodiment, reference can be made to the relevant description of other embodiments.
[0178] An embodiment of the present application further provides a computer-readable storage medium, which stores a computer program. When the computer program is executed by a processor, the steps in the above-mentioned method embodiments can be implemented.
[0179] An embodiment of the present application further provides a computer program product. When the computer program product is run on an electronic device, the electronic device can implement the steps in the above-mentioned various method embodiments.
[0180] The present application also provides a chip system, comprising a processor coupled to a memory, the processor executing a computer program stored in the memory to implement the steps of any method embodiment of the present application. The chip system can be a single chip or a chip module composed of multiple chips.
[0181] In the above embodiments, it can be implemented in whole or in part by software, hardware, firmware or any combination thereof. When implemented using software, it can be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer instructions. When the computer instructions are loaded and executed on a computer, the process or function described in the embodiment of the present application is generated in whole or in part. 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-readable storage medium, or transmitted from one computer-readable storage medium to another computer-readable storage medium. For example, the computer instructions can be transmitted from a website, computer, server or data center to another website, computer, server or data center via a wired (such as a coaxial cable, optical fiber, digital subscriber line (DSL)) or wireless (such as infrared, wireless, microwave, etc.) method. The computer-readable storage medium can be any available medium that a computer can access, or a data storage device such as a server or data center that includes one or more available media integrations. The available medium may be a magnetic medium (eg, a floppy disk, a hard disk, a magnetic tape), an optical medium (eg, a digital versatile disc (DVD)), or a semiconductor medium (eg, a solid state disk (SSD)).
[0182] The above are optional embodiments provided for this application and are not intended to limit this application. Any modifications, equivalent replacements, improvements, etc. made within the technical scope disclosed in this application should be included in the scope of protection of this application.
Claims
1. A method for displaying an application icon, characterized in that: The method comprises: Launch the desktop application; For any one of the plurality of application icons, verifying the one application icon according to an application program identifier associated with the one application icon and a user identifier associated with the one application icon; If the application icon passes the verification, the application icon is displayed on the desktop; If the verification of the application icon fails, the application icon is not displayed on the desktop.
2. The method according to claim 1, wherein The verifying the application icon according to the application program identifier associated with the application icon and the user identifier associated with the application icon includes: querying a startup interface identifier from a package management service PMS according to an application identifier associated with the one application icon and a user identifier associated with the one application icon; If no startup interface identifier is found, it is determined that the verification of the one application icon has failed; If a startup interface identifier is queried, then if the queried startup interface identifier is the same as the startup interface identifier associated with the application icon saved by the desktop application, it is determined that the verification of the application icon has passed; if the queried startup interface identifier is different from the startup interface identifier associated with the application icon saved by the desktop application, it is determined that the verification of the application icon has failed.
3. The method according to claim 1, wherein The verifying the application icon according to the application program identifier associated with the application icon and the user identifier associated with the application icon includes: Determining whether a corresponding application exists for the application icon according to an application program identifier associated with the application icon and a user identifier associated with the application icon; If there is no corresponding application program for the one application icon, determining that the one application icon verification fails; If there is a corresponding application for the application icon, the startup interface identifier is queried from the PMS based on the application identifier associated with the application icon and the user identifier associated with the application icon; if the queried startup interface identifier is the same as the startup interface identifier associated with the application icon saved by the desktop application, it is determined that the verification of the application icon has passed; if the queried startup interface identifier is different from the startup interface identifier associated with the application icon saved by the desktop application, it is determined that the verification of the application icon has failed.
4. The method according to any one of claims 1 to 3, characterized in that The multiple application icons include an application icon of a main application and an application icon of a clone application corresponding to the main application.
5. The method according to any one of claims 1 to 4, characterized in that The method further comprises: In response to an installation request for a first application, allocating a first user identifier to the first application, and installing the first application in a user space corresponding to the first user identifier according to an installation package of the first application; The target information of the first application is saved in the PMS and the desktop application, where the target information of the first application includes an association relationship between the application identifier, application icon, startup interface identifier of the first application and the first user identifier.
6. The method according to claim 5, wherein The method further comprises: In response to a received instruction to enable the application clone function of the first application, use the first application as a main application, assign a second user identifier to the clone application of the main application, and install the clone application in a user space corresponding to the second user identifier; The target information of the clone application is saved in the PMS and the desktop application, where the target information of the clone application includes an association relationship between the application identifier, application icon, startup interface identifier of the clone application and the second user identifier.
7. The method according to claim 6, wherein The method further comprises: In response to a received instruction to change an application icon of a second application, changing the application icon and a startup interface identifier of the second application, where the second application is the main application or the clone application; The target information of the second application stored in the PMS and the desktop application is updated.
8. The method according to any one of claims 1 to 7, characterized in that The step of verifying any one of the plurality of application icons according to an application program identifier associated with the application icon and a user identifier associated with the application icon includes: If an application icon of a clone application exists among the multiple application icons, then for any one of the multiple application icons, the one application icon is verified according to the application identifier associated with the one application icon and the user identifier associated with the one application icon.
9. An electronic device, characterized in that: The electronic device 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, where the computer program code includes computer instructions. The one or more processors call the computer instructions to enable the electronic device to execute the method according to any one of claims 1 to 8.
10. A computer-readable storage medium, characterized in that The computer-readable storage medium comprises instructions, which, when executed on an electronic device, cause the electronic device to perform the method according to any one of claims 1 to 8.
Citation Information
Patent Citations
Method for simultaneously starting multiple identical application programs of Android system
CN106095603A
Application starting method and device and mobile terminal
CN108628644A
Duplicate setting method and device, electronic equipment and readable storage medium
CN110888724A
Application program control method and device and storage medium
CN112783579A
Space management method and device, electronic equipment and readable storage medium
CN114637441A