Application management method and device, electronic equipment and computer readable storage medium

Abstract

The embodiment of the invention discloses an application management method and device, electronic equipment and a computer readable storage medium, and relates to the technical field of computers. The method comprises the following steps: in response to a custom operation for triggering a hiding function in a target interface, displaying a hiding function interface; the hidden function interface comprises a hidden application interface; and in response to a hiding operation on the first application on the application hiding interface, simultaneously performing desktop hiding and system-level hiding on the first application. In this way, desktop hiding and system-level hiding of the application can be conveniently achieved, and privacy protection of the hidden application is high.

Description

Technical Field

[0001] This application relates to the field of computer technology, specifically to an application management method, apparatus, electronic device, and computer-readable storage medium. Background Technology

[0002] Users can hide apps on their devices to effectively protect their privacy. One technology involves hiding app icons on the desktop. However, this still allows users to view the hidden app's information through system settings, indicating insufficient privacy protection. Another technology requires disabling the app in system settings or using administrator privileges, which is more complex. Summary of the Invention

[0003] This application provides an application management method, device, electronic device, and computer-readable storage medium, which can easily achieve desktop and system-level hiding of applications, and provides high privacy protection for hidden applications.

[0004] In a first aspect, embodiments of this application provide an application management method, the method comprising:

[0005] In response to a custom operation that triggers the hiding function in the target interface, the hidden function interface is displayed; the hidden function interface includes the hidden application interface.

[0006] In response to the hiding operation of the first application in the hidden application interface, the first application is simultaneously hidden on the desktop and hidden at the system level.

[0007] In one embodiment, responding to the hiding operation of the first application on the hidden application interface, simultaneously hiding the first application on the desktop and at the system level includes:

[0008] In response to the hiding operation of the first application in the hidden application interface, the biometric verification interface is displayed;

[0009] After verification through the biometric verification interface, the first application is simultaneously hidden on the desktop and at the system level.

[0010] In one embodiment, the hidden function interface further includes unhiding the application interface;

[0011] The method further includes:

[0012] The hidden second application is displayed on the unhide application interface;

[0013] In response to the unhiding operation of the second application on the unhiding application interface, the biometric verification interface is displayed;

[0014] After passing the biometric verification interface, both desktop hiding and system-level hiding are simultaneously removed for the second application.

[0015] In one embodiment, the method further includes:

[0016] In response to the temporary display operation of the second application in the unhidden application interface, the biometric verification interface is displayed;

[0017] After verification through the biometric verification interface, the second application is temporarily displayed on both the desktop and the system.

[0018] After the temporary display duration is reached, the second application is simultaneously hidden on the desktop and at the system level.

[0019] In one embodiment, before displaying the hidden function interface in response to a custom operation that triggers the hidden function in the target interface, the method further includes:

[0020] Obtain the custom operation set by the user in the system settings interface;

[0021] Store the information of the custom operation.

[0022] In one embodiment, the method further includes:

[0023] Get the logged-in user account;

[0024] The information of the custom operation and / or the information of the hidden application are synchronized to other devices logged into the user account, so that the other devices can configure the custom operation according to the information of the custom operation and / or hide the application according to the information of the hidden application.

[0025] In one embodiment, simultaneously hiding the first application on the desktop and at the system level includes:

[0026] By modifying the underlying application package management service of the system, a hidden marker is added to the first application;

[0027] When querying and / or displaying applications on the desktop and system settings interface, filters out applications carrying the hidden marker.

[0028] In one embodiment, hiding an application on the desktop includes: hiding the application's icon on the desktop;

[0029] System-level hiding of an application includes hiding the application's information in the system settings interface.

[0030] Secondly, embodiments of this application provide an application management device, the device comprising:

[0031] The display module is used to display the hidden function interface in response to a custom operation that triggers the hidden function in the target interface; the hidden function interface includes the hidden application interface.

[0032] A hiding module is used to simultaneously hide the first application on the desktop and at the system level in response to a hiding operation of the first application on the hidden application interface.

[0033] Thirdly, embodiments of this application also provide an electronic device, which includes a memory, a processor, and a computer program stored in the memory and executable on the processor. When the computer program is executed by the processor, it implements the steps in the application management method described above.

[0034] Fourthly, embodiments of this application also provide a computer-readable storage medium storing a computer program, which, when executed by a processor, implements the steps in the application management method described above.

[0035] Fifthly, embodiments of this application also provide a computer program product or computer program, which includes computer instructions stored in a computer-readable storage medium. A processor of a computer device reads the computer instructions from the computer-readable storage medium and executes the computer instructions, causing the computer device to perform the methods provided in the various optional implementations described in embodiments of this application.

[0036] The embodiments of this application have the following beneficial effects: the hidden function interface is displayed in response to a custom operation that triggers the hidden function in the target interface. Because the operation is custom, it is not easy for others to obtain the custom operation, thus providing high privacy protection. In response to the hiding operation of the first application in the hidden application interface, the first application can be hidden on the desktop and at the system level at the same time, without the need to hide the application on the desktop and at the system level in the system settings separately. This improves the convenience of the hiding operation and can help improve the user experience. Overall, it can easily realize the desktop hiding and system-level hiding of applications, and provides high privacy protection for the hidden applications. Attached Figure Description

