Desktop application program management method and device, terminal equipment and storage medium

Abstract

The embodiment of the invention discloses a desktop application program management method and device, terminal equipment and a storage medium, which are used for managing non-common application programs on a desktop interface according to use data of each application program and reducing interference in the use process of other common application programs on a desktop. The method provided by the embodiment of the invention comprises the following steps: detecting use data of each application program in a preset duration on a desktop interface; adding a non-common-use identifier to a non-common-use application program on the desktop interface, and / or reducing a display area occupied by the non-common-use application program on the desktop interface; wherein the unusual use identifier is used for prompting that the unusual use application program is an application program of which the use frequency is smaller than or equal to a use frequency threshold value within the preset duration, and the unusual use application program is determined according to the use data of each application program within the preset duration.

Description

Technical Field

[0001] The present application relates to the field of terminal devices, and in particular to a method, device, terminal device and storage medium for managing desktop applications. Background Art

[0002] The desktop interface of existing terminal devices displays all available applications or shortcuts for download. A large number of applications can easily bring great cognitive and operational costs to users. Many applications exist on the desktop interface, but users use them very rarely, or they are no longer used after using them once, thus becoming a kind of "zombie application" that interferes with users' use of other commonly used applications. Summary of the invention

[0003] The embodiments of the present application provide a desktop application management method, apparatus, terminal device and storage medium for managing infrequently used applications on a desktop interface based on usage data of each application, thereby reducing interference with the use of other commonly used applications on the desktop.

[0004] A first aspect of the present application provides a method for managing a desktop application, which may include:

[0005] Detect usage data of each application within a preset time period on the desktop interface;

[0006] Adding a non-common mark to a non-common application on the desktop interface, and / or reducing a display area occupied by the non-common application on the desktop interface;

[0007] The infrequently used identifier is used to indicate that the infrequently used application is an application whose usage frequency within the preset duration is less than or equal to a usage frequency threshold, and the infrequently used application is determined based on usage data of each application within the preset duration.

[0008] A second aspect of the present application provides a management device for a desktop application, which may include:

[0009] A detection module, used to detect usage data of each application within a preset time period on the desktop interface;

[0010] A display module is used to add a non-commonly used mark to a non-commonly used application on the desktop interface, and / or to reduce the display area occupied by the non-commonly used application on the desktop interface; wherein the non-commonly used mark is used to prompt that the non-commonly used application is an application whose usage frequency within the preset time period is less than or equal to a usage frequency threshold, and the non-commonly used application is determined based on usage data of each application within the preset time period.

[0011] A third aspect of the present application provides a terminal device, which may include a memory and a processor, wherein the memory stores a computer program that can be executed on the processor, and when the terminal device executes the program, the method described in the first aspect of the present application is implemented.

[0012] A fourth aspect of the present application provides a computer-readable storage medium having a computer program stored thereon, which, when executed by a processor, implements the method described in the first aspect of the present application.

[0013] Yet another aspect of an embodiment of the present application discloses a computer program product. When the computer program product is run on a computer, the computer is enabled to execute the method described in the first aspect of the present application.

[0014] Another aspect of an embodiment of the present application discloses an application publishing platform, which is used to publish a computer program product. When the computer program product runs on a computer, the computer executes the method described in the first aspect of the present application.

[0015] It can be seen from the above technical solutions that the embodiments of the present application have the following advantages:

[0016] In an embodiment of the present application, usage data of each application within a preset time period on a desktop interface is detected; an infrequently used indicator is added to an infrequently used application on the desktop interface, and / or a display area occupied by the infrequently used application is reduced on the desktop interface; wherein the infrequently used indicator is used to prompt that the infrequently used application is an application whose usage frequency within the preset time period is less than or equal to a usage frequency threshold, and the infrequently used application is determined based on the usage data of each application within the preset time period, which can reduce interference with the use of other commonly used applications on the desktop. BRIEF DESCRIPTION OF THE DRAWINGS

[0017] In order to more clearly illustrate the technical solutions of the embodiments of the present application, the drawings required for use in the embodiments and the description of the prior art will be briefly introduced below. Obviously, the drawings described below are only some embodiments of the present application, and other drawings can be obtained based on these drawings.

[0018] Figure 1A A schematic diagram of an application in a desktop interface in one implementation;

[0019] Figure 1B A schematic diagram of an application in a folder management desktop interface in one implementation;

[0020] Figure 2 A schematic diagram of an embodiment of a method for managing desktop applications in an embodiment of the present application;

[0021] Figure 3 This is another schematic diagram of an embodiment of the method for managing desktop applications in an embodiment of the present application;

[0022] Figure 4A A schematic diagram of moving a non-commonly used application to a non-commonly used application folder in an embodiment of the present application;

[0023] Figure 4B A schematic diagram showing that the setting interface includes uncommon application function controls in an embodiment of the present application;

[0024] Figure 4C A schematic diagram showing that the setting interface includes at least one duration control in an embodiment of the present application;

[0025] Figure 4D A schematic diagram of selecting two duration controls in the setting interface in the embodiment of the present application, and correspondingly generating two infrequently used application folders;

[0026] Figure 4E A schematic diagram of reducing and displaying the icon of the infrequently used application on the desktop interface in an embodiment of the present application;

[0027] Figure 5A A schematic diagram of a triggering operation of a pure mode in an embodiment of the present application;

[0028] Figure 5B A schematic diagram of hiding and displaying the infrequently used application according to the pure mode in an embodiment of the present application;

[0029] Figure 5C A schematic diagram of displaying commonly used applications according to the pure mode in an embodiment of the present application;

[0030] Figure 5D Another schematic diagram of displaying commonly used applications according to the pure mode in an embodiment of the present application;

[0031] Figure 6 This is another schematic diagram of an embodiment of the method for managing desktop applications in an embodiment of the present application;

[0032] Fig. 7A A schematic diagram of moving a non-common application to a non-common application folder and adding a non-common mark to a non-common application in an embodiment of the present application;

[0033] Figure 7B A schematic diagram of an embodiment of the present application in which the setting interface also includes an original location area icon control of a non-common application;

[0034] Figure 8This is another schematic diagram of an embodiment of the method for managing desktop applications in an embodiment of the present application;

[0035] Fig. 9 A schematic diagram of adding an unusually used mark to an unusually used application in an embodiment of the present application;

[0036] Fig.10 A schematic diagram of an embodiment of a management device for a desktop application in an embodiment of the present application;

[0037] Fig.11 This is a schematic diagram of an embodiment of a terminal device in an embodiment of the present application;

[0038] Fig.12 This is another schematic diagram of a terminal device in an embodiment of the present application. DETAILED DESCRIPTION

[0039] The embodiments of the present application provide a desktop application management method, apparatus, terminal device and storage medium for managing infrequently used applications on a desktop interface based on usage data of each application, thereby reducing interference with the use of other commonly used applications on the desktop.

[0040] In order to make the technical personnel in the technical field better understand the scheme of the present application, the technical scheme in the embodiment of the present application will be described below in conjunction with the drawings in the embodiment of the present application. Obviously, the described embodiment is only a part of the embodiment of the present application, not all of the embodiments. Based on the embodiments in the present application, they should all fall within the scope of protection of the present application.

[0041] In one implementation, the desktop interface of an existing terminal device displays all available applications or shortcuts for download. Figure 1A As shown in FIG. 1 , a schematic diagram of an application in a desktop interface in one implementation is shown. Figure 1B FIG. 1 is a schematic diagram of an application program in a folder management desktop interface in one implementation. Figure 1B As shown, the operation of managing applications in the desktop interface through folders is realized through user operations, that is, the user wants to manage which applications in the folder, for example, by dragging application A to the position of application B, application A and application B can be displayed in the same folder. A large number of applications can easily bring great cognitive and operational costs to users. Many applications exist on the desktop interface, but the user's use frequency is very low, or they are no longer used after using them once, which will cause certain interference to the user's use of other commonly used applications.

