WO2017024821A1

WO2017024821A1 - Application processing method, mobile terminal, and computer-readable storage medium

Info

Publication number: WO2017024821A1
Application number: PCT/CN2016/080913
Authority: WO
Inventors: 李昌达
Original assignee: 中兴通讯股份有限公司
Priority date: 2015-08-07
Filing date: 2016-05-03
Publication date: 2017-02-16
Also published as: CN106445572A

Abstract

Provided are an application processing method, mobile terminal, and computer-readable storage medium, the method comprising: when it is detected that an installation package of a first application has been downloaded and is ready to be installed, obtaining an identifier and a type of the first application from the installation package; obtaining an application list, wherein the application list stores an identifier and/or a type of a non-installable application; and if the identifier or the type of the first application is stored on the application list, terminating installation of the first application.

Description

Application processing method, mobile terminal and computer readable storage medium

Technical field

The present application relates to, but is not limited to, Internet technologies, and in particular, to an application processing method, a mobile terminal, and a computer readable storage medium.

Background technique

With the intelligentization of mobile terminals, more and more applications are installed on mobile terminals. In daily life, the user intentionally or unintentionally installs various applications on the mobile terminal, and after the user uses this application, the application with good user experience is retained, and the application with poor user experience is uninstalled. For the user, the user does not want to install such an application with a bad user experience. However, the next time the user may download the installation package of the application with poor user experience, or other applications will bundle the application with poor user experience. Therefore, these applications with poor user experience will be installed again, and the user needs to experience it again. , delete again, this greatly reduces the user experience.

Summary of the invention

The following is an overview of the topics detailed in this document. This Summary is not intended to limit the scope of the claims.

The embodiment of the invention provides an application processing method, a mobile terminal and a computer readable storage medium, which can enable the user to manually stop installing the non-installable application and improve the user experience.

An application processing method includes:

When it is detected that the installation package of the first application is downloaded and ready to be installed, obtaining the identifier and type of the first application from the installation package;

Obtaining an application list, where the application list stores an identifier and/or a type of the application that is not installable;

When the identifier or type of the first application is stored in the application list, the installation of the first application is terminated.

Optionally, the method further includes: adding or deleting an identifier and a type of the one or more applications in the application list according to an indication of the user, to obtain a new application, before acquiring the application list. List.

Optionally, the method further includes:

Obtaining an identifier of the second application when the second application needs to be uninstalled before acquiring the application list;

Generating and displaying first query information according to the identifier of the second application, where the first query information is used to determine to the user whether the second application is an uninstallable application;

Receiving an instruction sent by the user that the second application is an uninstallable application;

Obtaining the list of applications;

Determining whether the identifier of the second application is stored in the application list;

When the identifier of the second application is not stored in the application list, the identifier of the second application is added to the application list to obtain a new application list.

Optionally, the method further includes:

Obtaining the identifier and type of the second application when the second application needs to be uninstalled before acquiring the application list;

Receiving, by the user, a first instruction that indicates that the second application is an uninstallable application;

And generating, according to the type of the second application, second query information, where the second query information is used to determine, to the user, whether an application of the same type as the second application is an uninstallable application;

Receiving, by the user, an application whose indication is the same as the type of the second application is a second instruction of an application that is not installable;

Obtaining the list of applications;

Determining whether the type of the second application is stored in the application list;

When the type of the second application is not stored in the application list, the class of the second application is The type is added to the application list to get a new application list.

Optionally, the method further includes:

Receiving, by the user, an instruction indicating that the application of the same type as the second application is not a non-installable application;

Obtaining the list of applications;

When the identifier of the second application is stored in the application list, the identifier of the second application is deleted from the application list to obtain a new application list.

Optionally, the method further includes:

After obtaining the new application list, download the stored application list from the cloud storage;

When the new application list is different from the stored application list, the new application list is merged with the stored application list, and the merged application list is uploaded.

A mobile terminal includes:

An obtaining unit, configured to: when detecting that the installation package of the first application is downloaded and ready to be installed, obtain the identifier and type of the first application from the installation package;

An obtaining unit, configured to obtain the application list, where the application list stores an identifier and/or a type of an application that is not installable;

And a termination unit, configured to terminate installation of the first application when the identifier or type of the first application is stored in the application list.

Optionally, the mobile terminal further includes:

The adding and subtracting unit is configured to add or delete an identifier and a type of the one or more applications in the application list according to an instruction of the user before obtaining the application list, to obtain a new application list.

Optionally,

The obtaining unit is further configured to acquire an identifier of the second application when the second application needs to be uninstalled before acquiring the application list;

The mobile terminal further includes:

a generating unit, configured to generate and display first query information according to the identifier of the second application, where the first query information is used to determine, by the user, whether the second application is an uninstallable application;

a receiving unit, configured to receive an instruction sent by the user that indicates that the second application is an uninstallable application;

The obtaining unit is further configured to acquire the application list;

a determining unit, configured to determine whether the identifier of the second application is stored in the application list;

The adding and subtracting unit is further configured to: when the identifier of the second application is not stored in the application list, add the identifier of the second application to the application list to obtain a new application list.

Optionally,

The obtaining unit is further configured to acquire the identifier and type of the second application when the second application needs to be uninstalled before acquiring the application list;

The generating unit is further configured to generate and display first query information according to the identifier of the second application, where the first query information is used to determine, by the user, whether the second application is an uninstallable application;

The receiving unit is further configured to receive a first instruction sent by the user that indicates that the second application is an uninstallable application;

The generating unit is further configured to generate and display second query information according to the type of the second application, where the second query information is used to determine, to the user, whether an application of the same type as the second application is Is an application that cannot be installed;

The receiving unit is further configured to receive, by the user, a second instruction that indicates that the application of the same type as the second application is an application that is not installable;

The obtaining unit is further configured to acquire the application list;

The determining unit is further configured to determine whether the type of the second application is stored in the application list;

The adding and subtracting unit is further configured to: when the type of the second application is not stored in the application list, add the type of the second application to the application list to obtain a new application list.

Optionally,

The receiving unit is further configured to receive, by the user, a third instruction that indicates that the application of the same type as the second application is not an uninstallable application;

The obtaining unit is further configured to acquire the application list;

The determining unit is further configured to determine whether the identifier of the second application is stored in the application list;

The adding and subtracting unit is further configured to: when the identifier of the second application is stored in the application list, delete the identifier of the second application from the application list to obtain a new application list.

Optionally, the mobile terminal further includes:

a transmission unit configured to download a list of stored applications from the cloud storage;

a merging unit, configured to merge the new application list with the stored application list when the new application list is different from the stored application list, and upload the merged application list to the cloud storage.

A computer readable storage medium storing computer executable instructions that, when executed by a processor, implement the described application processing method.

In the solution of the embodiment of the present invention, the mobile terminal determines whether it can be installed from the application to be installed by using the identifier and/or type of the application that cannot be installed in the application list, and if not, can stop the installation. This eliminates the need for users to manually stop installing non-installable applications, which simplifies user operations and improves the user experience.

BRIEF abstract

FIG. 1 is a flowchart of an application processing method according to an embodiment of the present invention;

2 is a flowchart of another application processing method according to an embodiment of the present invention;

FIG. 3 is a flowchart of still another application processing method according to an embodiment of the present invention;

4 is a schematic diagram of a window corresponding to a first inquiry message displayed by a mobile terminal according to an embodiment of the present invention; Figure

5 is a schematic diagram of a window corresponding to a second inquiry message displayed by a mobile terminal according to an embodiment of the present invention;

FIG. 6 is a schematic structural diagram of a mobile terminal according to an embodiment of the present disclosure;

FIG. 7 is a schematic structural diagram of another mobile terminal according to an embodiment of the present invention.

Embodiments of the invention