[0037] To more clearly illustrate the technical solutions in this application, the accompanying drawings used in the description of the embodiments will be briefly introduced below. Obviously, the drawings described below are only some embodiments of the present invention. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0038] Figure 1 This is a schematic diagram illustrating the steps of an application management method provided in an embodiment of this application;

[0039] Figure 2 A schematic diagram of a hidden function interface provided in an embodiment of this application;

[0040] Figure 3 A flowchart illustrating an application management method provided in one embodiment of this application;

[0041] Figure 4 This is a schematic diagram of the structure of an application management device provided in an embodiment of this application;

[0042] Figure 5 This is a schematic diagram of the structure of an electronic device provided in an embodiment of this application. Detailed Implementation

[0043] The technical solutions of this application will now be clearly and completely described with reference to the accompanying drawings. Obviously, the described embodiments are merely some embodiments of the present invention, and not all embodiments. All other embodiments obtained by those skilled in the art based on the embodiments of the present invention without creative effort are within the scope of protection of the present invention.

[0044] In one embodiment, such as Figure 1 As shown, an application management method is provided. Although the logical order is illustrated in the step diagram, in some cases, the steps shown or described may be performed in a different order than that shown in the diagram. Specifically, this application management method can be applied to a terminal, which may include, but is not limited to, one or more of smartphones, tablets, laptops, desktop computers, and in-vehicle computers.

[0045] The following sections provide detailed descriptions of each example. It should be noted that the order in which the embodiments are described is not intended to limit the priority of the embodiments.

[0046] according to Figure 1 The application management method shown includes at least steps S110 to S120, which are described in detail below:

[0047] In step S110, in response to the custom operation that triggers the hidden function in the target interface, the hidden function interface is displayed.

[0048] The target interface can be any interface on the terminal; optionally, the target interface can be the system settings interface. The custom operation that triggers the hidden function can be any user-defined operation; for example, it can be a specific gesture or operation of a specific control.

[0049] Users pre-defined actions to trigger the hidden function in the system settings interface, and the terminal records this customized action information. When the user subsequently executes this customized action to trigger the hidden function again in the target interface, the terminal will display the hidden function interface.

[0050] The hidden function interface can include hiding the application interface and / or unhiding the application interface. It can be understood that the hidden function interface including the hidden application interface can mean that a part of the hidden function interface is the hidden application interface, or it can mean that the hidden function interface includes an entry point to the hidden application interface (such as an entry control for the hidden application interface). By operating the entry point of the hidden application interface, the terminal can jump to the hidden function interface.

[0051] Similarly, the hidden function interface including the unhide application interface can refer to a part of the hidden function interface being the unhide application interface, or it can refer to the hidden function interface including an entry point to the unhide application interface (such as an entry control for the unhide application interface). By operating this entry point, the terminal can jump to the unhide function interface.

[0052] In one embodiment, in response to a custom action that triggers the hiding function on the target interface, a hiding function interface is displayed, such as... Figure 2 As shown, this includes an entry control for hiding the application interface and an entry control for unhiding the application interface. In response to the user's action on the entry control for hiding the application interface, the hidden application interface can be displayed; in response to the user's action on the entry control for unhiding the application interface, the unhidden application interface can be displayed.

[0053] In step S120, in response to the hiding operation of the first application in the hidden application interface, the first application is simultaneously hidden on the desktop and hidden at the system level.

[0054] The hidden application interface can include a list of unhidden applications, which can include information about each application that is not currently hidden. The first application can be any application that is not currently hidden.

[0055] The hiding operation can be configured according to actual needs. In one embodiment, the hiding operation can be to select one or more applications from the list of unhidden applications and choose to hide the selected applications, thereby achieving simultaneous desktop hiding and system-level hiding of the selected one or more applications.

[0056] In another embodiment, the hiding operation can be a long press on any application in the list of unhidden applications. After the long press, a pop-up window will appear asking whether to hide the application. When the confirmation option in the pop-up window is selected, the application can be hidden on the desktop and at the system level at the same time.

[0057] Hiding an application (including the first application, the second application, and other applications) on the desktop means hiding the application's icon on the terminal's desktop. Hiding an application (including the first application, the second application, and other applications) at the system level means hiding the application's information in the system settings interface.

[0058] After an application is hidden at the system level, its information cannot be viewed or searched even in the system settings interface.

[0059] Compared to related technologies that achieve system-level hiding of applications by disabling them or by granting device administrator privileges, the convenience of system-level hiding operations in this application embodiment is greatly improved. Furthermore, in related technologies, desktop hiding and system-level hiding require separate operations, while this application embodiment can simultaneously achieve desktop hiding and system-level hiding of applications, further enhancing the convenience of hiding operations.