[0042] In an embodiment of the present application, by automatically detecting the usage data of each application within a preset time period on the desktop interface; managing the infrequently used applications on the desktop interface, and the infrequently used applications are determined based on the usage data of each application within the preset time period, interference with the use of commonly used applications can be avoided to a certain extent.

[0043] In the embodiment of the present application, the terminal device can be a mobile phone, a tablet computer, a computer with wireless transceiver function, a virtual reality (VR) terminal device, an augmented reality (AR) terminal device, a wireless terminal device in industrial control, a wireless terminal device in self driving, a wireless terminal device in remote medical, a wireless terminal device in a smart grid, a wireless terminal device in transportation safety, a wireless terminal device in a smart city, or a wireless terminal device in a smart home, etc.

[0044] As an example but not limitation, in the embodiments of the present application, the terminal device may also be a wearable device. Wearable devices may also be referred to as wearable smart devices, which are a general term for wearable devices that are intelligently designed and developed using wearable technology for daily wear, such as glasses, gloves, watches, clothing, and shoes. A wearable device is a portable device that is worn directly on the body or integrated into the user's clothes or accessories. Wearable devices are not only hardware devices, but also powerful functions achieved through software support, data interaction, and cloud interaction. Broadly speaking, wearable smart devices include full-featured, large-sized, and fully or partially independent of smartphones, such as smart watches or smart glasses, as well as devices that only focus on a certain type of application function and need to be used in conjunction with other devices such as smartphones, such as various types of smart bracelets and smart jewelry for vital sign monitoring.

[0045] The technical solution of the present application is further described below by way of embodiments. Figure 2 As shown, it is a schematic diagram of an embodiment of a method for managing a desktop application in an embodiment of the present application, which may include:

[0046] 201. Detect usage data of each application program on a desktop interface within a first preset time period.

[0047] The terminal device detects usage data of each application on the terminal device within a first preset time period. For example, the first preset time period can be: one week, half a month, one month, three months, half a year, one year, or two years.

[0048] In some possible implementations, the first preset duration is a default duration, or a duration selected and set by a user.

[0049] The usage data may include at least one of the number of times the device is used and the duration of use. The usage data may be at least one of the total number of times the device is used and the total duration of use within a first preset duration, or may be at least one of the number of times the device is used per day and the duration of use per day within the first preset duration, which is not limited in the specific embodiments of the present application.

[0050] In some possible implementations, the presentation of each application on the desktop interface may be a shortcut to the application, for example, a shortcut to the application on a laptop computer.

[0051] 202. Adding a non-commonly used mark to a non-commonly used application on the desktop interface, and / or reducing a display area occupied by the non-commonly used application on the desktop interface.

[0052] The infrequently used identifier is used to indicate that the infrequently used application is an application whose usage frequency within the preset duration is less than or equal to a usage frequency threshold, and the infrequently used application is determined based on usage data of each application within the preset duration.

[0053] Optionally, the usage frequency may be characterized by at least one of usage duration and usage times.

[0054] The following first describes how to determine the infrequently used applications based on the usage data of each application within the preset time period, as shown below:

[0055] 1. When the usage data is at least one of the total number of uses and the total usage duration within the first preset duration, the preset number of uses can be understood as the preset total number of uses, and the preset usage duration can be understood as the preset total usage duration.

[0056] Optionally, determining the uncommonly used applications according to the usage data of each application may include:

[0057] When the first usage count of the first application is less than or equal to the preset usage count, determining that the first application is a non-commonly used application; or,

[0058] When the first usage duration of the first application is less than or equal to the preset usage duration, determining that the first application is a non-commonly used application; or,

[0059] When a first usage count of a first application is less than or equal to a preset usage count and a first usage duration of the first application is less than or equal to a preset usage duration, the first application is determined to be a less frequently used application.

[0060] Exemplarily, assuming that the first preset time period is 1 month, if the number of times the application (Application, APP) 4 is used is 1, and the preset number of times of use is 10, then 1 is less than 10, and it is determined that the application 4 is not a frequently used application.

[0061] Assuming that the first preset duration is 1 month, if the usage duration of application (Application, APP) 4 is 10 minutes and the preset usage duration is 300 minutes, then 10 minutes is less than 300 minutes, and application 4 is determined to be an infrequently used application.

[0062] Assuming that the first preset time is 1 month, if the number of times application (Application, APP) 4 is used is 1, and the preset number of times is 10, then 1 is less than 10, and if the usage time of application (Application, APP) 4 is 10 minutes, and the preset usage time is 300 minutes, then 10 minutes is less than 300 minutes, and application 4 is determined to be a less frequently used application.

[0063] Assuming that the first preset time is 1 month, if the number of times the application (Application, APP) 5 is used is 5 and the preset number of times is 10, then 5 is less than 10, and it is determined that the application 5 is an infrequently used application.

[0064] Assuming that the first preset duration is 1 month, if the usage duration of application (Application, APP) 5 is 50 minutes and the preset usage duration is 300 minutes, then 50 minutes is greater than 300 minutes, and it is determined that application 5 is a not-very-used application.

[0065] Assuming that the first preset time is 1 month, if the number of times application (Application, APP) 5 is used is 5, and the preset number of times is 10, then 5 is less than 10; and if the usage time of application (Application, APP) 5 is 50 minutes, and the preset usage time is 300 minutes, then 50 minutes is less than 300 minutes, and application 5 is determined to be a less frequently used application.

[0066] 2. When the usage data is at least one of the number of uses per day and the daily usage duration within the first preset duration, the preset number of uses is understood to be the preset number of uses corresponding to each day; the preset usage duration is understood to be the preset usage duration corresponding to each day.

[0067] (1) Determining infrequently used applications based on usage data of each application may include: when a preset number of usages is a preset number of usages corresponding to each day, comparing the number of usages per day within a first preset time period with the preset number of usages to determine infrequently used applications per day; and then calculating a first proportion of each application determined as an infrequently used application within the first preset time period, and when a first proportion of a first application among each application determined as an infrequently used application within the first preset time period is greater than a first proportion threshold, determining that the first application is an infrequently used application.

[0068] Exemplarily, assuming that the first preset time is one month, the usage data of each application includes the number of times it is used every day. The preset number of times is 1. If the number of times a certain application is used on a certain day is less than or equal to the preset number of times, then the application is determined to be an infrequently used application on that day. Then, the first ratio of the number of times the application is determined to be an infrequently used application in this month to the number of days in this month is calculated. For example, if the first ratio is 40% and the first ratio threshold is 30%, then if the first ratio of 40% is greater than the first ratio threshold of 30%, the application is determined to be an infrequently used application.

[0069] or,

[0070] (2) Determining infrequently used applications based on usage data of each application may include: when a preset usage time is a preset usage time corresponding to each day, comparing the usage time of each day within a first preset time with the preset usage time to determine infrequently used applications for each day; then calculating a second proportion of each application determined as an infrequently used application within the first preset time, and when the second proportion of a first application among each application determined as an infrequently used application within the first preset time is greater than a second proportion threshold, determining that the first application is an infrequently used application.

[0071] Exemplarily, assuming that the first preset duration is one month, the usage data of each application includes the daily usage duration. The preset usage duration is 5 minutes. If the usage duration of an application on a certain day is less than or equal to the preset usage duration, then the application is determined to be an infrequently used application on that day. Then, the second ratio of the number of times the application is determined to be an infrequently used application in this month to the number of days in this month is calculated. For example, if the second ratio is 50% and the second ratio threshold is 40%, then if the second ratio of 50% is greater than the second ratio threshold of 40%, the application is determined to be an infrequently used application.

