CN117032737A - Application uninstalling method, device, electronic equipment and readable storage medium - Google Patents

Abstract

This application discloses an application uninstallation method, device, electronic device and readable storage medium, which belongs to the field of data processing technology. The method includes: receiving a first input for switching from a first sub-application to another sub-application; and in response to the first input, saving a first sub-application in a base application of the first sub-application. A cache file, the first cache file includes the application instance of the first sub-application and the virtual DOM structure data of the first sub-application; uninstall the first sub-application.

Description

Application uninstallation method, device, electronic device and readable storage medium

Technical field

This application belongs to the field of data processing technology, and specifically relates to an application uninstallation method, device, electronic device and readable storage medium.

Background technique

The current micro front-end solution in the industry divides applications into base applications and sub-applications. For example, a complete application downloaded in an electronic device is a base application, and an application that appears as a small program in other applications is a sub-application. Sub-applications can help users quickly access designated pages of the base application.

In the browser, when sub-application A of the dock application is displayed, if you want to switch to sub-application B of the dock application, you need to uninstall the currently displayed sub-application A and load the initialization data of sub-application B. Usually, when users access multiple sub-applications, they need to constantly uninstall one sub-application and load the initialization data of another sub-application. As a result, loading the initialization data takes a long time, resulting in an increase in the access time and giving the user a kind of page switching stuck. A sense of pause and slowness.

It can be seen that the existing technology has the phenomenon of switching lag when switching between multiple sub-applications.

Contents of the invention

The purpose of the embodiments of the present application is to provide an application uninstallation method that can solve the problem of switching lag in the existing technology when switching between multiple sub-applications.

In a first aspect, embodiments of the present application provide an application uninstallation method, which method includes: receiving a first input, the first input being used to switch from a first sub-application to another sub-application; responding to the first input , save the first cache file in the base application of the first sub-application, the first cache file includes the application instance of the first sub-application and the virtual DOM structure data of the first sub-application; uninstall all Describe the first sub-application.

In a second aspect, embodiments of the present application provide an application uninstallation device, which includes: a first receiving module configured to receive a first input, the first input being used to switch from a first sub-application to another sub-application; A first saving module, configured to save a first cache file in the base application of the first sub-application in response to the first input, where the first cache file includes an application instance of the first sub-application and The virtual DOM structure data of the first sub-application; an uninstall module used to uninstall the first sub-application.

In a third aspect, embodiments of the present application provide an electronic device. The electronic device includes a processor and a memory. The memory stores programs or instructions that can be run on the processor. The programs or instructions are processed by the processor. When the processor is executed, the steps of the method described in the first aspect are implemented.

In a fourth aspect, embodiments of the present application provide a readable storage medium. Programs or instructions are stored on the readable storage medium. When the programs or instructions are executed by a processor, the steps of the method described in the first aspect are implemented. .

In a fifth aspect, embodiments of the present application provide a chip. The chip includes a processor and a communication interface. The communication interface is coupled to the processor. The processor is used to run programs or instructions to implement the first aspect. the method described.

In a sixth aspect, embodiments of the present application provide a computer program product, the program product is stored in a storage medium, and the program product is executed by at least one processor to implement the method as described in the first aspect.

In this way, in the embodiment of the present application, when the user triggers switching from the currently displayed first sub-application to other sub-applications through the first input, the first sub-application will not be uninstalled directly in response to the first input, but will be The first cache file is saved in the base application of the first sub-application. The first cache file includes the application instance of the first sub-application and the virtual DOM structure data of the first sub-application. After saving, the first sub-application is uninstalled. Therefore, when switching to the first sub-application next time, the first cache file can be directly used without loading the initialization data of the first sub-application. It can be seen that based on the uninstallation method provided by the embodiment of the present application, when switching between multiple sub-applications, the step of loading initialization data is saved, and the time for loading page data is shortened, so that no lag occurs when switching applications. Phenomenon.

Description of the drawings

Figure 1 is a flow chart of an application uninstallation method according to an embodiment of the present application;