[0060] The technical solution of this application embodiment displays the hidden function interface in response to a custom operation that triggers the hidden function in the target interface. Because the operation is customizable, it is not easy for others to obtain the custom operation, thus providing high privacy protection. In response to the hiding operation of the first application in the hidden application interface, the first application can be hidden on the desktop and at the system level at the same time, without the need to hide it on the desktop and at the system level in the system settings separately. This improves the convenience of the hiding operation and helps to enhance the user experience. Overall, it can easily achieve desktop and system-level hiding of applications and provides high privacy protection for the hidden applications.

[0061] Based on the above technical solution, as an example, in response to the custom operation of triggering the hiding function in the target interface, the biometric verification interface is displayed; after verification through the biometric verification interface, the hiding function interface is displayed; in response to the hiding operation of the first application in the hiding application interface, the first application is simultaneously hidden on the desktop and hidden at the system level.

[0062] In response to a custom action that triggers the hidden function on the target interface, the biometric verification interface can be displayed first. The hidden function interface will only be revealed after successful verification on the biometric verification interface, thus improving security and privacy protection.

[0063] The biometric verification interface can be a face recognition interface and / or a fingerprint recognition interface, etc. Optionally, the biometric verification interface can be a pop-up window, which can be displayed on top of the original interface. When the biometric verification interface is a face recognition interface, verification through the biometric verification interface can refer to verification through face recognition; when the biometric verification interface is a fingerprint recognition interface, verification through the biometric verification interface can refer to verification through fingerprint recognition.

[0064] Based on the above technical solution, as an embodiment, before displaying the hidden function interface in response to a custom operation that triggers the hidden function in the target interface, the application management method may further include: obtaining the custom operation configured by the user in the system settings interface; and storing the information of the custom operation.

[0065] Users can set custom actions to trigger hidden functions in the system settings interface, and the terminal will record the information of the custom actions set by the user.

[0066] Optionally, the system settings interface may include a control for setting a custom operation to trigger the hidden function. After the user operates this control, they enter the interface for setting the custom operation. In this interface, the user can set a specific gesture, which the terminal will record. Later, when the user performs a gesture in the system settings interface, if the terminal determines that the gesture performed is the recorded specific gesture, the hidden function interface can be displayed.

[0067] In one embodiment, after obtaining the user's custom operation settings in the system settings interface, a biometric verification interface is displayed. The custom operation only takes effect and is stored on the terminal after successful verification through the biometric verification interface. Thus, biometric verification can improve security and privacy.

[0068] The biometric verification interface can be a face recognition interface and / or a fingerprint recognition interface, etc. Optionally, the biometric verification interface can be a pop-up window, which can be displayed on top of the original interface. When the biometric verification interface is a face recognition interface, verification through the biometric verification interface can refer to verification through face recognition; when the biometric verification interface is a fingerprint recognition interface, verification through the biometric verification interface can refer to verification through fingerprint recognition.

[0069] By employing the technical solution of this application embodiment, users can customize the operation to trigger the hiding function, thereby customizing the path to enter the hiding function interface. Access to the hiding function interface is only possible through the user-defined path (via the custom operation), resulting in high privacy protection. Compared to related technologies that require a fixed path to access the hiding-related interface, this significantly improves privacy protection.

[0070] Based on the above technical solution, as an embodiment, in response to the hiding operation of the first application in the hidden application interface, the first application is simultaneously hidden on the desktop and hidden at the system level, which may include: in response to the hiding operation of the first application in the hidden application interface, displaying the biometric verification interface; after passing the verification through the biometric verification interface, the first application is simultaneously hidden on the desktop and hidden at the system level.

[0071] After a user hides the first application in the hidden application interface, the biometric verification interface can be displayed first. Only after the biometric verification is passed will the hiding operation take effect, and the first application will be hidden on both the desktop and the system.

[0072] The biometric verification interface can be a face recognition interface and / or a fingerprint recognition interface, etc. Optionally, the biometric verification interface can be a pop-up window, which can be displayed on top of the original interface. When the biometric verification interface is a face recognition interface, verification through the biometric verification interface can refer to verification through face recognition; when the biometric verification interface is a fingerprint recognition interface, verification through the biometric verification interface can refer to verification through fingerprint recognition.

[0073] Using the technical solution of this application embodiment, after the user performs the hiding operation, the first application will be simultaneously hidden on the desktop and at the system level only after verification through the biometric verification interface. Thus, biometric verification can improve security and privacy protection.

[0074] Based on the above technical solution, as an embodiment, the hidden function interface also includes an application unhiding interface; the application management method may further include: displaying a hidden second application on the application unhiding interface; in response to the unhiding operation of the second application on the application unhiding interface, displaying a biometric verification interface; after verification through the biometric verification interface, simultaneously unhiding the desktop and unhiding the system-level application.

[0075] The hidden function interface, including the unhide application interface, can refer to a portion of the hidden function interface being the unhide application interface, or it can refer to the hidden function interface including an entry point to the unhide application interface (such as an entry control for the unhide application interface). By operating this entry point, the terminal can jump to the unhide function interface.

[0076] The interface for unhiding applications can include a list of hidden applications, which can include information about each application that is currently hidden. The second application can be any application that is currently hidden.