Embodiments of the present invention will be described below with reference to the accompanying drawings. It should be noted that, in the case of no conflict, the features in the embodiments and the embodiments in the present application may be arbitrarily combined with each other.

Embodiment 1

The embodiment of the present invention provides an application processing method, which is applied to a mobile terminal, and the mobile terminal may include a mobile phone, a notebook, a tablet computer, a POS machine, or even a vehicle-mounted computer. As shown in FIG. 1 , the method includes steps 101-103. :

Step 101: When it is detected that the installation package of the first application is downloaded and ready to be installed, obtain the identifier and type of the first application from the installation package.

Here, the identifier may be an application-specific identifier such as the name of the application, and the type may be divided according to the function of the application. For example, some applications have anti-virus functions, and the corresponding type is anti-virus; some applications have a phone book, and the corresponding type is a phone book.

Step 102: Acquire an application list, where the application list stores an identifier and/or a type of the application that is not installable.

In general, applications that cannot be installed are applications that do not have a good user experience.

Step 103: When the identifier or type of the first application is stored in the application list, the installation of the first application is terminated.

When the identifier or type of the first application is stored in the application list, the first application is an application that cannot be installed, and therefore, the first application is terminated, and at the same time, the installation package of the first application may be deleted.

The mobile terminal is installed from the identity and/or type of the application that cannot be installed in the application list. The application determines if it can be installed, and if it can't be installed, stops the installation. In this way, the user does not need to manually stop installing the non-installable application, thereby simplifying the user's operation and improving the user experience.

Optionally, before step 102, the embodiment of the present invention provides three solutions to obtain an application list.

The first solution includes: adding or deleting the identifier and type of one or more applications in the application list according to the user's instruction, to obtain a new application list.

When the user wants to re-use a non-installable application, the user clicks into the application settings interface and clicks to delete the non-installable application. When the user wants to install at least two applications at the same time, and the types of the two applications are types of non-installable applications, the user clicks into the application setting interface, clicks to delete the type of the non-installable application; when the user does not like an application Click to enter the application settings interface, click to add the application's logo to the application list; when an application is already installed, other applications of the same type do not need to be installed. At this time, the user clicks into the application settings interface, click to add the type to the application list. .

The second solution includes: when the second application needs to be uninstalled, acquiring an identifier of the second application; generating, according to the identifier of the second application, the first query information, where the first query information is used to determine, by the user, whether the second application is An application that is not installable; an instruction sent by the user indicating that the second application is an uninstallable application; obtaining an application list; determining whether an identifier of the second application is stored in the application list; and not storing the identifier of the second application in the application list, Add the identity of the second application to the application list to get a new application list. In this case, since the application list only stores the identifier of the application, step 101 may acquire only the identifier of the first application from the viewpoint of resource saving.

The third solution includes: when the second application needs to be uninstalled, acquiring the identifier and type of the second application; generating and displaying the first query information according to the identifier of the second application, where the first query information is used to determine the second application to the user Whether it is an uninstallable application; receiving a first instruction sent by the user indicating that the second application is an uninstallable application; generating and displaying the second query information according to the type of the second application, The second query information is used to determine to the user whether the application of the same type as the second application is an uninstallable application; the second instruction of the application sent by the user indicating that the application of the same type as the second application is a non-installable application; The application list determines whether the type of the second application is stored in the application list; when the type of the second application is not stored in the application list, the type of the second application is added to the application list to obtain a new application list.

For the third solution, the method further includes: receiving, by the user, a third instruction indicating that the application of the same type as the second application is not an uninstallable application; acquiring the application list; determining whether the second application is stored in the application list When the identifier of the second application is stored in the application list, the identifier of the second application is deleted from the application list to obtain a new application list.

For the above three solutions, the method further includes: after obtaining the new application list, downloading the stored application list from the cloud storage; when the new application list is different from the stored application list, the new application list is The stored application list is merged, and the merged application list is uploaded to the cloud storage. In this way, the user uses the new mobile terminal, and the application list does not need to be re-established, and can be directly downloaded from the cloud storage.