Figure 2 is one of the schematic diagrams illustrating the application uninstallation method according to the embodiment of the present application;

Figure 3 is the second schematic diagram illustrating the application uninstallation method according to the embodiment of the present application;

Figure 4 is the third schematic diagram illustrating the application uninstallation method according to the embodiment of the present application;

Figure 5 is a block diagram of an application uninstaller according to an embodiment of the present application;

Figure 6 is one of the schematic diagrams of the hardware structure of the electronic device according to the embodiment of the present application;

FIG. 7 is a second schematic diagram of the hardware structure of the electronic device according to the embodiment of the present application.

Detailed ways

The technical solutions of the embodiments of the present application will be clearly described below with reference to the accompanying drawings of the embodiments of the present application. Obviously, the described embodiments are part of the embodiments of the present application, but not all of the embodiments. Based on the embodiments of this application, all other embodiments obtained by those of ordinary skill in the art fall within the scope of protection of this application.

The terms "first", "second", etc. in the description and claims of this application are used to distinguish similar objects and are not used to describe a specific order or sequence. It is to be understood that the figures so used are interchangeable under appropriate circumstances so that the embodiments of the present application can be practiced in orders other than those illustrated or described herein, and that "first," "second," etc. are distinguished Objects are usually of one type, and the number of objects is not limited. For example, the first object can be one or multiple. In addition, "and/or" in the description and claims indicates at least one of the connected objects, and the character "/" generally indicates that the related objects are in an "or" relationship.

The execution subject of the application uninstallation method provided by the embodiments of the present application may be the application uninstallation device provided by the embodiments of the present application, or an electronic device integrated with the application uninstallation device, where the application uninstallation device may be implemented in hardware or software.

The application uninstallation method provided by the embodiments of the present application will be described in detail below with reference to the accompanying drawings through specific embodiments and application scenarios.

Figure 1 shows a flow chart of an application uninstallation method according to an embodiment of the present application, applied to electronic devices, the method includes:

Step 110: Receive a first input, the first input is used to switch from the first sub-application to other sub-applications. The first input includes the user's touch input on the screen, which is not limited to click, slide, drag and other inputs. The first input may also be the user's air-to-air input, such as gestures, facial movements, etc. The first input also includes the user's input of physical buttons on the device, and is not limited to inputs such as pressing. Moreover, the first input includes one or more inputs, wherein the multiple inputs may be continuous or have time intervals.

In this step, the first input is used by the user to trigger switching from the currently displayed first sub-application to other sub-applications.

In this embodiment, referring to Figure 2, based on a certain base application 201, multiple sub-applications 202 can be split, and each sub-application displays the content of the page being navigated to the user. Among them, the base application 201 provides the registration interface, sub-application loading entrance, sub-application environment isolation and other capabilities of the sub-application 202 to ensure that the sub-application can be easily switched and run.

Among them, the first sub-application is a sub-application of the base application, and the other sub-applications are another sub-application of the base application.

For example, see Figure 3. Base application A is a shopping application, including a site-wide navigation menu. Base application A can be divided into navigation B and navigation C. Navigation B corresponds to sub-application B. The page navigated by sub-application B is a product list. Page, navigation C corresponds to sub-application C, and the page navigated by sub-application C is the shopping cart checkout page. Correspondingly, the first input is used for the user to trigger switching from sub-application B 301 to sub-application C 302 .

The application scenario of this embodiment is, for example, when the browser displays the content of the page navigated by the first sub-application, the user clicks the link corresponding to the other sub-application to trigger the display of the content of the page navigated by the other sub-application.

Step 120: In response to the first input, save a first cache file in the base application of the first sub-application, where the first cache file includes an application instance of the first sub-application and virtual DOM structure data of the first sub-application.

In this step, before uninstalling the first sub-application, the first cache file is saved in the base application of the first sub-application based on the page content of the currently displayed first sub-page.

The first cache file includes an application instance of the first sub-application and virtual Document Object Model (DOM) structural data of the first sub-application.