[0077] The unhiding operation can be configured according to actual needs. When a user performs the unhiding operation on a second application in the unhiding application interface, a biometric verification interface is displayed; the unhiding operation will only take effect after the user passes the biometric verification interface, and the second application will be unhidden from both the desktop and system levels simultaneously.

[0078] The biometric verification interface can be a face recognition interface and / or a fingerprint recognition interface, etc. Optionally, the biometric verification interface can be a pop-up window, which can be displayed on top of the original interface. When the biometric verification interface is a face recognition interface, verification through the biometric verification interface can refer to verification through face recognition; when the biometric verification interface is a fingerprint recognition interface, verification through the biometric verification interface can refer to verification through fingerprint recognition.

[0079] In one embodiment, the unhiding operation can be to select one or more applications in the hidden application list and then select the selected applications to unhide, thereby enabling the simultaneous unhiding of desktop and system-level hiding of the selected one or more applications after biometric verification.

[0080] In another embodiment, the unhiding operation can be performed by long-pressing any application in the list of unhidden applications. After the long press, a pop-up window will appear asking whether to unhide the application. When the confirmation option in the pop-up window is selected, a biometric verification interface is displayed. After passing the biometric verification interface, the application can be unhidden from both the desktop and the system level.

[0081] The technical solution adopted in this application embodiment hides the function interface, including the unhiding application interface. Therefore, a custom operation is required to enter the unhiding application interface, which improves privacy protection; biometric verification is required to complete the unhiding operation, which further enhances security.

[0082] Optionally, as an embodiment, the hidden function interface also includes an unhide application interface; the application management method may further include: displaying a hidden second application on the unhide application interface; in response to the unhide operation of the second application on the unhide application interface, simultaneously unhiding the second application from the desktop and unhiding it from the system level.

[0083] Since accessing the hidden feature interface requires a custom operation, which already ensures a high level of security and privacy protection, there is no need for biometric verification again when unhiding the feature, thus improving the user experience.

[0084] Based on the above technical solution, as an embodiment, the application management method may further include: displaying a hidden second application on the unhide application interface; displaying a biometric verification interface in response to the temporary display operation of the second application on the unhide application interface; temporarily displaying the second application on both the desktop and the system simultaneously after verification through the biometric verification interface; and hiding the second application on both the desktop and the system level after the temporary display duration has elapsed.

[0085] The interface for unhiding applications can include a list of hidden applications, which can include information about each application that is currently hidden. The second application can be any application that is currently hidden.

[0086] The temporary display operation can be configured according to actual needs. When a user temporarily displays a second application by unhiding the application interface, a biometric verification interface is displayed. Only after successful verification through the biometric verification interface will the temporary display operation take effect, and the second application will be temporarily unhidden from both the desktop and the system, meaning it will be temporarily displayed on both the desktop and the system simultaneously.

[0087] In one embodiment, the temporary display operation may involve selecting one or more applications from the hidden application list and choosing to temporarily display the selected applications, thereby enabling the selected one or more applications to be temporarily displayed on both the desktop and the system simultaneously after biometric verification.

[0088] In another embodiment, the temporary display operation can be a long press on any application in the list of unhidden applications. After the long press, a pop-up window will appear asking whether to temporarily display the application. When the confirmation option in the pop-up window is selected, the biometric verification interface is displayed. After passing the verification on the biometric verification interface, the application can be temporarily displayed on both the desktop and the system simultaneously.

[0089] Because the display is temporary, after the temporary display duration expires, the application needs to be hidden on both the desktop and the system level. The temporary display duration can be preset according to actual needs, or it can be customized by the user.

[0090] By adopting the technical solution of this application embodiment, the hidden second application is temporarily displayed, which can meet the user's current need to use or view the second application. It can also automatically hide the application again after the temporary display time is reached, which can prevent the user from forgetting to hide the application again after using or viewing the application, and can also improve the convenience of hiding the application again.

[0091] Optionally, as an embodiment, the application management method may further include: displaying a hidden second application on the unhide application interface; in response to the temporary display operation of the second application on the unhide application interface, temporarily displaying the second application on the desktop and system simultaneously; and after the temporary display duration is reached, simultaneously hiding the second application on the desktop and system.

[0092] Since accessing the hidden function interface requires a custom operation, which already ensures a high level of security and privacy protection, there is no need to perform biometric verification again when temporarily displaying the interface, thus improving the user experience.

[0093] Based on the above technical solution, as an embodiment, simultaneously hiding the first application on the desktop and at the system level can include: adding a hidden marker to the first application by modifying the underlying application package manager service; and filtering applications carrying the hidden marker when querying and / or displaying applications on the desktop and system settings interfaces.

[0094] Hiding the first application can be achieved by modifying the system's underlying application package management service to add a hidden flag to the application. This hidden flag can be configured according to specific needs; for example, it can be a pre-defined field.

[0095] When searching for and / or displaying applications on the desktop, and / or when searching for and / or displaying applications in the system settings interface, applications with hidden tags will be filtered out, thus only applications without hidden tags will be displayed; in this way, applications can be hidden.

[0096] When unhiding an application, it can be done by modifying the underlying application package management service to remove the hidden marker carried by the application.