It is worth noting that the first solution can be used in combination with the second and third solutions.

Embodiment 2

An embodiment of the present invention provides an application processing method, which is applied to a smart phone. As shown in FIG. 2, the method includes steps 201-206:

Step 201: Detect an installation situation of the application.

Step 202: When it is detected that the installation package of the A application is downloaded and ready to be installed, obtain the name and type of the A application.

Here, the name of the A application can be the package name of the installation package. The type of application can be divided according to the application function. For example, the application for smart phone security is a security application, and the application for mobile phone photography is a camera application. When one of the security applications is installed, other applications of the security application need not be installed, thereby reducing the memory usage of the smartphone and increasing the speed of the smartphone. Improve the user experience.

Step 203: Acquire an application list.

Here, when the smartphone stores the application list, it is obtained from the storage area of the smart phone; when the smart phone application list does not store the application list, the application list is downloaded from the cloud storage.

Step 204: Determine whether the name or type of the A application is stored in the application list. If the name or type of the A application is stored, step 206 is performed; if the name or type of the A application is not stored, step 205 is performed.

Step 205: Install the A application, and end the process.

Step 206: Terminate the installation of the A application, and delete the installation package of the A application.

Embodiment 3

An embodiment of the present invention provides an application processing method, which is applied to a smart phone. As shown in FIG. 3, the method may further include steps 301-314:

Step 301: Generate an application list, and upload the application list to the cloud storage.

Here, in the memory of the smartphone, it is necessary to divide an area for storing the application sequence table, and the application list of the embodiment stores the name and/or type of the application that cannot be installed.

In the initial state, the application list can be empty.

Step 302: When the A application needs to be uninstalled, obtain the name and type of the A application.

Here, when the A application needs to be uninstalled, the smart phone enters the uninstall page of the A application. When the user has not clicked the uninstall button, the A application does not actually enter the uninstall process, but only enters the uninstall preparation process of the A application.

Step 303: Generate and display first query information according to the name of the A application.

Here, the first inquiry information is used to determine to the user whether the A application is an uninstallable application. Among them, the application that cannot be installed refers to the application that permanently blocks the installation.

As shown in Figure 4, the screen of the smartphone pops up a window showing "A application is a permanently blocked application", and two buttons are displayed in the window below, "Yes" and "No". The user presses the button "Yes" or "No" according to his or her own decision. When the user presses the button "No", it indicates that the user does not wish to permanently block the installation of the A application; when the user presses the button "Yes", it indicates that the user wishes to permanently block the installation of the A application.

Step 304: Receive a first instruction sent by a user.

Here, the first instruction indicates that the A application is an application that is not installable.

Step 305: Generate and display second query information according to the type of the A application.

Here, the second inquiry information is used to determine to the user whether the application of the same type as the A application is an application that is not installable.

As shown in Figure 5, the screen of the smartphone can pop up a window again, showing "whether the application with the same type of A application is an application that permanently blocks the installation." The following window also displays two buttons, "Yes" and "Yes" respectively. no". The user presses the button "Yes" or "No" according to his or her own decision. When the user presses the button "Yes", the user wishes to permanently block the installation of such an application; when the user presses the button "No", the user does not wish to permanently prevent the installation of such an application.

Step 306: Receive a third instruction sent by the user, and uninstall the A application.

Here, the third instruction indicates that the application of the same type as the A application is not an application that is not installable.

Step 307: Determine whether the name of the A application is stored in the application sequence table. If the name of the A application is stored in the application sequence table, the process ends; if the name of the A application is not stored in the application sequence table, step 308 is performed.

Step 308: Add the name of the A application to the application list, and perform step 312.

Step 309: Receive a second instruction sent by the user, and uninstall the A application.

Here, the second instruction indicates that the application of the same type as the A application is an application that is not installable.

Step 310: Determine whether the type of the A application is stored in the application sequence table. If the type of the A application is stored in the application sequence table, the process ends; if the application sequence table does not store the type of the A application, step 311 is performed.