For example, the first sub-application is sub-application B, and the saved first cache file includes: AppB and node (Node) B, where AppB is used to represent the application instance of sub-application B, and NodeB is used to represent the node of the virtual DOM structure data. .

Optionally, save the first cache file to a designated storage location of the base application to facilitate subsequent reading.

Step 130: Uninstall the first sub-application.

In this step, after saving the first cache file of the first sub-application, the first sub-application is uninstalled.

Further, switch to other sub-applications.

For example, see Figure 3. After switching from sub-application B to sub-application C, "B: AppB, NodeB" is saved in base application A.

In this embodiment, when switching applications, monitoring is performed in the base application. If it is detected that the two applications switched this time are two sub-applications of the base application, the cache files of the sub-applications before switching will be cached. of preservation.

In this way, in the embodiment of the present application, when the user triggers switching from the currently displayed first sub-application to other sub-applications through the first input, the first sub-application will not be uninstalled directly in response to the first input, but will be The first cache file is saved in the base application of the first sub-application. The first cache file includes the application instance of the first sub-application and the virtual DOM structure data of the first sub-application. After saving, the first sub-application is uninstalled. Therefore, when switching to the first sub-application next time, the first cache file can be directly used without loading the initialization data of the first sub-application. It can be seen that based on the uninstallation method provided by the embodiment of the present application, when switching between multiple sub-applications, the step of loading initialization data is saved, and the time for loading page data is shortened, so that no lag occurs when switching applications. Phenomenon.

In the process of the application uninstallation method according to another embodiment of the present application, step 130 includes:

Sub-step A1: Delete the page node of the first sub-application.

Sub-step A2: Set the first attribute information of the first cache file.

In this step, when the first sub-application is uninstalled, only the page node of the first sub-application is deleted, and the first attribute information of the first cache file is set to "keepalive".

In this embodiment, when the first sub-application is uninstalled, the first cache file saved in the base application is not deleted, and the attribute of the first cache file is set to "keepalive" to ensure that the cache file is switched to the first sub-application next time. Available in a sub-application scenario.

In the process of the application download method in another embodiment of the present application, step 120 includes:

Sub-step B1: Save the first cache file as a variable.

In this step, the first cache file is saved in the base application and maintained as the variable "appMap".

Among them, "appMap" is the variable name in the base application, which can be understood as a memory space to store cache content.

Optionally, persist the variable "appMap" to the front-end storage "localstorage". The next time the user triggers the display of the first sub-application, the page content can be restored through the persistent data to speed up rendering.

In this embodiment, the storage location of the first cache file is limited to ensure that it can be used in switching scenarios of sub-applications. In addition, the first cache file is saved as a variable and can be deleted based on the actual size of the remaining storage space to ensure the performance of the electronic device.

In the process of the application download method in another embodiment of the present application, after step 130, the method further includes:

Step C1: Receive a second input, the second input is used to switch from the second sub-application to the first sub-application.

The second input includes the user's touch input on the screen, which is not limited to click, slide, drag and other inputs. The second input can also be the user's input through the air, such as gestures, facial movements, etc. The second input also includes the user's input to physical buttons on the device, and is not limited to input such as pressing. Moreover, the second input includes one or more inputs, wherein the multiple inputs may be continuous or have time intervals.

In this step, the second input is used by the user to trigger switching from the currently displayed second sub-application to the first sub-application.

Among them, the first sub-application and the second sub-application are two sub-applications of the base application respectively.

For example, referring to Figure 4, the second sub-application is sub-application C, the first sub-application is sub-application B, and the second input is used for the user to trigger switching from sub-application C 401 to sub-application B 402.

Step C2: In response to the second input, obtain the first cache file in the base application according to the name information of the first sub-application.

In this step, the corresponding first cache file can be queried in the base application according to the name information of the first sub-application.

For example, the first sub-application is sub-application B, and the base application stores: "B: AppB, NodeB", where "B" in front of ":" is used to represent the name information of sub-application B.