[0097] When temporarily displaying an application, the underlying application package management service can be modified to remove the hidden marker carried by the application and automatically add the hidden marker back to the application after the temporary display period has expired.

[0098] By adopting the technical solution of this application embodiment, by modifying the application package management service at the system level, a hidden marker is added or removed for the application, thereby enabling the application to be hidden or unhidden at both the desktop and system level.

[0099] Based on the above technical solution, as an embodiment, the application management method may further include: obtaining the logged-in user account; synchronizing the information of custom operations and / or the information of hidden applications to other devices of the logged-in user account, so that other devices can configure custom operations according to the information of custom operations, and / or hide applications according to the information of hidden applications.

[0100] When a user account is logged in on the terminal, information about user-defined custom operations and / or information about hidden applications can be linked to that user account. This can involve uploading the custom operation information and / or the hidden application information to the cloud and storing it in relation to the user account.

[0101] When logging into the user account on another device, information about custom actions and / or hidden applications bound to the user account can be synchronized to that other device, and the information about custom actions and / or hidden applications can be applied on that other device.

[0102] After the information for the custom operation is applied on another device, the other device responds to the custom operation that triggers the hiding function in the target interface and displays the hiding function interface; the other device responds to the hiding operation of the application in the hidden application interface and simultaneously hides the application on the desktop and at the system level.

[0103] After applying the information of a hidden application to another device, that other device can detect whether it has followed the application corresponding to the information of the hidden application. If it has followed the application corresponding to the information of the hidden application on the other device, then the application will be hidden on both the desktop and the system level.

[0104] By adopting the technical solution of this application embodiment, information of custom operations and / or information of hidden applications can be synchronized to other devices logged into the user's account. In this way, the relevant settings for hiding can be quickly implemented on other devices logged into the user's account, so that the user does not need to reconfigure them, which can improve convenience and protect privacy on other devices.

[0105] In one embodiment of this application, a user can customize the operation to trigger the hiding function in the system settings interface, and verify their identity through fingerprint recognition or facial recognition to temporarily display or unhide the hidden application. The hidden application is not only removed from the desktop icon, but also simultaneously filtered in the system settings interface (e.g., the application list in the system settings interface) to prevent access via other paths. Furthermore, the display and hiding states can be dynamically switched according to user needs, satisfying both privacy protection and ease of use. Synchronizing the customized operation information and / or the information of the hidden application through the user account ensures consistency of the hiding function across multiple devices.

[0106] Figure 3 A flowchart illustrating an application management method provided in one embodiment of this application is shown. Figure 3As shown, you can first enter the system settings interface, where you can configure the custom actions to trigger the hiding function. The system will save the custom action information and synchronize it to your user account. You can perform the custom action in the system settings interface to access the hiding function interface. In the hiding function interface, select the hidden app list to select apps and hide them. The information of the hidden apps will also be synchronized to your user account. Alternatively, select the unhide app list to long-press an app and select unhide. After biometric verification, the unhide app icon will appear on the desktop.

[0107] The information on hiding and unhiding applications will be synchronized to the system settings. The system settings can then modify the application package management service based on this information, thereby adding or removing hidden tags for applications, filtering applications with hidden tags, and enabling the hiding or unhiding of applications.

[0108] Based on the above technical solutions, considering that the Android system does not allow ordinary applications to modify the application list in the system settings (such as the filtering logic of PackageManager) by default, one embodiment of this application proposes that the application list in the system settings can be modified by hooking system services. For example, the getInstalledApplications method of the PackageManager service can be hijacked through Binder (an inter-process communication mechanism); the application list in the system settings can be modified by modifying the system framework code.

[0109] To achieve real-time linkage between biometric verification and concealment mechanisms, and to dynamically control the application's display state based on the biometric verification results, it is necessary to ensure that the verification results are immutable and have low latency. Therefore, one embodiment of this application proposes binding Android's BiometricPrompt to a hardware-level security module, and using LiveData or BroadcastReceiver to implement real-time communication between the Launcher and the verification module.

[0110] BiometricPrompt is an API that allows developers to easily integrate biometric authentication functionality into their applications, such as fingerprint and facial recognition. Using BiometricPrompt, a small amount of code is needed to invoke the system's biometric dialog box and guide the user through the biometric authentication process. The hardware-level security module can be the KeyStore of the TEE. Hardware-level security modules are hardware components designed to ensure data security and privacy; a Trusted Execution Environment (TEE) is a typical example. A TEE provides a secure execution environment isolated from the main operating system, effectively preventing malware attacks. KeyStore is a key component in the TEE, primarily used to securely store encryption keys. The Launcher is the main screen application of the Android system, responsible for displaying application icons, widgets, etc., and handling user clicks. The authentication module is responsible for biometric authentication; when a user triggers authentication, it calls BiometricPrompt to perform the biometric verification. LiveData is an observable data holder class in the Android architecture, possessing lifecycle awareness capabilities. LiveData enables real-time communication between the Launcher and the authentication module. BroadcastReceiver is a component in the Android system used to receive broadcast messages. BroadcastReceiver can be used to enable real-time communication between the Launcher and the verification module.