[0072] or,

[0073] (3) Determining infrequently used applications based on usage data of each application may include: when a preset number of usages is a preset number of usages corresponding to each day, comparing the number of usages per day within a first preset time period with the preset number of usages to determine infrequently used applications per day, and then calculating a first proportion of each application determined as an infrequently used application within the first preset time period; when a preset usage time is a preset usage time corresponding to each day, comparing the usage time per day within the first preset time period with the preset usage time to determine infrequently used applications per day, and then calculating a second proportion of each application determined as an infrequently used application within the first preset time period; when a first proportion of a first application among each application determined as an infrequently used application within the first preset time period is greater than a first proportion threshold, and a second proportion of a first application among each application determined as an infrequently used application within the first preset time period is greater than a second proportion threshold, determining that the first application is an infrequently used application.

[0074] Exemplarily, assuming that the first preset duration is one month, the usage data of each application includes the number of times the third application is used and the usage duration per day. The preset number of times is 1, if the number of times the third application is used on a certain day is less than or equal to the preset number of times, then the third application is determined to be an infrequently used application on that day, then the first proportion of the number of times the third application is determined to be an infrequently used application in this month to the number of days in this month is calculated, for example, the first proportion is 40%, the first proportion threshold is 30%, then the first proportion of 40% is greater than the first proportion threshold of 30%; and the preset usage duration is 5 minutes, if the usage duration of the third application on a certain day is less than or equal to the preset usage duration, then the third application is determined to be an infrequently used application on that day, then the second proportion of the number of times the third application is determined to be an infrequently used application in this month to the number of days in this month is calculated, for example, the second proportion is 50%, the second proportion threshold is 40%, then the second proportion of 50% is greater than the second proportion threshold of 40%, and the third application is determined to be an infrequently used application.

[0075] It should be noted that different first preset durations correspond to different preset usage times and preset usage durations.

[0076] In the technical solution of the present application, the usage data of the application includes at least one of the number of uses and the usage duration, and how to determine whether the application is an infrequently used application based on the number of uses and at least one of the usage duration is specifically explained, thereby improving the feasibility of the solution.

[0077] In some possible implementations, after determining the infrequently used applications based on the usage data of the various applications, the method further includes: adding an infrequently used identifier to the infrequently used applications.

[0078] Exemplarily, after determining the infrequently used applications based on the usage data of the various applications, if the infrequently used applications have not been managed, an infrequently used mark is added to the infrequently used applications to prompt the user that these applications are infrequently used applications, so as to facilitate the user to determine whether to delete these applications. If the application is to be deleted, the target application is deleted on the desktop interface when a deletion operation on the target application is detected. If the application is not to be deleted, the infrequently used application is moved to an infrequently used application folder for management, or the infrequently used application is hidden and displayed, etc., when no operation on the target application is detected within a second preset time period.

[0079] In this technical solution, after determining the infrequently used applications based on the usage data of the various applications, an infrequently used mark is added to the infrequently used applications to prompt the user that these applications are infrequently used applications, so as to facilitate the user to decide whether to delete these applications and to facilitate the user to manage the infrequently used applications.

[0080] In some possible implementations, when it is detected that the effective usage time of the first target application is less than a specific time threshold, the first target application is determined to be a non-commonly used application.

[0081] Exemplarily, the reason for the failure to log in to the first target application may be that the login data is wrong, or the application version is too low, etc. In short, the first target application is not successfully used. In other words, when the effective use time of the first target application is less than a specific time threshold, the first target application is determined to be an uncommon application. In other words, some application users may have clicked on them, but they cannot log in or the version is too low, etc., and no effective behavior is generated. When the effective use time is less than a specific time threshold, they can also be regarded as uncommon applications.

[0082] In this technical solution, the first target application is determined to be a non-common application, a specific implementation method is provided, and the feasibility of the solution is improved.

[0083] Exemplarily, after the terminal device determines the infrequently used applications according to the usage data of the various applications, the infrequently used applications may be managed on the desktop interface, and the management of the infrequently used applications on the desktop interface may include:

[0084] Adding a non-common mark to a non-common application on the desktop interface; or,

[0085] reducing the display area occupied by the infrequently used application on the desktop interface; or,

[0086] A non-common mark is added to the non-common application on the desktop interface, and a display area occupied by the non-common application on the desktop interface is reduced.

[0087] Exemplarily, the infrequently used mark may include a sleeping mark, or infrequently used text, or some other marks, which are not specifically limited in the embodiments of the present application. The infrequently used mark is used to indicate that the corresponding application is an infrequently used application.

[0088] After reducing the display area occupied by the infrequently used applications on the desktop interface, because the display area occupied by the infrequently used applications is reduced compared to before the display area occupied by the infrequently used applications is reduced, more display area can be used, thereby reducing interference with other frequently used applications on the desktop to a certain extent.

[0089] In an embodiment of the present application, usage data of each application within a preset time period on a desktop interface is detected; an infrequently used indicator is added to an infrequently used application on the desktop interface, and / or a display area occupied by the infrequently used application is reduced on the desktop interface; wherein the infrequently used indicator is used to prompt that the infrequently used application is an application whose usage frequency within the preset time period is less than or equal to a usage frequency threshold, and the infrequently used application is determined based on the usage data of each application within the preset time period, which can reduce interference with the use of other commonly used applications on the desktop.

[0090] like Figure 3 FIG. 1 is a schematic diagram of another embodiment of the method for managing desktop applications in an embodiment of the present application. The method may include:

[0091] 301. Detect usage data of each application program on a desktop interface within a first preset time period.

[0092] The step of managing the infrequently used application on the desktop interface may include step 302:

[0093] 302. Reduce the display area occupied by the infrequently used application on the desktop interface.

[0094] In some possible implementations, reducing the display area occupied by the infrequently used applications on the desktop interface may include: generating an infrequently used application folder on the desktop interface; and moving the infrequently used application to the infrequently used application folder for management.

[0095] For example, a folder is automatically generated on the desktop interface, which can be named a frequently used application folder or a dormant application folder. The user can also customize the name, which is not limited in the embodiment of the present application. Then, the frequently used application is moved to the frequently used application folder for management. At this time, because the frequently used application is moved to the frequently used application folder, the interference with the user's use of frequently used applications is greatly reduced.

[0096] For example: There are 9 applications on the desktop interface, namely Application 1 (Application1, APP1), APP2, APP3, APP4, APP5, APP6, APP7, APP8, APP9. Suppose based on the usage data of these 9 applications, the infrequently used applications are determined to include APP4, APP5 and APP6. Then, after the infrequently used applications are determined, a folder can be automatically created. This folder can be named by default, such as an infrequently used application folder. Then, APP4, APP5 and APP6 are automatically moved to the infrequently used application folder for management. Figure 4A As shown, it is a schematic diagram of moving a seldom-used application to a seldom-used application folder in an embodiment of the present application.

[0097] In this technical solution, after the terminal device determines the infrequently used applications based on the usage data of the various applications, a folder of infrequently used applications is generated on the desktop interface; the infrequently used applications are moved to the folder of infrequently used applications for centralized management. Applications that are not used for a long time or are used infrequently by users are screened out through the time dimension, helping users to intelligently organize desktop applications.

[0098] In some possible implementations, the icon size of the infrequently used application folder is the same as the icon size of other applications, or the icon size of the infrequently used application folder is larger than the icon size of other applications.