Step C3: When the second sub-application has been uninstalled, display the first sub-application according to the first cache file.

In this step, after the currently displayed second sub-application is uninstalled, the page content of the first sub-application is restored according to the application instance of the first sub-application and the virtual DOM structure data of the first sub-application to complete the modification of the first sub-application. Switch display of the application.

Referring to Figure 4, combined with Figure 3 and the application uninstallation method of the present application, when switching from sub-application C 401 to sub-application B 402, base application A stores: "B: AppB, NodeB" and "C: AppC, NodeC”.

In this embodiment, a method of restoring page content based on saved cache files is provided. It can be used in switching scenarios between sub-applications without reloading the initial data, which improves the page rendering speed and avoids switching for users. Stuttering experience.

In the process of the application download method according to another embodiment of the present application, the method further includes:

Step D1: When the third sub-application of the base application is displayed, obtain the application instance of the fourth sub-application of the base application and the virtual DOM structure data of the fourth sub-application.

In this step, the third sub-application and the fourth sub-application are any two sub-applications of the base application.

The application scenario of this embodiment is, for example, when loading a sub-application of the base application for the first time, if the third sub-application is loaded, other sub-applications can be automatically loaded in the background. For example, the other sub-application is the fourth sub-application, and based on the loading Data, automatically obtain the application instance of the fourth sub-application and the virtual DOM structure data of the fourth sub-application in the background.

Step D2: Save the second cache file in the base application. The second cache file includes the application instance of the fourth sub-application and the virtual DOM structure data of the fourth sub-application.

In this step, the second cache file of the dock application is automatically saved in the background. The second cache file is the cache file corresponding to the fourth sub-application and is used to restore the page content of the fourth sub-application.

Among them, referring to the method of this embodiment, cache files corresponding to all sub-applications can be saved in the base application.

Therefore, when the user switches to the fourth sub-application, the second cache file is directly used to restore the page content of the fourth sub-page, thereby reducing the steps of initializing the instance and speeding up rendering.

In the embodiment, cache files corresponding to each sub-application are saved in the base application in advance, so that the cache file can be used when switching to a certain sub-application for the first time, thereby reducing data loading time and improving user experience.

In other embodiments of this application, for micro frontend applications without virtual DOM, the method of saving cache data in this application can be used to save other forms of cache data of page content, so as to reduce the time of loading page data when switching next time. time.

In other embodiments of this application, if the cache file corresponding to the sub-application is not saved in the base application, the resources of the sub-application are directly loaded, the application is instantiated such as "AppC", the script is executed to build the virtual DOM, and the page is rendered. .

In summary, based on the current front-end development trend, more and more functions are designed on the World Wide Web (WEB) side, applications are becoming more and more complex, and traditional single page applications (Single Page Application, SPA) have also become is getting bigger and bigger, prompting the use of micro-front-end solutions to solve the growing number of front-end applications, such as splitting a larger SPA into multiple smaller applications, that is, splitting a base application into sub-applications to solve monolithic applications The problem. Based on this, this application proposes an application uninstallation method. With the help of the virtual DOM structure of the front-end framework, the cache file is saved when the application is uninstalled, so that based on the saved cache file, the sub-application can be loaded once and used multiple times, where It can also save user operation information.

Table 1

Referring to Table 1, the optimized micro front-end application switching method of this application, compared with the conventional micro front-end application switching method, saves the steps of loading current application resources, executing current application initialization code, building application instances, and building virtual DOM, and The page is rendered directly based on the virtual DOM structure data in the cache file, which shortens the time spent on displaying the page, thereby solving the problem of lagging during switching and giving users the ultimate performance experience.

For the application uninstallation method provided by the embodiments of the present application, the execution subject may be an application uninstallation device. In the embodiment of this application, the application uninstallation method performed by the application uninstallation device is used as an example to illustrate the application uninstallation device provided by the embodiment of this application.

Figure 5 shows a block diagram of an application uninstallation device according to an embodiment of the present application. The device includes:

The first receiving module 10 is used to receive a first input, and the first input is used to switch from the first sub-application to other sub-applications;

The first saving module 20 is configured to save a first cache file in the base application of the first sub-application in response to the first input, where the first cache file includes an application instance of the first sub-application and a virtual DOM of the first sub-application. structured data;

The uninstall module 30 is used to uninstall the first sub-application.

In this way, in the embodiment of the present application, when the user triggers switching from the currently displayed first sub-application to other sub-applications through the first input, the first sub-application will not be uninstalled directly in response to the first input, but will be The first cache file is saved in the base application of the first sub-application. The first cache file includes the application instance of the first sub-application and the virtual DOM structure data of the first sub-application. After saving, the first sub-application is uninstalled. Therefore, when switching to the first sub-application next time, the first cache file can be directly used without loading the initialization data of the first sub-application. It can be seen that based on the uninstallation method provided by the embodiment of the present application, when switching between multiple sub-applications, the step of loading initialization data is saved, and the time for loading page data is shortened, so that no lag occurs when switching applications. Phenomenon.

Optionally, uninstall module 30, including:

Delete unit, used to delete the page node of the first sub-application;

The setting unit is used to set the first attribute information of the first cache file.

Optionally, the first saving module 20 includes:

The saving unit is used to save the first cache file as a variable.

Optionally, the device also includes:

a second receiving module, configured to receive a second input, and the second input is used to switch from the second sub-application to the first sub-application;

A first acquisition module, configured to acquire the first cache file in the base application according to the name information of the first sub-application in response to the second input;

A display module configured to display the first sub-application according to the first cache file when the second sub-application has been uninstalled.

Optionally, the device also includes:

The second acquisition module is used to acquire the application instance of the fourth sub-application of the base application and the virtual DOM structure data of the fourth sub-application when the third sub-application of the base application is displayed;

The second saving module is configured to save a second cache file in the base application. The second cache file includes the application instance of the fourth sub-application and the virtual DOM structure data of the fourth sub-application.

The application uninstallation device in the embodiment of the present application may be an electronic device or a component in the electronic device, such as an integrated circuit or a chip. The electronic device may be a terminal or other devices other than the terminal. For example, the electronic device may be a mobile phone, a tablet computer, a notebook computer, a handheld computer, a vehicle-mounted electronic device, a mobile Internet device (MID), or augmented reality (AR)/virtual reality (VR) Devices, robots, wearable devices, ultra-mobile personal computers (UMPC), netbooks or personal digital assistants (PDA), etc., can also be servers, network attached storage (Network Attached Storage, NAS) , personal computer (PC), television (TV), teller machine or self-service machine, etc., the embodiments of this application are not specifically limited.

The application uninstallation device in the embodiment of the present application may be a device with an action system. The action system can be an Android action system, an ios action system, or other possible action systems, which are not specifically limited in the embodiments of this application.

The application uninstallation device provided by the embodiments of the present application can implement each process implemented by the above method embodiments. To avoid duplication, the details will not be described here.

Optionally, as shown in Figure 6, this embodiment of the present application also provides an electronic device 100, including a processor 101, a memory 102, and a program or instructions stored on the memory 102 and executable on the processor 101. The program Or when the instruction is executed by the processor 101, each step of any of the above application uninstallation method embodiments is implemented, and the same technical effect can be achieved. To avoid duplication, the details will not be described here.

It should be noted that the electronic devices in the embodiments of the present application include the above-mentioned mobile electronic devices and non-mobile electronic devices.

FIG. 7 is a schematic diagram of the hardware structure of an electronic device that implements an embodiment of the present application.

The electronic device 1000 includes but is not limited to: radio frequency unit 1001, network module 1002, audio output unit 1003, input unit 1004, sensor 1005, display unit 1006, user input unit 1007, interface unit 1008, memory 1009, processor 1010, camera 1011 and other parts.