[0111] Hiding application information requires synchronization across modules such as Launcher, System Settings, and PackageInstaller to avoid data inconsistencies. To achieve this, a database field (e.g., is_hidden) can be added to the system SettingsProvider, and a status check can be triggered during application installation / update. ContentObserver can then be used to monitor changes in the hidden state and refresh the UI of each module in real time.

[0112] When dynamically displaying and hiding applications, a balance needs to be struck between security and convenience (such as the duration of temporary displays and exit mechanisms). Therefore, a countdown auto-hide function (based on CountDownTimer) can be introduced, which supports user-defined display duration, listens for focus changes in encrypted folders (onWindowFocusChanged), and immediately hides the icon when focus is lost.

[0113] In one embodiment, the application can be hidden by dynamically intercepting the rendering request of the application icon at the system framework layer (such as ViewRootImpl). This can be achieved by writing view rendering logic to dynamically intercept the rendering request of the application icon at the system framework layer.

[0114] In one embodiment, the application can be hidden by replacing the application icon resource with transparent pixels to disguise it as a "blank icon".

[0115] Existing technologies cannot achieve dynamic hiding functionality based on biometric verification; users can only hide applications through a single static operation, lacking flexibility. Applications hidden in these technologies can still be viewed in system settings, resulting in incomplete privacy protection. This deficiency is particularly pronounced when sensitive information is involved (such as in home-shared devices). While related technologies can hide applications using device administrator privileges or by disabling the application, the process is complex and fails to meet the dynamic interaction needs of everyday scenarios, providing no user-friendly solution. The technical solution of this application addresses these technical problems.

[0116] The application management method of this application embodiment can be applied to any of the following scenarios:

[0117] Privacy protection scenarios. In this scenario, users need to hide privacy-sensitive applications, such as password managers, personal diaries, and financial transaction applications. When sharing devices or in public places, users can protect these applications from being seen by others through customized actions and biometric authentication. For example, if a user's phone includes work-related applications but they don't want other family members to see them, they can hide these applications.

[0118] To prevent interference and accidental clicks, this scenario involves hiding infrequently used applications to prevent their icons from cluttering the screen or being accidentally clicked, thus maintaining a clean and simple system interface. For example, when using mobile navigation, users might want to hide game applications to prevent accidental clicks; in this case, game applications can be hidden.

[0119] Shared device scenario. In this scenario, multiple people use the same device, and users want to hide their important applications to protect their personal space while ensuring that other users cannot accidentally access or view non-public content. For example, a user might hide their social media apps on a company-provided work tablet to avoid affecting work or being accidentally discovered by colleagues.

[0120] Kids Mode Scenario. In this scenario, users want to hide apps unsuitable for children, providing a dedicated mode for children or restricting access to certain apps. For example, parents might hide shopping or entertainment apps to ensure children can only access educational apps.

[0121] Switching between scenarios. Users may need to switch between different trigger paths or hidden application configurations in various scenarios. Users can quickly load the corresponding hidden configurations in different scenarios through application management methods. For example, users can use the hidden configuration during work hours to block social applications; after get off work, they can switch to the entertainment hidden configuration to block work applications.

[0122] Cross-device synchronization scenario. In this scenario, when a user changes devices or logs into the same account on multiple devices, information about custom actions and / or hidden applications can be automatically synchronized to ensure a consistent user experience. For example, after a user gets a new phone, they do not need to reconfigure custom actions and hidden applications to maintain the original settings.

[0123] To facilitate better implementation of the application management method of this application, this application also provides an application management device based on the above-described application management method. The meanings of the terms used are the same as in the application management method described above, and specific implementation details can be found in the descriptions of the method embodiments.

[0124] Please see Figure 4 , Figure 4 This is a schematic diagram of the structure of the application management device provided in the embodiments of this application, wherein the application management device includes:

[0125] The display module 401 is used to display the hidden function interface in response to a custom operation that triggers the hidden function in the target interface; the hidden function interface includes the hidden application interface.

[0126] The hiding module 402 is used to simultaneously hide the first application on the desktop and at the system level in response to the hiding operation of the first application on the hidden application interface.

[0127] In one embodiment, the hiding module 402 includes:

[0128] The first display unit is configured to display the biometric verification interface in response to a hiding operation of the first application in the hidden application interface.

[0129] The first hiding unit is used to simultaneously hide the first application on the desktop and at the system level after verification through the biometric verification interface.

[0130] In one embodiment, the hidden function interface further includes unhiding the application interface; the device further includes:

[0131] The display module is used to display the hidden second application in the unhide application interface;

[0132] The first verification display module is used to display the biometric verification interface in response to the unhiding operation of the second application on the unhiding application interface.

[0133] The unhide module is used to simultaneously unhide the desktop and unhide the system-level hide of the second application after verification through the biometric verification interface.

[0134] In one embodiment, the device further includes:

[0135] The second verification display module is used to display the biometric verification interface in response to the temporary display operation of the second application in the unhidden application interface.