[0099] In this technical solution, the icon size of the infrequently used application folder is explained to improve the feasibility of the solution. The display form of the infrequently used application folder is the same as the conventional desktop small folder. When the application is not used for a long time, it will enter the infrequently used application folder after the set or default time is triggered, helping users to intelligently organize desktop applications.

[0100] In some possible implementations, the infrequently used application and the infrequently used application folder are in the same or different desktop interfaces.

[0101] In some possible implementations, generating a non-common application folder on the desktop interface; and moving the non-common application to the non-common application folder for management may include: displaying a first prompt message on the desktop interface, the first prompt message being used to prompt whether to generate a non-common application folder to manage the non-common application? When a triggering operation of generating a non-common application folder to manage the non-common application is detected, generating a non-common application folder; and moving the non-common application to the non-common application folder for management.

[0102] Exemplarily, after the terminal device determines the infrequently used applications based on the usage data of the various applications, the first prompt information may be displayed on the desktop interface, for example: Do you want to generate an infrequently used application folder to manage the infrequently used applications? If the user clicks "Yes", the terminal device detects the triggering operation of generating an infrequently used application folder to manage the infrequently used applications, generates an infrequently used application folder, and moves the infrequently used applications to the infrequently used application folder for management; if the user clicks "No", the terminal device detects the triggering operation of not generating an infrequently used application folder to manage the infrequently used applications, and does not generate an infrequently used application folder.

[0103] In the technical solution, after the terminal device determines the infrequently used applications based on the usage data of the various applications, before generating an infrequently used application folder to manage the infrequently used applications, a first prompt message can be displayed to prompt whether to generate an infrequently used application folder? The user can select "yes" or "no" according to his actual needs, so that the user can decide whether to manage the infrequently used applications according to his needs, which can improve the user experience.

[0104] In some possible implementations, the method further includes: when a setting operation is detected, displaying a setting interface, the setting interface including a non-common application function control; and when an operation to enable the non-common application function control is detected, enabling a function for managing the non-common application.

[0105] For example, Figure 4B As shown, a schematic diagram of a setting interface including a non-common application function control in an embodiment of the present application is shown. When a setting operation is detected, the terminal device displays a setting interface, wherein the setting interface includes a non-common application function control, and when an opening operation of the non-common application function control is detected, such as a single click operation or a sliding operation, the function of managing non-common applications is opened. Thus, non-common applications can be subsequently managed through non-common application folders, or non-common applications can be hidden using a pure mode, etc.

[0106] In this technical solution, if you want to execute the function of managing infrequently used applications, you need to first enable the function of managing infrequently used applications in the setting interface before you can manage infrequently used applications.

[0107] In some possible implementations, the setting interface further includes at least one duration control, and the method may further include: determining the preset duration when a triggering operation on the target duration control is detected.

[0108] For example, Figure 4C As shown, a schematic diagram of the setting interface including at least one duration control in an embodiment of the present application. The setting interface of the terminal device includes not only a non-common application function control, but also at least one duration control (applications that have not been used for a certain period of time enter a non-common application folder, or, applications that have not been used for a certain period of time enter a dormant application folder), for example: at least one duration control includes one month, three months, six months, one year, custom, etc. When the user turns on the function of managing non-common applications, he can also select an application that is a certain distance from the current time to determine the non-common application, and then manage the non-common application.

[0109] Assuming that the user selects a one-year duration control, the terminal device determines the preset duration as one year when detecting the selection operation of the one-year duration control. Then, the terminal device can detect the usage data of each application within one year from the current time, and determine the infrequently used applications based on the usage data of each application within one year, so as to manage the infrequently used applications.

[0110] If the displayed one-month duration control, three-month duration control, six-month duration control, and one-year duration control are not what the user wants to choose, then the user can also customize the preset duration through the custom duration control. For example: if the user customizes ten months, then the terminal device can detect the usage data of each application within 10 months from the current time, and determine the infrequently used applications based on the usage data of each application within 10 months, so as to manage the infrequently used applications.

[0111] In the present technical solution, the preset duration is explained, which can be the duration set by the user. The specific user can select the duration control to obtain the preset duration, or can customize the preset duration through the custom control, so that uncommon applications can be managed, the user's personalized needs can be met, the interactivity with the user can be improved, and the feasibility of the solution can be improved.

[0112] In some possible implementations, when at least one duration control includes multiple duration controls, the number of the target duration controls is multiple, and the number corresponding to the preset durations is multiple.

[0113] Exemplarily, in the case where at least one duration control includes multiple duration controls, the user can select at least two duration controls in the same setting process, and then the number of corresponding preset durations is at least two. For example, if the user selects a three-month duration control and a one-year duration control, then the corresponding preset durations are three months and one year.

[0114] Then, the terminal device can detect the usage data of each application within three months from the current time, and determine the infrequently used applications within three months based on the usage data of each application within three months, so as to manage the infrequently used applications within three months. And the terminal device can detect the usage data of each application within one year from the current time, and determine the infrequently used applications within one year based on the usage data of each application within one year, so as to manage the infrequently used applications within one year. Therefore, two infrequently used application folders will be generated on the desktop interface of the terminal device, one is the infrequently used application folder within three months, and the other is the infrequently used application folder within one year. Figure 4D As shown, it is a schematic diagram of selecting two duration controls in the setting interface in an embodiment of the present application and correspondingly generating two infrequently used application folders.

[0115] That is, the technical solution of the embodiment of the present application not only supports the management of a frequently used application folder of a preset duration, but also supports the management of frequently used application folders of multiple preset durations, such as frequently used application folders of one year, two years, or three years.

[0116] In this technical solution, it is specifically explained that users can select multiple duration controls during a setting process, so that infrequently used applications can be classified and managed according to different preset durations, which helps users to perform subsequent processing on infrequently used applications, such as deletion.

[0117] In some possible implementations, when at least one duration control includes multiple duration controls, the user can select a duration control during this setting process, and the corresponding preset duration is one. For example, if the user selects a three-month duration control, the corresponding preset duration is three months. The terminal device can detect the usage data of each application within three months from the current time, and determine the infrequently used applications within three months based on the usage data of each application within three months, so as to manage the infrequently used applications within three months. Therefore, a folder of infrequently used applications within three months will be generated on the desktop interface of the terminal device.

[0118] In the case where at least one duration control includes multiple duration controls, the user can select a duration control during the next setting process, then the corresponding number of preset durations is one. For example, if the user selects a one-year duration control, then the corresponding preset duration is one year. The terminal device can detect the usage data of each application within one year from the current time, and determine the infrequently used applications within one year based on the usage data of each application within one year, so as to manage the infrequently used applications within one year. Therefore, a folder for infrequently used applications within one year will be generated on the desktop interface of the terminal device. At this time, the folder for infrequently used applications within three months can continue to be retained or automatically deleted, depending on the actual needs of the user.

[0119] In the present technical solution, it is specifically explained that the user can select a duration control in one setting process. If one wants to manage non-commonly used applications with multiple preset durations, then the duration control can be set multiple times, thereby classifying and managing non-commonly used applications according to different preset durations, which helps users to perform subsequent processing on non-commonly used applications, such as deletion.

[0120] In some possible implementations, when the preset usage duration and the preset usage count are both 0, the infrequently used applications can be understood as applications that have not been used within the preset duration. Then, the corresponding infrequently used application folder is the application folder that has not been used within the preset duration. For applications in folders that exceed the target preset duration, one-click deletion is supported. For example, applications in an application folder that have not been used for more than three years can be directly deleted.

[0121] In some possible implementations, reducing the display area occupied by the infrequently used application on the desktop interface may include: displaying the icon of the infrequently used application in a reduced size on the desktop interface.