Step 311: Add the type of the A application to the application list.

Step 312: When the smart phone has a network connection, obtain a list of applications stored in the cloud storage.

Step 313: Determine whether the added application list is the same as the stored application list. If the added application list is the same as the stored application list, the process ends; if the joined application list and the stored application list are different, step 314 is performed.

Step 314: Combine the added application list with the stored application list, and upload the merged application list to the cloud storage.

It is worth noting that when the user chooses not to permanently prevent the installation of the A application, it is also necessary to uninstall the A application.

Embodiment 4

The embodiment of the present invention provides a mobile terminal 40. As shown in FIG. 6, the mobile terminal 40 may include:

The obtaining unit 401 is configured to: when detecting that the installation package of the first application is downloaded and ready to be installed, obtain the identifier and type of the first application from the installation package;

The obtaining unit 401 is further configured to acquire an application list, where the application list stores an identifier and/or a type of the application that is not installable.

The termination unit 402 is configured to terminate the installation of the first application when the identifier or type of the first application is stored in the application list.

According to the identification and/or type of the application that cannot be installed in the application list, it is determined from the application to be installed whether it can be installed, and if it can not be installed, the installation is stopped. In this way, the user does not need to manually stop installing the non-installable application, thereby simplifying the user's operation and improving the user experience.

Optionally, as shown in FIG. 7, the mobile terminal 40 further includes:

The adding and subtracting unit 403 is configured to add or delete an identifier and a type of one or more applications in the application list according to an instruction of the user before obtaining the application list, to obtain a new application list.

Optionally, the obtaining unit 401 is further configured to: before acquiring the application list, when When the second application needs to be uninstalled, the identifier of the second application is obtained.

As shown in FIG. 7, the mobile terminal 40 further includes:

The generating unit 404 is configured to generate and display first query information according to the identifier of the second application, where the first query information is used to determine to the user whether the second application is an uninstallable application.

The receiving unit 405 is configured to receive an instruction sent by the user that indicates that the second application is an uninstallable application.

The obtaining unit 401 is further configured to acquire the application list.

The determining unit 406 is configured to determine whether the identifier of the second application is stored in the application list;

The adding and subtracting unit 403 is further configured to: when the identifier of the second application is not stored in the application list, add the identifier of the second application to the application list to obtain a new application list.

Optionally, the obtaining unit 401 is further configured to acquire the identifier and type of the second application when the second application needs to be uninstalled before acquiring the application list.

The generating unit 404 is further configured to generate and display first query information according to the identifier of the second application, where the first query information is used to determine to the user whether the second application is an uninstallable application.

The receiving unit 405 is further configured to receive a first instruction sent by the user that indicates that the second application is an uninstallable application.

The generating unit 404 is further configured to generate and display second query information according to the type of the second application, where the second query information is used to determine, to the user, whether an application of the same type as the second application is Uninstallable apps.

The receiving unit 405 is further configured to receive a second instruction sent by the user indicating that the application of the same type as the second application is an application that is not installable.

The obtaining unit 401 is further configured to acquire the application list.

The determining unit 406 is further configured to determine whether the type of the second application is stored in the application list.

The adding and subtracting unit 403 is further configured to: when the type of the second application is not stored in the application list, add the type of the second application to the application list to obtain a new application list.

Optionally, the receiving unit 405 is further configured to receive, by the user, a third instruction that indicates that the application of the same type as the second application is not an application that is not installable.

The obtaining unit 401 is further configured to acquire the application list.

The determining unit 406 is further configured to determine whether the identifier of the second application is stored in the application list.

The adding and subtracting unit 403 is further configured to: when the application list stores the identifier of the second application, delete the identifier of the second application from the application list, to obtain a new application list.

Optionally, as shown in FIG. 7, the mobile terminal further includes:

The transmitting unit 407 is configured to download the stored application list from the cloud storage.

The merging unit 408, when the new application list and the stored application list are different, merge the new application list with the stored application list, and upload the merged application list to the Cloud storage.