[0136] A temporary display module is used to temporarily display the second application on both the desktop and the system simultaneously after verification through the biometric verification interface.

[0137] Simultaneously, a hidden module is used to simultaneously hide the second application on the desktop and at the system level after the temporary display duration has elapsed.

[0138] In one embodiment, before displaying the hidden function interface in response to a custom operation that triggers the hidden function in the target interface, the device further includes:

[0139] The operation acquisition module is used to acquire the custom operation configured by the user in the system settings interface;

[0140] An information storage module is used to store information about the custom operation.

[0141] In one embodiment, the device further includes:

[0142] The account retrieval module is used to retrieve the logged-in user account;

[0143] The synchronization module is used to synchronize the information of the custom operation and / or the information of the hidden application to other devices logged into the user account, so that the other devices can configure the custom operation according to the information of the custom operation and / or hide the application according to the information of the hidden application.

[0144] In one embodiment, the hiding module 402 includes:

[0145] The tag-adding unit is used to add a hidden tag to the first application by modifying the application package management service at the system's underlying level;

[0146] A filtering unit is used to filter applications carrying the hidden marker when the application is queried and / or displayed on the desktop and system.

[0147] In one embodiment, hiding an application on the desktop includes: hiding the application's icon on the desktop;

[0148] System-level hiding of an application includes hiding the application's information in the system settings interface.

[0149] The technical solution of this application embodiment displays the hidden function interface in response to a custom operation that triggers the hidden function in the target interface. Because the operation is customizable, it is not easy for others to obtain the custom operation, thus providing high privacy protection. In response to the hiding operation of the first application in the hidden application interface, the first application can be hidden on the desktop and at the system level at the same time, without the need to hide it on the desktop and at the system level in the system settings separately. This improves the convenience of the hiding operation and helps to enhance the user experience. Overall, it can easily achieve desktop and system-level hiding of applications and provides high privacy protection for the hidden applications.

[0150] For specific limitations regarding the application management device, please refer to the limitations on the application management method above, which will not be repeated here. Each module in the aforementioned application management device can be implemented entirely or partially through software, hardware, or a combination thereof. These modules can be embedded in or independent of the processor in the computer device in hardware form, or stored in the memory of the computer device in software form, so that the processor can call and execute the operations corresponding to each module.

[0151] In addition, this application also provides an electronic device, such as Figure 5 As shown, it illustrates the structural diagram of the electronic device involved in this application, specifically:

[0152] The electronic device may include components such as a processor 501 with one or more processing cores and a memory 502 of one or more computer-readable storage media. Those skilled in the art will understand that... Figure 5 The electronic device structure shown does not constitute a limitation on the electronic device and may include more or fewer components than shown, or combine certain components, or have different component arrangements. Wherein:

[0153] The processor 501 is the control center of the electronic device. It connects various parts of the electronic device via various interfaces and lines. By running or executing software programs and / or modules stored in the memory 502, and by calling data stored in the memory 502, it performs various functions and processes data, thereby providing overall monitoring of the electronic device. Optionally, the processor 501 may include one or more processing cores; preferably, the processor 501 may integrate an application processor and a modem processor, wherein the application processor mainly handles the operating system, user interface, and applications, and the modem processor mainly handles wireless communication. It is understood that the modem processor may not be integrated into the processor 501.

[0154] The memory 502 can be used to store software programs and modules. The processor 501 executes various functional applications and data processing by running the software programs and modules stored in the memory 502. The memory 502 may mainly include a program storage area and a data storage area. The program storage area may store the operating system, application programs required for at least one function (such as sound playback function, image playback function, etc.), etc.; the data storage area may store data created according to the use of the electronic device, etc. In addition, the memory 502 may include high-speed random access memory, and may also include non-volatile memory, such as at least one disk storage device, flash memory device, or other volatile solid-state storage device. Accordingly, the memory 502 may also include a memory controller to provide the processor 501 with access to the memory 502.

[0155] In one embodiment, the electronic device further includes a power supply 503 that supplies power to the various components. Preferably, the power supply 503 can be logically connected to the processor 501 through a power management system, thereby enabling functions such as charging, discharging, and power consumption management through the power management system. The power supply 503 may also include one or more DC or AC power supplies, recharging systems, power equipment debugging circuits, power converters or inverters, power status indicators, and other arbitrary components.

[0156] In one embodiment, the electronic device may further include an input unit 504, which can be used to receive input digital or character information and generate keyboard, mouse, joystick, optical or trackball signal inputs related to user settings and function control.

[0157] Although not shown, the electronic device may also include a display unit, etc., which will not be described in detail here. Specifically, in this embodiment, the processor 501 in the electronic device loads the executable files corresponding to the processes of one or more applications into the memory 502 according to the following instructions, and the processor 501 runs the applications stored in the memory 502, thereby implementing the steps in any of the application management methods provided in the embodiments of this application.

[0158] Those skilled in the art will understand that Figure 5 The structure shown is merely a block diagram of a portion of the structure related to the present application and does not constitute a limitation on the electronic device to which the present application is applied. The specific electronic device may include more or fewer components than shown in the figure, or combine certain components, or have different component arrangements.