[0122] For example, there are 9 applications on the desktop interface, namely APP1, APP2, APP3, APP4, APP5, APP6, APP7, APP8, and APP9. Suppose that according to the usage data of these 9 applications, the unused applications determined include APP4, APP5, and APP6. Then, the icons of APP4, APP5, and APP6 are reduced and displayed. Figure 4E As shown, it is a schematic diagram of reducing the size of the icon of the infrequently used application on the desktop interface in an embodiment of the present application.

[0123] In the present technical solution, a specific implementation method is provided for reducing the display area occupied by the infrequently used applications on the desktop interface, that is, the icons of the infrequently used applications are displayed in a reduced size on the desktop interface, thereby reducing interference with other commonly used applications on the desktop.

[0124] In some possible implementations, displaying the icon of the infrequently used application in reduced size on the desktop interface may include: displaying the icon of the infrequently used application in reduced size in an infrequently used area on the desktop interface.

[0125] Exemplarily, the unused area on the desktop interface may be the left area, the top area, etc. of the desktop interface, which may be specifically determined according to the user's usage habits and will not be elaborated here.

[0126] In the technical solution, the icons of the infrequently used applications are displayed in a reduced size in the infrequently used area on the desktop interface, thereby greatly reducing the interference with the use of other commonly used applications on the desktop.

[0127] In an embodiment of the present application, usage data of each application within a preset time period on a desktop interface is detected; the display area occupied by the infrequently used application on the desktop interface is reduced, which can specifically include generating a infrequently used application folder and moving the infrequently used application to the infrequently used application folder for management, wherein the infrequently used application is determined based on the usage data of each application within the preset time period, which can reduce interference with the use of other commonly used applications on the desktop.

[0128] In some possible implementations, detecting usage data of each application within a first preset time period on the desktop interface may include: detecting usage data of each application within a preset time period on the desktop interface when a trigger operation on the pure mode is detected;

[0129] The reducing the display area occupied by the infrequently used application on the desktop interface may include: hiding the infrequently used application according to the pure mode.

[0130] Exemplary, the triggering operation of the pure mode may include a double-click operation on a blank area of ​​the desktop interface, or a long press operation on a blank area of ​​the desktop interface, or a pull-down operation on the top of the desktop interface to display a function control interface, which includes a pure mode control, an opening operation on the pure mode control, or a specific operation (such as a long press operation) on the volume button (volume up button or volume down button), or a triggering operation on a pure mode virtual control (such as a single click, double click, long press, etc.), or a preset input operation on the desktop interface (such as drawing a circle, a cross pattern, a sliding operation, etc.), etc., which is not specifically limited in the embodiments of the present application. Figure 5A As shown, it is a schematic diagram of the trigger operation of the pure mode in the embodiment of the present application. When the trigger operation of the pure mode is detected, the step of determining the infrequently used applications is triggered. It is necessary to first detect the usage data of each application within a preset time period on the desktop interface, and then provide a basis for hiding and displaying infrequently used applications according to the pure mode.

[0131] Exemplarily, when a trigger operation related to the pure mode is detected, after detecting the usage data of each application within a preset time period on the desktop interface, the uncommonly used applications are hidden and displayed according to the pure mode, and further, applications other than the uncommonly used applications are displayed on the desktop interface. Figure 5B As shown, it is a schematic diagram of hiding and displaying the infrequently used applications according to the pure mode in an embodiment of the present application. For example, there are 9 applications on the desktop interface, namely Application 1 (Application1, APP1), APP2, APP3, APP4, APP5, APP6, APP7, APP8, and APP9. Assuming that according to the usage data of these 9 applications, the infrequently used applications determined include APP4, APP5, and APP6, then after using the pure mode, the infrequently used applications APP4, APP5, and APP6 are hidden, and the applications displayed on the desktop interface include APP1, APP2, APP3, APP7, APP8, and APP9.

[0132] In this technical solution, after the desktop interface enters the pure mode, only commonly used applications are displayed on the desktop interface, and infrequently used applications are hidden, thereby reducing the interference of infrequently used applications on commonly used applications.

[0133] In some possible implementations, applications other than the infrequently used applications are displayed in the top area, or the bottom area, or the default area of ​​the desktop interface.

[0134] Exemplarily, there are 9 applications on the desktop interface, namely Application 1 (Application1, APP1), APP2, APP3, APP4, APP5, APP6, APP7, APP8, and APP9. Assuming that based on the usage data of these 9 applications, the infrequently used applications are determined to include APP4, APP5, and APP6, then after using the pure mode, the infrequently used applications APP4, APP5, and APP6 will be hidden, and the applications displayed on the desktop interface include APP1, APP2, APP3, APP7, APP8, and APP9, which can be considered as frequently used applications. Frequently used applications can be displayed directly in the original location area, or they can be reordered and displayed in the top area, bottom area, left area, or right area of ​​the desktop interface, or they can also be displayed in the area corresponding to the adjustment operation according to the user's adjustment operation, which is not limited to the specific embodiments of the present application. Figure 5C As shown in FIG. 1 , a schematic diagram of displaying commonly used applications according to the pure mode in an embodiment of the present application is shown. Figure 5D As shown, it is another schematic diagram of displaying commonly used applications according to the pure mode in an embodiment of the present application.

[0135] In this technical solution, after the desktop interface enters the pure mode, only frequently used applications are displayed on the desktop interface, and the display positions of frequently used applications can be adjusted automatically or manually, for example, they can be set to be displayed in the default order in the settings, or displayed in order of sinking to the bottom (i.e., the bottom area) or pinning to the top (i.e., the top area). Infrequently used applications are hidden, thereby reducing the interference of infrequently used applications on frequently used applications.

[0136] In some possible implementations, the method may further include: when a recovery operation related to the pure mode is detected, displaying the infrequently used application on the desktop interface.

[0137] Exemplarily, regarding the recovery operation of the pure mode, reference may be made to the above description of the triggering operation of the pure mode, which will not be repeated here.

[0138] In this technical solution, infrequently used applications can be hidden through a trigger operation of the pure mode, or displayed through a restore operation of the pure mode, which can be determined according to user needs.

[0139] In some possible implementations, when the preset usage duration and the preset usage count are both 0, the infrequently used application may be understood as an application that has not been used within the preset duration.

[0140] In an embodiment of the present application, in a method for lightweight management of desktop applications, when a trigger operation regarding the pure mode is detected, usage data of each application within a preset time period on the desktop interface is detected; based on the usage data of each application, infrequently used applications are determined; and the infrequently used applications are hidden and displayed according to the pure mode; this is intended to help users perform refined management of applications and reduce interference with the use of other applications on the desktop interface.

[0141] like Figure 6 FIG. 1 is a schematic diagram of another embodiment of the method for managing desktop applications in an embodiment of the present application. The method may include:

[0142] 601. Detect usage data of each application program on a desktop interface within a first preset time period.

[0143] The step of managing the infrequently used application on the desktop interface may include step 602:

[0144] 602. Add a non-commonly used mark to a non-commonly used application on the desktop interface, and reduce a display area occupied by the non-commonly used application on the desktop interface.

[0145] In some possible implementations, adding a non-common identifier to a non-common application on the desktop interface and reducing the display area occupied by the non-common application on the desktop interface may include: generating a non-common application folder on the desktop interface; moving the non-common application to the non-common application folder for management; retaining the icon of the non-common application in the original location area of ​​the non-common application and adding a non-common identifier.