In an actual application, the obtaining unit 401, the terminating unit 402, the adding and subtracting unit 403, the generating unit 404, the receiving unit 405, the determining unit 406, the transmitting unit 407, and the merging unit 408 may each be a central processor located in the mobile terminal 40. (Central Processing Unit, CPU), Microprocessor Unit (MPU), Digital Signal Processor (DSP), or Field Programmable Gate Array (FPGA).

This embodiment not only automatically increases the application list, but also actively increases the application in the application list by the user. The screen of the smart terminal displays the setting interface corresponding to the application list, and the user adds the name or type of the application on the setting interface, deletes the name or type of the application, and the smart phone uses The user's instructions modify the application list and synchronize the modified application list to the cloud storage.

If the user changes to a new smart phone, the smart phone does not have to re-create the application list, and the new smart phone can obtain the application list from the cloud storage, thereby improving the user experience.

Those skilled in the art will appreciate that embodiments of the present invention can be provided as a method, system, or computer program product. Accordingly, the present invention can take the form of a hardware embodiment, a software embodiment, or a combination of software and hardware. Moreover, the invention can take the form of a computer program product embodied on one or more computer-usable storage media (including but not limited to disk storage and optical storage, etc.) including computer usable program code.

The present invention has been described with reference to flowchart illustrations and/or block diagrams of methods, apparatus (system), and computer program products according to embodiments of the invention. It will be understood that each flow and/or block of the flowchart illustrations and/or FIG. These computer program instructions can be provided to a processor of a general purpose computer, special purpose computer, embedded processor, or other programmable data processing device to produce a machine for the execution of instructions for execution by a processor of a computer or other programmable data processing device. Means for implementing the functions specified in one or more of the flow or in a block or blocks of the flow chart.

The computer program instructions can also be stored in a computer readable memory that can direct a computer or other programmable data processing device to operate in a particular manner, such that the instructions stored in the computer readable memory produce an article of manufacture comprising the instruction device. The apparatus implements the functions specified in one or more blocks of a flow or a flow and/or block diagram of the flowchart.

These computer program instructions can also be loaded onto a computer or other programmable data processing device such that a series of operational steps are performed on a computer or other programmable device to produce computer-implemented processing for execution on a computer or other programmable device. The instructions provide steps for implementing the functions specified in one or more of the flow or in a block or blocks of a flow diagram.

The above-mentioned internal use is only an alternative embodiment of the embodiments of the present invention, and is not intended to limit the scope of protection of the embodiments of the present invention.

Industrial applicability

Claims

An application processing method includes:

When it is detected that the installation package of the first application is downloaded and ready to be installed, obtaining the identifier and type of the first application from the installation package;

Obtaining an application list, where the application list stores an identifier and/or a type of the application that is not installable;

When the identifier or type of the first application is stored in the application list, the installation of the first application is terminated.
The method according to claim 1, further comprising: adding or deleting an identifier and a type of one or more applications in the application list according to an indication of the user before obtaining the application list, to obtain a new one. Application List.
The method of claim 1 further comprising:

Obtaining an identifier of the second application when the second application needs to be uninstalled before acquiring the application list;

Generating and displaying first query information according to the identifier of the second application, where the first query information is used to determine to the user whether the second application is an uninstallable application;

Receiving an instruction sent by the user that the second application is an uninstallable application;

Obtaining the list of applications;

Determining whether the identifier of the second application is stored in the application list;

When the identifier of the second application is not stored in the application list, the identifier of the second application is added to the application list to obtain a new application list.
The method of claim 1 further comprising:

Obtaining the identifier and type of the second application when the second application needs to be uninstalled before acquiring the application list;

Generating and displaying first query information according to the identifier of the second application, where the first query information is used to determine to the user whether the second application is an uninstallable application;

Receiving, by the user, a first instruction that indicates that the second application is an uninstallable application;

And generating, according to the type of the second application, second query information, where the second query information is used to determine, to the user, whether an application of the same type as the second application is an uninstallable application;