Those skilled in the art can understand that the electronic device 1000 may also include a power supply (such as a battery) that supplies power to various components. The power supply may be logically connected to the processor 1010 through a power management system, thereby managing charging, discharging, and function through the power management system. Consumption management and other functions. The structure of the electronic device shown in Figure 7 does not constitute a limitation on the electronic device. The electronic device may include more or less components than shown in the figure, or combine certain components, or arrange different components, which will not be described again here. .

Among them, the user input unit 1007 is used to receive a first input, and the first input is used to switch from the first sub-application to other sub-applications; the processor 1010 is used to respond to the first input, in the first sub-application. Saving a first cache file in a base application of a sub-application, the first cache file including an application instance of the first sub-application and virtual DOM structure data of the first sub-application; uninstalling the first sub-application .

In this way, in the embodiment of the present application, when the user triggers switching from the currently displayed first sub-application to other sub-applications through the first input, the first sub-application will not be uninstalled directly in response to the first input, but will be The first cache file is saved in the base application of the first sub-application. The first cache file includes the application instance of the first sub-application and the virtual DOM structure data of the first sub-application. After saving, the first sub-application is uninstalled. Therefore, when switching to the first sub-application next time, the first cache file can be directly used without loading the initialization data of the first sub-application. It can be seen that based on the uninstallation method provided by the embodiment of the present application, when switching between multiple sub-applications, the step of loading initialization data is saved, and the time for loading page data is shortened, so that no lag occurs when switching applications. Phenomenon.

Optionally, the processor 1010 is also configured to delete the page node of the first sub-application; and set the first attribute information of the first cache file.

Optionally, the processor 1010 is also configured to save the first cache file as a variable.

Optionally, the user input unit 1007 is also configured to receive a second input for switching from the second sub-application to the first sub-application; the processor 1010 is also configured to respond to the first sub-application. The second input is to obtain the first cache file in the base application according to the name information of the first sub-application; the display unit 1006 is used to display the first cache file according to the second sub-application when the second sub-application has been uninstalled. The first cache file displays the first sub-application.

Optionally, the processor 1010 is further configured to obtain an application instance of a fourth sub-application of the base application and a virtual instance of the fourth sub-application when the third sub-application of the base application is displayed. DOM structure data; save a second cache file in the base application, where the second cache file includes an application instance of the fourth sub-application and virtual DOM structure data of the fourth sub-application.

In summary, based on the current front-end development trend, more and more functions are designed on the World Wide Web (WEB) side, applications are becoming more and more complex, and traditional single page applications (Single Page Application, SPA) have also become is getting bigger and bigger, prompting the use of micro-front-end solutions to solve the growing number of front-end applications, such as splitting a larger SPA into multiple smaller applications, that is, splitting a base application into sub-applications to solve monolithic applications The problem. Based on this, this application proposes an application uninstallation method. With the help of the virtual DOM structure of the front-end framework, the cache file is saved when the application is uninstalled, so that based on the saved cache file, the sub-application can be loaded once and used multiple times, where It can also save user operation information. Compared with the conventional micro front-end application switching method, the optimized micro front-end application switching method of this application saves the steps of loading current application resources, executing current application initialization code, building application instances, and building virtual DOM, and is directly based on caching. The virtual DOM structure data in the file is used to render the page, which shortens the time it takes to display the page, thereby solving the problem of lagging during switching and giving users the ultimate performance experience.

It should be understood that in the embodiment of the present application, the input unit 1004 may include a graphics processor (Graphics Processing Unit, GPU) 10041 and a microphone 10042, and the graphics processor 10041 is responsible for the image capture device (GPU) in the video image capture mode or the image capture mode. Process the image data of still pictures or video images obtained by a camera (such as a camera). The display unit 1006 may include a display panel 10061, which may be configured in the form of a liquid crystal display, an organic light emitting diode, or the like. The user input unit 1007 includes at least one of a touch panel 10071 and other input devices 10072 . Touch panel 10071, also known as touch screen. The touch panel 10071 may include two parts: a touch detection device and a touch controller. Other input devices 10072 may include but are not limited to physical keyboards, function keys (such as volume control keys, switch keys, etc.), trackballs, mice, and action sticks, which will not be described again here. Memory 1009 may be used to store software programs as well as various data, including but not limited to application programs and action systems. The processor 1010 can integrate an application processor and a modem processor. The application processor mainly processes action systems, user pages, application programs, etc., and the modem processor mainly processes wireless communications. It can be understood that the above modem processor may not be integrated into the processor 1010.