[0146] For example: There are 9 applications on the desktop interface, namely Application 1 (Application1, APP1), APP2, APP3, APP4, APP5, APP6, APP7, APP8, APP9. Suppose based on the usage data of these 9 applications, the infrequently used applications are determined to include APP4, APP5 and APP6. Then, after the infrequently used applications are determined, a folder can be automatically created. This folder can be named by default, such as an infrequently used application folder. Then, APP4, APP5 and APP6 are automatically moved to the infrequently used application folder for management, and an infrequently used mark is added to the original location area of ​​APP4, APP5 and APP6. Fig. 7A As shown, it is a schematic diagram of moving a non-commonly used application to a non-commonly used application folder and adding a non-commonly used mark to a non-commonly used application in an embodiment of the present application.

[0147] In the present technical solution, after the infrequently used application is moved to the infrequently used application folder for management, the icon of the infrequently used application can be retained in the original location area of ​​the infrequently used application, and an infrequently used mark can be added to prompt the user that the application is an infrequently used application and whether to delete it.

[0148] In some possible implementations, the setting interface also includes an original location area icon control for an infrequently used application, and the method may further include: upon detecting an operation to turn on the original location area icon control for the infrequently used application, executing the steps of retaining the icon for the infrequently used application and adding an infrequently used mark in the original location area of ​​the infrequently used application.

[0149] Exemplarily, the settings interface also includes an icon control for the original location area of ​​​​uncommon applications, for example: entering the dormant application folder retains the original application icon, that is, after turning on this function, the application that enters the dormant folder retains the corresponding icon in the original location area. Figure 7B As shown, it is a schematic diagram of an embodiment of the present application in which the setting interface also includes an original location area icon control of a non-common application.

[0150] If the user opens the icon control in the original location area of ​​a seldom-used application, such as by clicking or sliding, then the usage data of each application within a preset time period is subsequently detected on the desktop interface; based on the usage data of each application, the seldom-used application is determined; and steps are performed to manage the seldom-used application on the desktop interface, for example: moving the seldom-used application to a seldom-used application folder, retaining the icon of the seldom-used application in the original location area of ​​the seldom-used application, and adding a seldom-used mark instead of a commonly used mark to make it easier for users to know which are seldom-used applications, so that users can understand the purpose of the application in order to decide whether to continue using it.

[0151] In the present technical solution, an infrequently used application is moved to an infrequently used application folder. Whether to retain the icon of the infrequently used application and add an infrequently used mark in the original location area of ​​the infrequently used application can be set by the user according to his or her actual needs, thereby improving the interactivity with the user and helping the user to perform subsequent processing on the infrequently used application, such as deletion.

[0152] In the above scheme, you can add a setting item for the infrequently used application function in the desktop interface settings, which will take effect after it is turned on. Users can set how long an unused or rarely used application enters the infrequently used application folder (also called a dormant folder), or set a default time for an unused or rarely used application to enter the infrequently used application folder. Applications that enter the folder can choose to keep the icon in the original location area, or directly enter the infrequently used application folder.

[0153] In some possible implementations, the method may further include: when a deletion operation on the second target application is detected, deleting the second target application on the desktop interface.

[0154] Exemplarily, the second target application can be a non-common application or a common application, and there is no specific limitation. In the case where the second target application is a non-common application, if the icon of the second target application is not retained in the original location area of ​​the second target application, then when the second target application is deleted, the second target application is only deleted from the non-common application folder on the desktop interface; if the icon of the second target application is retained in the original location area of ​​the second target application, then when the second target application is deleted, the second target application is deleted from both the non-common application folder on the desktop interface and the original location area of ​​the second target application.

[0155] In this technical solution, the scenarios in which the second target application is deleted are described in detail, thereby improving the feasibility of the solution.

[0156] It should be noted that, in the embodiment of the present application, the opening or closing operation of the uncommon application function control in the setting interface and the opening or closing operation of at least one duration control can refer to Figure 3 The description in the illustrated embodiment will not be repeated here.

[0157] In an embodiment of the present application, in a method of lightweight management of desktop applications, usage data of each application within a first preset time period on the desktop interface is detected; a non-common application folder is generated on the desktop interface; and the non-common application is moved to the non-common application folder for management. In order to help users manage applications in a refined manner, non-common applications can be moved to non-common application folders for management. Optionally, users can clean up infrequently used applications in a timely manner. Reduce interference with the use of other applications on the desktop interface. For example: for some special scenarios, such as when users have forgotten the specific functions of an application due to long-term non-use, special marks (non-common marks) can be used to help users understand the purpose of the application in a timely manner, so that users can easily understand the purpose of the application in order to decide whether to continue using it.

[0158] like Figure 8 FIG. 1 is a schematic diagram of another embodiment of the method for managing desktop applications in an embodiment of the present application. The method may include:

[0159] 801. Detect usage data of each application program on a desktop interface within a first preset time period.

[0160] The step of managing the infrequently used application on the desktop interface may include step 802:

[0161] 802. Add a non-commonly used mark to the non-commonly used application on the desktop interface.

[0162] Exemplarily, the infrequently used mark may include a sleeping mark, or infrequently used text, or some other marks, which are not specifically limited in the embodiments of the present application. The infrequently used mark is used to indicate that the corresponding application is an infrequently used application.

[0163] In some possible implementations, the method may further include: when a deletion operation on a second target application is detected, deleting the second target application on the desktop interface, the second target application being one of the infrequently used applications.

[0164] Exemplarily, the second target application can be a frequently used application or a frequently used application, and there is no specific limitation. Because a frequently used application is marked with a frequently used label, it is convenient for users to identify which applications are frequently used applications, thereby facilitating users to understand the purpose of frequently used applications so as to decide whether to continue using them.

[0165] For example, there are 9 applications on the desktop interface, namely Application 1 (APP1), APP2, APP3, APP4, APP5, APP6, APP7, APP8, and APP9. Suppose that based on the usage data of these 9 applications, the infrequently used applications are determined to include APP4, APP5, and APP6. Then, after the infrequently used applications are determined, infrequently used labels are added to the original location areas of APP4, APP5, and APP6. Fig. 9 As shown, it is a schematic diagram of adding a non-common identifier to a non-common application in an embodiment of the present application.

[0166] In this technical solution, a non-common identification is added to non-common applications, so that users can understand the purpose of non-common applications and decide whether to continue using them. If the user deletes the second target application, it can reduce interference with the use of other applications on the desktop interface.

[0167] In some possible implementations, when the preset usage duration and the preset usage count are both 0, the infrequently used application may be understood as an application that has not been used within the preset duration.

[0168] In the embodiment of the present application, in the method of lightweight management of desktop applications provided, the usage data of each application within a first preset time period on the desktop interface is detected; and a non-usual mark is added to the non-usual application. It is intended to help users to manage applications in a refined manner. Adding a non-usual mark to the non-usual application can help users to clean up infrequently used applications in a timely manner. Reduce interference with the use of other applications on the desktop interface.

[0169] In some possible implementations, the method may further include: detecting usage data of each application within a first preset time period on the desktop interface; determining frequently used applications based on the usage data of each application; and performing folder management on the frequently used applications.

[0170] For example, there are 9 applications on the desktop interface, namely Application 1 (Application1, APP1), APP2, APP3, APP4, APP5, APP6, APP7, APP8, and APP9. Assuming that based on the usage data of these 9 applications, the commonly used applications determined include APP1, APP2, APP3, APP7, APP8, and APP9, these commonly used applications can also be managed through folders.

[0171] In this technical solution, commonly used applications can also be managed in folders, so that the applications on the desktop interface can be classified, thereby improving the cleanliness of the desktop interface.

[0172] like Fig.10 As shown, it is a schematic diagram of an embodiment of a management device for a desktop application in an embodiment of the present application, which may include:

[0173] The detection module 1001 is used to detect the usage data of each application program within a preset time period on the desktop interface;

[0174] Display module 1002 is used to add a non-commonly used mark to a non-commonly used application on the desktop interface, and / or to reduce the display area occupied by the non-commonly used application on the desktop interface; wherein the non-commonly used mark is used to indicate that the non-commonly used application is an application whose usage frequency within the preset time period is less than or equal to a usage frequency threshold, and the non-commonly used application is determined based on usage data of each application within the preset time period.

[0175] Optionally, in some possible implementations, the display module 1002 is specifically configured to generate a non-commonly used application folder on the desktop interface; and move the non-commonly used application to the non-commonly used application folder for management.

[0176] Optionally, in some possible implementations, the display module 1002 is used to generate a non-common application folder on the desktop interface; move the non-common application to the non-common application folder for management; retain the icon of the non-common application in the original location area of ​​the non-common application, and add a non-common mark.

[0177] Optionally, in some possible implementations, the display module 1002 is further configured to display a setting interface when a setting operation is detected, wherein the setting interface includes a non-common application function control;

[0178] The processing module 1003 is specifically configured to enable the function of managing the infrequently used application when an enabling operation on the infrequently used application function control is detected.

[0179] Optionally, in some possible implementations, the setting interface further includes at least one duration control, and the processing module 1003 is further used to determine the preset duration when a triggering operation on the target duration control is detected.

[0180] Optionally, in some possible implementations, the setting interface also includes an original location area icon control for an infrequently used application, and the display module 1002 is also used to, upon detecting an operation to turn on the original location area icon control for the infrequently used application, execute the steps of retaining the icon of the infrequently used application and adding an infrequently used mark in the original location area of ​​the infrequently used application.

[0181] Optionally, in some possible implementations, the detection module 1001 is specifically configured to detect usage data of each application within a preset time period on the desktop interface when a trigger operation on the pure mode is detected;

[0182] The display module 1002 is further configured to hide and display the infrequently used application according to the pure mode.

[0183] like Fig.11 As shown, it is a schematic diagram of an embodiment of a terminal device in an embodiment of the present application, which may include: Fig.10 The desktop application management device is shown.

[0184] like Fig.12 FIG. 1 is a schematic diagram of another embodiment of a terminal device in an embodiment of the present application. Fig.12 A detailed introduction to the various components of the mobile phone in the terminal device:

[0185] The RF circuit 1210 can be used for receiving and sending signals during the process of sending and receiving information or making calls. In particular, after receiving the downlink information of the base station, it is sent to the processor 1280 for processing; in addition, the designed uplink data is sent to the base station. Generally, the RF circuit 1210 includes but is not limited to an antenna, at least one amplifier, a transceiver, a coupler, a low noise amplifier (Low Noise Amplifier, LNA), a duplexer, etc. In addition, the RF circuit 1210 can also communicate with the network and other devices through wireless communication. The above-mentioned wireless communication can use any communication standard or protocol, including but not limited to Global System of Mobile communication (Global System of Mobile communication, GSM), General Packet Radio Service (General Packet Radio Service, GPRS), Code Division Multiple Access (Code Division Multiple Access, CDMA), Wideband Code Division Multiple Access (Wideband Code Division Multiple Access, WCDMA), Long Term Evolution (Long Term Evolution, LTE), email, Short Messaging Service (SMS), etc.

[0186] The memory 1220 can be used to store software programs and modules. The processor 1280 executes various functional applications and data processing of the mobile phone by running the software programs and modules stored in the memory 1220. The memory 1220 can mainly include a program storage area and a data storage area, wherein 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 according to the use of the mobile phone (such as audio data, a phone book, etc.), etc. In addition, the memory 1220 can include a high-speed random access memory, and can also include a non-volatile memory, such as at least one disk storage device, a flash memory device, or other volatile solid-state storage devices.

[0187] The input unit 1230 can be used to receive input digital or character information, and to generate key signal input related to the user settings and function control of the mobile phone. Specifically, the input unit 1230 may include a touch panel 1231 and other input devices 1232. The touch panel 1231, also known as a touch screen, can collect the user's touch operation on or near it (such as the user's operation on the touch panel 1231 or near the touch panel 1231 using any suitable object or accessory such as a finger, stylus, etc.), and drive the corresponding connection device according to a pre-set program. Optionally, the touch panel 1231 may include two parts: a touch detection device and a touch controller. Among them, the touch detection device detects the user's touch orientation, detects the signal brought by the touch operation, and transmits the signal to the touch controller; the touch controller receives the touch information from the touch detection device, converts it into the touch point coordinates, and then sends it to the processor 1280, and can receive and execute the command sent by the processor 1280. In addition, the touch panel 1231 can be implemented in various types such as resistive, capacitive, infrared, and surface acoustic waves. In addition to the touch panel 1231, the input unit 1230 may also include other input devices 1232. Specifically, other input devices 1232 may include but are not limited to one or more of a physical keyboard, function keys (such as volume control keys, switch keys, etc.), a trackball, a mouse, a joystick, etc.

[0188] The display unit 1240 can be used to display information input by the user or information provided to the user and various menus of the mobile phone. The display unit 1240 may include a display panel 1241. Optionally, the display panel 1241 may be configured in the form of a liquid crystal display (LCD), an organic light-emitting diode (OLED), etc. Further, the touch panel 1231 may cover the display panel 1241. When the touch panel 1231 detects a touch operation on or near it, it is transmitted to the processor 1280 to determine the type of touch event. Subsequently, the processor 1280 provides a corresponding visual output on the display panel 1241 according to the type of touch event. Although in Fig.12 In the embodiment, the touch panel 1231 and the display panel 1241 are used as two independent components to realize the input and output functions of the mobile phone, but in some embodiments, the touch panel 1231 and the display panel 1241 can be integrated to realize the input and output functions of the mobile phone.

[0189] The mobile phone may also include at least one sensor 1250, such as a light sensor, a motion sensor, and other sensors. Specifically, the light sensor may include an ambient light sensor and a proximity sensor, wherein the ambient light sensor may adjust the brightness of the display panel 1241 according to the brightness of the ambient light, and the proximity sensor may turn off the display panel 1241 and / or the backlight when the mobile phone is moved to the ear. As a type of motion sensor, the accelerometer sensor can detect the magnitude of acceleration in all directions (generally three axes), and can detect the magnitude and direction of gravity when stationary. It can be used for applications that identify the posture of the mobile phone (such as horizontal and vertical screen switching, related games, magnetometer posture calibration), vibration recognition related functions (such as pedometer, tapping), etc.; as for other sensors that can be configured in the mobile phone, such as gyroscopes, barometers, hygrometers, thermometers, infrared sensors, etc., they will not be repeated here.

[0190] The audio circuit 1260, the speaker 1261, and the microphone 1262 can provide an audio interface between the user and the mobile phone. The audio circuit 1260 can transmit the received audio data to the speaker 1261 after converting the received audio data into an electrical signal, which is converted into a sound signal for output; on the other hand, the microphone 1262 converts the collected sound signal into an electrical signal, which is received by the audio circuit 1260 and converted into audio data, and then the audio data is output to the processor 1280 for processing, and then sent to another mobile phone through the RF circuit 1210, or the audio data is output to the memory 1220 for further processing.

[0191] Wi-Fi is a short-range wireless transmission technology. The mobile phone can help users send and receive emails, browse web pages and access streaming media through the Wi-Fi module 1270, which provides users with wireless broadband Internet access. Fig.12 A Wi-Fi module 1270 is shown, but it is understandable that it is not an essential component of the mobile phone and can be omitted as needed without changing the essence of the invention.