Receiving, by the user, an application whose indication is the same as the type of the second application is a second instruction of an application that is not installable;

Obtaining the list of applications;

Determining whether the type of the second application is stored in the application list;

When the type of the second application is not stored in the application list, adding the type of the second application to the application list to obtain a new application list.
The method of claim 4, further comprising:

Receiving, by the user, an instruction indicating that the application of the same type as the second application is not a non-installable application;

Obtaining the list of applications;

Determining whether the identifier of the second application is stored in the application list;

When the identifier of the second application is stored in the application list, the identifier of the second application is deleted from the application list to obtain a new application list.
The method according to any one of claims 2 to 5, further comprising: downloading the stored application list from the cloud storage after obtaining the new application list;

When the new application list is different from the stored application list, the new application list is merged with the stored application list, and the merged application list is uploaded to the cloud storage.
A mobile terminal includes:

An obtaining unit, configured to: when detecting that the installation package of the first application is downloaded and ready to be installed, obtain the identifier and type of the first application from the installation package;

An obtaining unit, configured to obtain the application list, where the application list is not installable Identification and/or type of application;

And a termination unit, configured to terminate installation of the first application when the identifier or type of the first application is stored in the application list.
The mobile terminal of claim 7, wherein the mobile terminal further comprises:

The adding and subtracting unit is configured to add or delete an identifier and a type of the one or more applications in the application list according to an instruction of the user before obtaining the application list, to obtain a new application list.
The mobile terminal according to claim 7,

The obtaining unit is further configured to acquire an identifier of the second application when the second application needs to be uninstalled before acquiring the application list;

The mobile terminal further includes:

a generating unit, configured to generate and display first query information according to the identifier of the second application, where the first query information is used to determine, by the user, whether the second application is an uninstallable application;

a receiving unit, configured to receive an instruction sent by the user that indicates that the second application is an uninstallable application;

The obtaining unit is further configured to acquire the application list;

a determining unit, configured to determine whether the identifier of the second application is stored in the application list;

The adding and subtracting unit is further configured to: when the identifier of the second application is not stored in the application list, add the identifier of the second application to the application list to obtain a new application list.
The mobile terminal according to claim 7,

The obtaining unit is further configured to acquire the identifier and type of the second application when the second application needs to be uninstalled before acquiring the application list;

The generating unit is further configured to generate and display first query information according to the identifier of the second application, where the first query information is used to determine, by the user, whether the second application is an uninstallable application;

The receiving unit is further configured to receive, by the user, an indication that the second application is not available The first instruction of the installed application;

The generating unit is further configured to generate and display second query information according to the type of the second application, where the second query information is used to determine, to the user, whether an application of the same type as the second application is Is an application that cannot be installed;

The receiving unit is further configured to receive, by the user, a second instruction that indicates that the application of the same type as the second application is an application that is not installable;

The obtaining unit is further configured to acquire the application list;

The determining unit is further configured to determine whether the type of the second application is stored in the application list;

The adding and subtracting unit is further configured to: when the type of the second application is not stored in the application list, add the type of the second application to the application list to obtain a new application list.
The mobile terminal of claim 10,

The receiving unit is further configured to receive, by the user, a third instruction that indicates that the application of the same type as the second application is not an uninstallable application;

The obtaining unit is further configured to acquire the application list;

The determining unit is further configured to determine whether the identifier of the second application is stored in the application list;

The adding and subtracting unit is further configured to: when the identifier of the second application is stored in the application list, delete the identifier of the second application from the application list to obtain a new application list.
The mobile terminal according to any one of claims 8 to 11, wherein the mobile terminal further comprises:

a transmission unit configured to download a list of stored applications from the cloud storage;

And a merging unit, configured to merge the new application list with the stored application list, and upload the merged application list, when the new application list is different from the stored application list.
A computer readable storage medium storing computer executable instructions that, when executed by a processor, implement the application processing method of any one of claims 1 to 6.