[0159] In one embodiment, an electronic device is provided, including a memory and a processor, wherein the memory stores a computer program, and the processor executes the computer program to implement the methods described in any embodiment of this application.

[0160] In one embodiment, a computer-readable storage medium is provided having a computer program stored thereon, which, when executed by a processor, implements the method described in any embodiment of this application.

[0161] In some embodiments, a computer program product is also provided, including a computer program or instructions that, when executed by a processor, implement the methods described in any embodiment of this application.

[0162] For details on the implementation of each of the above operations, please refer to the previous examples, which will not be repeated here.

[0163] Those skilled in the art will understand that all or part of the steps in the various methods of the above embodiments can be performed by instructions, or by instructions controlling related hardware. These instructions can be stored in a computer-readable storage medium and loaded and executed by a processor.

[0164] Therefore, this application provides a computer-readable storage medium storing a computer program that can be loaded by a processor to execute the steps in any of the application management methods provided in this application.

[0165] For details on the implementation of each of the above operations, please refer to the previous examples, which will not be repeated here.

[0166] The computer-readable storage medium may include: read-only memory (ROM), random access memory (RAM), disk or optical disk, etc.

[0167] Since the instructions stored in the computer-readable storage medium can execute the steps of any of the application management methods provided in this application, the beneficial effects that any of the application management methods provided in this application can achieve can be realized, as detailed in the preceding embodiments, and will not be repeated here.

[0168] Finally, it should be noted that in this document, relational terms such as "first" and "second" are used only to distinguish one entity or operation from another, and do not necessarily require or imply any such actual relationship or order between these entities or operations. Furthermore, the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or terminal device that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or terminal device. Without further limitations, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the process, method, article, or terminal device that includes said element.

[0169] The above provides a detailed description of an application management method, apparatus, electronic device, and computer-readable storage medium provided in this application. Specific examples have been used to illustrate the principles and implementation methods of the present invention. The description of the above embodiments is only for the purpose of helping to understand the method and core ideas of the present invention. At the same time, those skilled in the art will recognize that there will be changes in the specific implementation methods and application scope based on the ideas of the present invention. Therefore, the content of this specification should not be construed as a limitation of the present invention.

Claims

1. An application management method, characterized in that, The method includes: In response to a custom operation that triggers the hiding function in the target interface, the hidden function interface is displayed; the hidden function interface includes the hidden application interface. In response to the hiding operation of the first application in the hidden application interface, the first application is simultaneously hidden on the desktop and hidden at the system level.

2. The method according to claim 1, characterized in that, The response to the hiding operation of the first application on the hidden application interface, simultaneously hiding the first application on the desktop and at the system level, includes: In response to the hiding operation of the first application in the hidden application interface, the biometric verification interface is displayed; After verification through the biometric verification interface, the first application is simultaneously hidden on the desktop and at the system level.

3. The method according to claim 1, characterized in that, The hidden function interface also includes unhiding the application interface; The method further includes: The hidden second application is displayed on the unhide application interface; In response to the unhiding operation of the second application on the unhiding application interface, the biometric verification interface is displayed; After passing the biometric verification interface, the desktop hiding and system-level hiding of the second application are simultaneously unhidden.

4. The method according to claim 3, characterized in that, The method further includes: In response to the temporary display operation of the second application in the unhidden application interface, the biometric verification interface is displayed; After verification through the biometric verification interface, the second application is temporarily displayed on both the desktop and the system. After the temporary display duration is reached, the second application is simultaneously hidden on the desktop and at the system level.

5. The method according to claim 1, characterized in that, Before displaying the hidden function interface in response to the custom operation that triggers the hidden function in the target interface, the method further includes: Obtain the custom operation set by the user in the system settings interface; Store the information of the custom operation.

6. The method according to claim 5, characterized in that, The method further includes: Get the logged-in user account; The information of the custom operation and / or the information of the hidden application are synchronized to other devices logged into the user account, so that the other devices can configure the custom operation according to the information of the custom operation and / or hide the application according to the information of the hidden application.

7. The method according to any one of claims 1 to 6, characterized in that, The simultaneous desktop hiding and system-level hiding of the first application includes: By modifying the underlying application package management service of the system, a hidden marker is added to the first application; When querying and / or displaying applications on the desktop and system settings interface, filters out applications carrying the hidden marker.

8. The method according to any one of claims 1 to 6, characterized in that, Hiding an application on the desktop includes: hiding the application's icon on the desktop; System-level hiding of an application includes hiding the application's information in the system settings interface.

9. An application management device, characterized in that, The device includes: The display module is used to display the hidden function interface in response to a custom operation that triggers the hidden function in the target interface; the hidden function interface includes the hidden application interface. A hiding module is used to simultaneously hide the first application on the desktop and at the system level in response to a hiding operation of the first application on the hidden application interface.

10. An electronic device, characterized in that, It includes a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor executes the computer program to implement the steps of the application management method as described in any one of claims 1 to 8.

11. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores a computer program that, when executed by a processor, implements the steps of the application management method as described in any one of claims 1 to 8.

Images