Memory 1009 may be used to store software programs as well as various data. The memory 1009 may mainly include a first storage area for storing programs or instructions and a second storage area for storing data, wherein the first storage area may store an operating system, an application program or instructions required for at least one function (such as a sound playback function, Image playback function, etc.) etc. Additionally, memory 1009 may include volatile memory or nonvolatile memory, or memory 1009 may include both volatile and nonvolatile memory. Among them, the non-volatile memory can be read-only memory (Read-Only Memory, ROM), programmable read-only memory (Programmable ROM, PROM), erasable programmable read-only memory (Erasable PROM, EPROM), electrically removable memory. Erase programmable read-only memory (Electrically EPROM, EEPROM) or flash memory. Volatile memory can be random access memory (Random Access Memory, RAM), static random access memory (Static RAM, SRAM), dynamic random access memory (Dynamic RAM, DRAM), synchronous dynamic random access memory (Synchronous DRAM, SDRAM), double data rate synchronous dynamic random access memory (Double Data Rate SDRAM, DDRSDRAM), enhanced synchronous dynamic random access memory (Enhanced SDRAM, ESDRAM), synchronous link dynamic random access memory (Synch link DRAM) , SLDRAM) and direct memory bus random access memory (Direct Rambus RAM, DRRAM). The memory 1009 in the embodiment of the present application includes, but is not limited to, these and any other suitable types of memory.

The processor 1010 may include one or more processing units; optionally, the processor 1010 integrates an application processor and a modem processor, where the application processor mainly handles operations related to the operating system, user interface, application programs, etc., Modem processors mainly process wireless communication signals, such as baseband processors. It can be understood that the above modem processor may not be integrated into the processor 1010.

Embodiments of the present application also provide a readable storage medium. Programs or instructions are stored on the readable storage medium. When the program or instructions are executed by the processor, each process of the above application uninstallation method embodiment is implemented, and the same technology can be achieved. The effect will not be described here to avoid repetition.

Wherein, the processor is the processor in the electronic device in the above embodiment. Readable storage media includes computer-readable storage media, such as computer read-only memory ROM, random access memory RAM, magnetic disks or optical disks.

The embodiment of the present application also provides a chip. The chip includes a processor and a communication interface. The communication interface is coupled to the processor. The processor is used to run programs or instructions to implement each process of the above application offloading method embodiment, and can achieve the same To avoid repetition, the technical effects will not be repeated here.

It should be understood that the chips mentioned in the embodiments of this application may also be called system-on-chip, system-on-a-chip, system-on-a-chip or system-on-chip, etc.

Embodiments of the present application provide a computer program product. The program product is stored in a storage medium. The program product is executed by at least one processor to implement each process of the above application uninstallation method embodiment, and can achieve the same technical effect. , to avoid repetition, will not be repeated here.

It should be noted that, in this document, the terms "comprising", "comprises" or any other variations thereof are intended to cover a non-exclusive inclusion, such that a process, method, article or device that includes a series of elements not only includes those elements, It also includes other elements not expressly listed or inherent in the process, method, article or apparatus. Without further limitation, an element defined by the statement "comprises a..." does not exclude the presence of additional identical elements in a process, method, article or apparatus that includes that element. In addition, it should be pointed out that the scope of the methods and devices in the embodiments of the present application is not limited to performing functions in the order shown or discussed, but may also include performing functions in a substantially simultaneous manner or in reverse order according to the functions involved. Functions may be performed, for example, the methods described may be performed in an order different from that described, and various steps may be added, omitted, or combined. Additionally, features described with reference to certain examples may be combined in other examples.