[0192] The processor 1280 is the control center of the mobile phone. It uses various interfaces and lines to connect various parts of the entire mobile phone. By running or executing software programs and / or modules stored in the memory 1220, and calling data stored in the memory 1220, it executes various functions of the mobile phone and processes data, thereby monitoring the mobile phone as a whole. Optionally, the processor 1280 may include one or more processing units; preferably, the processor 1280 may integrate an application processor and a modem processor, wherein the application processor mainly processes the operating system, user interface, and application programs, and the modem processor mainly processes wireless communications. It is understandable that the above-mentioned modem processor may not be integrated into the processor 1280.

[0193] The mobile phone also includes a power supply 1290 (such as a battery) for supplying power to various components. Preferably, the power supply can be logically connected to the processor 1280 through a power management system, so that the power management system can manage functions such as charging, discharging, and power consumption management.

[0194] Although not shown, the mobile phone may also include a camera, a Bluetooth module, etc., which will not be described in detail here.

[0195] In the embodiment of the present application, the processor 1280 is used to detect the usage data of each application within a preset time period on the desktop interface;

[0196] The display unit 1240 is used to add a non-common mark to a non-common application on the desktop interface, and / or to reduce a display area occupied by the non-common application on the desktop interface;

[0197] The infrequently used identifier is used to indicate that the infrequently used application is an application whose usage frequency within the preset duration is less than or equal to a usage frequency threshold, and the infrequently used application is determined based on usage data of each application within the preset duration.

[0198] Optionally, in some possible implementations, the display unit 1240 is specifically configured to generate a non-commonly used application folder on the desktop interface; and move the non-commonly used application to the non-commonly used application folder for management.

[0199] Optionally, in some possible implementations, the display unit 1240 is used to generate a non-commonly used application folder on the desktop interface; move the non-commonly used application to the non-commonly used application folder for management; retain the icon of the non-commonly used application in the original location area of ​​the non-commonly used application, and add a non-commonly used mark.

[0200] Optionally, in some possible implementations, the display unit 1240 is further configured to display a setting interface when a setting operation is detected, wherein the setting interface includes a non-common application function control;

[0201] The processor 1280 is specifically configured to enable the function of managing the infrequently used application when an enabling operation on the infrequently used application function control is detected.

[0202] Optionally, in some possible implementations, the setting interface further includes at least one duration control, and the processor 1280 is further configured to determine the preset duration when a triggering operation on the target duration control is detected.

[0203] Optionally, in some possible implementations, the setting interface also includes an original location area icon control for an infrequently used application, and the display unit 1240 is further used to, upon detecting an operation to turn on the original location area icon control for the infrequently used application, execute the steps of retaining the icon of the infrequently used application and adding an infrequently used mark in the original location area of ​​the infrequently used application.

[0204] Optionally, in some possible implementations, the processor 1280 is specifically configured to detect usage data of each application within a preset time period on the desktop interface when a trigger operation on the pure mode is detected;

[0205] The display unit 1240 is further configured to hide and display the infrequently used application according to the pure mode.

[0206] 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 program 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 devices. 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 site, computer, server or data center by wired (e.g., coaxial cable, optical fiber, digital subscriber line (Digital Subscriber Line, DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) mode to another website site, computer, server or data center. The computer-readable storage medium can be any available medium that a computer can store or a data storage device such as a server, data center, etc. that contains one or more available media integrated. The available medium may be a magnetic medium (eg, a floppy disk, a hard disk, a magnetic tape), an optical medium (eg, a DVD), or a semiconductor medium (eg, a solid state disk (SSD)).

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

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

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

[0210] In addition, each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit. The above-mentioned integrated unit may be implemented in the form of hardware or in the form of software functional units.

[0211] If the integrated unit is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present application is essentially or the part that contributes to the prior art or all or part of the technical solution can be embodied in the form of a software product, and the computer software product is stored in a storage medium, including a number of instructions to enable a computer device (which can be a personal computer, a server, or a network device, etc.) to perform all or part of the steps of the method described in each embodiment of the present application. The aforementioned storage medium includes: various media that can store program codes, such as a USB flash drive, a mobile hard disk, a read-only memory (ROM), a random access memory (RAM), a disk or an optical disk.

[0212] As described above, the above embodiments are only used to illustrate the technical solutions of the present application, rather than to limit them. Although the present application has been described in detail with reference to the aforementioned embodiments, those skilled in the art should understand that they can still modify the technical solutions described in the aforementioned embodiments, or make equivalent replacements for some of the technical features therein. However, these modifications or replacements do not deviate the essence of the corresponding technical solutions from the spirit and scope of the technical solutions of the embodiments of the present application.

Claims

1. A method for managing a desktop application, characterized in that: include: Detect usage data of each application within a preset time period on the desktop interface; Adding a non-common mark to a non-common application on the desktop interface, and / or reducing a display area occupied by the non-common application on the desktop interface; The infrequently used identifier is used to indicate that the infrequently used application is an application whose usage frequency within the preset duration is less than or equal to a usage frequency threshold, and the infrequently used application is determined based on usage data of each application within the preset duration.

2. The method according to claim 1, characterized in that The reducing the display area occupied by the uncommonly used application on the desktop interface comprises: Create a folder for uncommon applications on the desktop interface; The infrequently used application is moved to the infrequently used application folder for management.

3. The method according to claim 1, characterized in that The adding of an uncommon mark to an uncommon application on the desktop interface and reducing a display area occupied by the uncommon application on the desktop interface comprises: Create a folder for uncommon applications on the desktop interface; Moving the infrequently used application to the infrequently used application folder for management; In the original location area of ​​the infrequently used application, the icon of the infrequently used application is retained, and an infrequently used mark is added.

4. The method according to any one of claims 1 to 3, characterized in that The method further comprises: In the case where a setting operation is detected, displaying a setting interface, the setting interface including non-common application function controls; When an opening operation of the infrequently used application function control is detected, a function for managing the infrequently used application is opened.

5. The method according to claim 4, characterized in that The setting interface further includes at least one duration control, and the method further includes: When a trigger operation on the target duration control is detected, the preset duration is determined.

6. The method according to claim 4, characterized in that The setting interface also includes an original location area icon control of a non-common application, and the method further includes: When an opening operation of the icon control in the original location area of ​​the infrequently used application is detected, the steps of retaining the icon of the infrequently used application and adding an infrequently used mark are performed in the original location area of ​​the infrequently used application.

7. The method according to claim 1, characterized in that The detecting of usage data of each application program within a preset time period on the desktop interface includes: When a trigger operation related to the pure mode is detected, the usage data of each application within a preset time period on the desktop interface is detected; The reducing the display area occupied by the uncommonly used application on the desktop interface comprises: The infrequently used applications are hidden and displayed according to the pure mode.

8. A desktop application management device, characterized in that: include: A detection module, used to detect usage data of each application within a preset time period on the desktop interface; A display module is used to add a non-commonly used mark to a non-commonly used application on the desktop interface, and / or to reduce the display area occupied by the non-commonly used application on the desktop interface; wherein the non-commonly used mark is used to prompt that the non-commonly used application is an application whose usage frequency within the preset time period is less than or equal to a usage frequency threshold, and the non-commonly used application is determined based on usage data of each application within the preset time period.

9. A terminal device, characterized in that: include: A memory and a processor, wherein the memory stores a computer program that can be run on the processor, and when the terminal device executes the program, the method according to any one of claims 1 to 7 is implemented.

10. A computer-readable storage medium having a computer program stored thereon, characterized in that: When the computer program is executed by a processor, the method according to any one of claims 1 to 7 is implemented.

Images