Through the above description of the embodiments, those skilled in the art can clearly understand that the methods of the above embodiments can be implemented by means of software plus the necessary general hardware platform. Of course, it can also be implemented by hardware, but in many cases the former is better. implementation. Based on this understanding, the technical solution of the present application can be embodied in the form of a computer software product that is essentially or contributes to the existing technology. The computer software product is stored in a storage medium (such as ROM/RAM, disk , CD), including several instructions to cause a terminal (which can be a mobile phone, computer, server, or network device, etc.) to execute the methods of various embodiments of the present application.

The embodiments of the present application have been described above in conjunction with the accompanying drawings. However, the present application is not limited to the above-mentioned specific implementations. The above-mentioned specific implementations are only illustrative and not restrictive. Those of ordinary skill in the art will Inspired by this application, many forms can be made without departing from the purpose of this application and the scope protected by the claims, all of which fall within the protection of this application.

Claims (12)

1. An application uninstallation method, characterized in that the method includes: Receive a first input, the first input being used for switching from the first sub-application to other sub-applications; In response to the first input, a first cache file is saved in the base application of the first sub-application, the first cache file includes an application instance of the first sub-application and an application instance of the first sub-application. Virtual DOM structure data; Uninstall the first sub-application. 2. The method of claim 1, wherein uninstalling the first sub-application includes: Delete the page node of the first sub-application; Set first attribute information of the first cache file. 3. The method of claim 1, wherein saving the first cache file in the base application of the first sub-application includes: Save the first cache file as a variable. 4. The method of claim 1, wherein after uninstalling the first sub-application, the method further includes: Receive a second input, the second input being used to switch from the second sub-application to the first sub-application; In response to the second input, obtain the first cache file in the base application according to the name information of the first sub-application; When the second sub-application has been uninstalled, the first sub-application is displayed according to the first cache file. 5. The method according to claim 1, characterized in that, the method further comprises: When the third sub-application of the base application is displayed, obtain the application instance of the fourth sub-application of the base application and the virtual DOM structure data of the fourth sub-application; A second cache file is saved in the base application, and the second cache file includes an application instance of the fourth sub-application and virtual DOM structure data of the fourth sub-application. 6. An application uninstallation device, characterized in that the device includes: A first receiving module, configured to receive a first input, the first input being used to switch from the first sub-application to other sub-applications; A first saving module, configured to save a first cache file in the base application of the first sub-application in response to the first input, where the first cache file includes an application instance of the first sub-application and The virtual DOM structure data of the first sub-application; An uninstall module is used to uninstall the first sub-application. 7. The device according to claim 6, characterized in that the unloading module includes: A deletion unit, used to delete the page node of the first sub-application; A setting unit configured to set first attribute information of the first cache file. 8. The device according to claim 6, characterized in that the first saving module includes: A saving unit, configured to save the first cache file as a variable. 9. The device according to claim 6, characterized in that the device further comprises: a second receiving module, configured to receive a second input, the second input being used to switch from the second sub-application to the first sub-application; A first acquisition module configured to acquire the first cache file in the base application according to the name information of the first sub-application in response to the second input; A display module configured to display the first sub-application according to the first cache file when the second sub-application has been uninstalled. 10. The device of claim 6, further comprising: A second acquisition module, configured to acquire an application instance of a fourth sub-application of the base application and virtual DOM structure data of the fourth sub-application when the third sub-application of the base application is displayed; A second saving module is configured to save a second cache file in the base application, where the second cache file includes an application instance of the fourth sub-application and virtual DOM structure data of the fourth sub-application. 11. An electronic device, characterized in that it includes a processor and a memory, the memory stores programs or instructions that can be run on the processor, and when the programs or instructions are executed by the processor, the claims are implemented The steps of the application uninstallation method described in any one of 1 to 5. 12. A readable storage medium, characterized in that the readable storage medium stores programs or instructions, and when the programs or instructions are executed by a processor, the application uninstallation as described in any one of claims 1 to 5 is realized. Method steps.