Micro-application management and control method, system and device and computer readable storage medium

Abstract

The embodiment of the invention provides a micro-application management and control method, system and device and a computer readable storage medium. The method comprises the following steps: receiving a starting instruction for a target micro-application; wherein the target micro application is a micro application in the at least one micro application; obtaining a corresponding target micro-application configuration file according to the starting instruction; loading the target micro application according to the target micro application configuration file; and after the loading of the target micro-application is completed, displaying an interface of the target micro-application. In this way, a user can conveniently and flexibly use each micro-application on the micro-application management and control system integrated with a plurality of application function modules, so that the use flexibility of the micro-applications is improved, and the service efficiency can also be improved.

Description

Technical Field

[0001] This disclosure relates to the field of micro-applications, and more particularly to the field of micro-application management technology. Background Technology

[0002] Currently, many application functions are scattered. Enterprises obviously need many application functions to meet their business needs, but scattered application functions will cause inconvenience for users within the enterprise. Therefore, how to make it convenient for users to use many application functions and improve business efficiency has become an urgent problem to be solved. Summary of the Invention

[0003] This disclosure provides a micro-application management method, apparatus, device, and storage medium.

[0004] According to a first aspect of this disclosure, a micro-application management method is provided. The method includes:

[0005] Receive a launch command for a target micro-application; wherein the target micro-application is a micro-application among the at least one micro-application;

[0006] According to the startup command, obtain the corresponding target micro-application configuration file;

[0007] The target micro-application is loaded according to the target micro-application configuration file;

[0008] After the target micro-application is loaded, the interface of the target micro-application is displayed.

[0009] In addition to the aspects and any possible implementations described above, a further implementation is provided, wherein obtaining the corresponding target micro-application configuration file includes:

[0010] Determine whether the target micro-application configuration file is stored locally;

[0011] If the target micro-application configuration file is stored, then the target micro-application configuration file is obtained directly from the local machine;

[0012] If the target micro-application configuration file is not stored, a configuration file retrieval command is sent to the micro-application management center;

[0013] According to the configuration file retrieval instruction, the micro-application configuration file is retrieved from the micro-application management center, wherein the micro-application configuration file includes: the registration information of the target micro-application, as well as the functional description and dependency description of the target micro-application.

[0014] In addition to the aspects described above and any possible implementations, a further implementation is provided in which the method further includes, before loading the target micro-application:

[0015] Perform integrity verification on the micro-application configuration file;

[0016] Perform a technical compatibility check on the micro-application configuration file.

[0017] In addition to the aspects and any possible implementations described above, a further implementation is provided, wherein obtaining the corresponding target micro-application configuration file includes:

[0018] Obtain the application identifier and user identifier from the startup command;

[0019] The target micro-application to be launched is determined based on the application identifier;

[0020] Determine user permissions based on the user identifier;

[0021] Determine whether the user permissions include the permission to launch the target micro-application;

[0022] If the permission to launch the target micro-application is included, then the corresponding micro-application configuration file is obtained.

[0023] In addition to the aspects and any possible implementations described above, a further implementation is provided, wherein the method further includes:

[0024] Receive events published by the target micro-application;

[0025] Publish the event to all micro-applications that have subscribed to the event within the at least one micro-application; or

[0026] The event is shared to all micro-applications within the at least one micro-application.

[0027] In addition to the aspects and any possible implementations described above, a further implementation is provided, wherein the method further includes:

[0028] Receive a close command for the target micro-application;

[0029] Uninstall the target micro-application according to the shutdown command, and release the resources occupied by the target micro-application.

[0030] In addition to the aspects and any possible implementations described above, a further implementation is provided, wherein the method further includes:

[0031] Obtain information on the functional importance of each micro-application and user habits;

[0032] Based on the functional importance of each micro-application and user habits, the integration priority of each micro-application is determined;

[0033] According to the integration priority of each micro-application, select at least one micro-application from the micro-applications;

[0034] The at least one micro-application is integrated into the micro-application management system.

[0035] According to a second aspect of this disclosure, a micro-application management device is provided. The device includes:

[0036] A receiving module is configured to receive a launch command for a target micro-application; wherein the target micro-application is a micro-application among the at least one micro-application;

[0037] The acquisition module is used to acquire the corresponding target micro-application configuration file according to the startup command;

[0038] A loading module is used to load the target micro-application according to the target micro-application configuration file;

[0039] The display module is used to display the interface of the target micro-application after it has been loaded.

[0040] According to a third aspect of this disclosure, an electronic device is provided. The electronic device includes a memory and a processor, wherein the memory stores a computer program, and the processor executes the program to implement the method described above.

[0041] According to a fourth aspect of this disclosure, a computer-readable storage medium is provided having a computer program stored thereon that, when executed by a processor, implements the method according to a first aspect of this disclosure.

[0042] In this disclosure, after receiving a launch command for a target micro-application, the corresponding target micro-application configuration file can be obtained according to the launch command. Then, the target micro-application is loaded according to the target micro-application configuration file. After the target micro-application is loaded, its interface is displayed. This allows users to flexibly use each micro-application on a micro-application management system that integrates multiple application function modules, thereby improving the flexibility of micro-application usage and thus improving business efficiency.

[0043] It should be understood that the description in the Summary of the Invention section is not intended to limit the key or essential features of the embodiments of this disclosure, nor is it intended to restrict the scope of this disclosure. Other features of this disclosure will become readily apparent from the following description. Attached Figure Description

[0044] The above and other features, advantages, and aspects of the embodiments of this disclosure will become more apparent from the accompanying drawings and the following detailed description. The drawings are provided for a better understanding of the invention and are not intended to limit the scope of this disclosure. In the drawings, the same or similar reference numerals denote the same or similar elements, wherein:

[0045] Figure 1 A flowchart of a micro-application management method according to an embodiment of the present disclosure is shown;

[0046] Figure 2 A flowchart of another micro-application management method according to an embodiment of the present disclosure is shown;

[0047] Figure 3 A block diagram of a micro-application management system according to an embodiment of the present disclosure is shown;

[0048] Figure 4 A block diagram of an exemplary electronic device capable of implementing embodiments of the present disclosure is shown. Detailed Implementation

[0049] To make the objectives, technical solutions, and advantages of the embodiments of this disclosure clearer, the technical solutions of the embodiments of this disclosure will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of this disclosure, and not all embodiments. Based on the embodiments of this disclosure, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of this disclosure.

[0050] Furthermore, the term "and / or" in this article is merely a description of the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can represent: A existing alone, A and B existing simultaneously, or B existing alone. Additionally, the character " / " in this article generally indicates that the preceding and following related objects have an "or" relationship.

[0051] Figure 1 A flowchart of a micro-application management method 100 according to an embodiment of the present disclosure is shown. The method is applicable to a micro-application management system that integrates at least one micro-application. Each micro-application corresponds to an application function module. The at least one micro-application includes: a financial micro-application, an ERP micro-application, an EMS micro-application, an application center micro-application, a to-do center micro-application, etc. Method 100 may include:

[0052] Step 110: Receive a launch command for a target micro-application; wherein the target micro-application is a micro-application among the at least one micro-application;

[0053] Step 120: Obtain the corresponding target micro-application configuration file according to the startup command;

[0054] Step 130: Load the target micro-application according to the target micro-application configuration file;

[0055] Step 140: After the target micro-application is loaded, the interface of the target micro-application is displayed.

[0056] The micro-application management system integrates at least one micro-application, i.e., at least one application function module. Upon receiving a launch command for a target micro-application, the system can retrieve the corresponding target micro-application configuration file based on the command, load the target micro-application according to the configuration file, and then display its interface. This allows users to flexibly use each micro-application on a micro-application management system that integrates multiple application function modules, thereby improving the flexibility of micro-application usage and ultimately enhancing business efficiency.

[0057] In some embodiments, obtaining the corresponding target micro-application configuration file includes:

[0058] Determine whether the target micro-application configuration file is stored locally;

[0059] If the target micro-application configuration file is stored, then the target micro-application configuration file is obtained directly from the local machine;

[0060] If the target micro-application configuration file is not stored, a configuration file retrieval command is sent to the micro-application management center;

[0061] According to the configuration file retrieval instruction, the micro-application configuration file is retrieved from the micro-application management center, wherein the micro-application configuration file includes: the registration information of the target micro-application, as well as the functional description and dependency description of the target micro-application.

[0062] When retrieving the configuration file, it can be determined whether the target micro-application configuration file is stored locally. If the target micro-application configuration file is stored locally, it is retrieved directly from the local machine. If the target micro-application configuration file is not stored locally, a configuration file retrieval command is sent to the micro-application management center. Then, according to the configuration file retrieval command, the micro-application configuration file is retrieved from the micro-application management center. In this way, the target micro-application configuration file can be flexibly retrieved. Thus, when the target micro-application is used for the first time, the target micro-application configuration file can be retrieved from the remote micro-application management center. Subsequently, if the target micro-application configuration file is stored locally, it can be directly retrieved from the local machine to improve the configuration file retrieval rate, thereby improving the loading speed and usage efficiency of the micro-application.

[0063] In some embodiments, before loading the target micro-application, the method further includes:

[0064] Perform integrity verification on the micro-application configuration file;

[0065] Perform a technical compatibility check on the micro-application configuration file.

[0066] Before loading the target micro-application, the integrity and technical compatibility of the micro-application configuration file can be verified to ensure the integrity and compatibility of the micro-application configuration file, thereby ensuring that the micro-application can be loaded normally in different environments.

[0067] In some embodiments, obtaining the corresponding target micro-application configuration file includes:

[0068] Obtain the application identifier and user identifier from the startup command;

[0069] The target micro-application to be launched is determined based on the application identifier;

[0070] Determine user permissions based on the user identifier;

[0071] Determine whether the user permissions include the permission to launch the target micro-application;

[0072] If the permission to launch the target micro-application is included, then the corresponding micro-application configuration file is obtained.

[0073] After obtaining the application identifier and user identifier from the startup command, the target micro-application to be launched can be determined based on the application identifier, and the user permissions can be determined based on the user identifier. Then, it can be determined whether the user permissions include the permission to launch the target micro-application. If the user permissions include the permission to launch the target micro-application, it means that the user has the permission to use the target micro-application. Therefore, the corresponding micro-application configuration file can be automatically obtained.

[0074] In some embodiments, the method further includes:

[0075] Receive events published by the target micro-application;

[0076] Publish the event to all micro-applications that have subscribed to the event within the at least one micro-application; or

[0077] The event is shared to all micro-applications within the at least one micro-application.

[0078] After receiving an event published by the target micro-application, the event can be published to all micro-applications that have subscribed to the event within the at least one micro-application, so that all micro-applications that have subscribed to the event can be informed of the event published by each application as soon as possible; or the event can be shared to all micro-applications within the at least one micro-application, so that all micro-applications can receive the event as soon as possible, thereby enabling fast communication between micro-applications.

[0079] In some embodiments, the method further includes:

[0080] Receive a close command for the target micro-application;

[0081] Uninstall the target micro-application according to the shutdown command, and release the resources occupied by the target micro-application.

[0082] Upon receiving a shutdown command for the target micro-application, the target application can be uninstalled according to the shutdown command, and the memory, CPU and other resources occupied by the target micro-application can be released to make more resources available for other micro-applications.

[0083] In some embodiments, the method further includes:

[0084] Obtain information on the functional importance of each micro-application and user habits;

[0085] The importance of a function can vary depending on the type of business that the micro-application supports. For example, if a micro-application supports the core business of an enterprise, then the function of that micro-application will naturally be more important.

[0086] User habits include the frequency, number of times, and duration of use of micro-applications.

[0087] Based on the functional importance of each micro-application and user habits, the integration priority of each micro-application is determined;

[0088] According to the integration priority of each micro-application, select at least one micro-application from the micro-applications;

[0089] The at least one micro-application is integrated into the micro-application management system.

[0090] Based on the functional importance of each micro-application and user habits, the integration priority of each micro-application can be automatically determined. Then, according to the integration priority of each micro-application, at least one micro-application can be selected from each micro-application. For example, some micro-applications with higher integration priority than the preset priority can be selected and integrated into the micro-application management system, which also makes it convenient for users to use micro-applications and improves the flexibility and convenience of user business within the enterprise.

[0091] This invention provides a micro-application management method, such as... Figure 2 As shown:

[0092] Register in the Micro-Application Management Center;

[0093] Micro-application loading and startup: When a user accesses the workbench (also known as the workbench base) where the micro-application management system is located, the workbench retrieves the corresponding micro-application information from the micro-application management center based on the user's actions and permissions. The workbench dynamically loads the micro-application configuration file and loads the micro-application into the local runtime environment. During the loading process, the workbench manages the micro-application's dependent resources to ensure their correct loading. After loading is complete, the workbench starts the micro-application according to preset startup rules.

[0094] Communication between micro-applications: To achieve data interaction and collaboration between micro-applications, two communication methods are designed: one is based on a global event bus, which supports micro-applications to publish and subscribe to events, ensuring that all subscribers can receive and process the events after they are published; the other is supplemented by shared state management, which manages globally shared data such as user information and system configuration through a shared state library, allowing each micro-application to read and modify it to achieve synchronization.

[0095] Micro-application style isolation: To avoid style conflicts between different micro-applications, a style isolation solution combining CSS modularization and ShadowDOM is adopted. For micro-applications developed using CSS modularization, their styles only take effect within the current micro-application; for micro-applications that do not use CSS modularization, their styles are encapsulated in an independent scope through Shadow DOM to prevent style leakage and conflicts.

[0096] Uninstallation and destruction of micro-applications: When a user switches pages or closes a micro-application, the workbench is responsible for uninstalling and destroying the corresponding micro-application, releasing the resources it occupies, including memory, event listeners, etc., to ensure the stability of the workbench's performance.

[0097] Workbench business application integration (i.e., micro-application integration) implementation steps:

[0098] Business application information aggregation and evaluation

[0099] First, conduct a comprehensive review of the business applications to be integrated, and summarize key information: compile statistics on the technology stack (such as Vue, React, Angular, etc.), core functional modules, and dependent resources (such as interface services and third-party components) of each application; at the same time, clarify the integration method: inbound (only jump to the application through a link, maintaining independent operation) or deep integration (embedded in the workbench as a micro-application, interacting with the base), and determine the integration priority based on the importance of application functions and user usage frequency, and output a "Business Application Integration List" to provide a basis for subsequent registration and transformation.

[0100] Micro-application registration and information verification

[0101] Register your business applications to the micro-application management center according to the independent micro-application standard: Submit registration information (including application name, unique identifier, entry address, technology stack type, integration method, etc.), and attach the functional description and dependency description in the "Business Application Integration List"; The micro-application center verifies the completeness of the information (such as the uniqueness of the identifier) ​​and technical compatibility (such as whether it supports the base communication protocol). After passing the verification, the application is included in the application library and a registration file that can be recognized by the workbench base is generated.

[0102] Lightweight transformation and integration based on the workbench API

[0103] Registered business applications need to be adapted to the workbench base specifications and undergo lightweight modifications: call the APIs provided by the base (such as event bus interface, shared state read and write methods) to achieve basic interaction with the base; for embedded applications, focus on modifying the authentication logic of jump links (integrating with the base's single sign-on); for deeply integrated applications, additional adaptation to style isolation rules is required, and the stability of application startup, rendering, and resource loading in the workbench environment must be tested; after the modification is completed, pass the workbench access test (such as normal function and no style conflicts) before officially connecting to the workbench.

[0104] Development and adaptation of extended components for customized needs

[0105] For business applications with personalized needs (such as dedicated data dashboards and customized operation processes), develop adaptable components based on the workbench's extension capabilities: Develop micro-application extension components (such as custom data components and interactive plugins) according to the workbench extension API specifications to implement unique functions; extension components need to be registered in the workbench's component marketplace to support on-demand loading; at the same time, through the workbench's permission management mechanism, ensure that components are only open to target users; finally, after functional verification (such as normal linkage with the main application functions and meeting customized scenarios), adapt to users' personalized needs.

[0106] The above steps form a closed loop of "information sorting → registration and access → standardization transformation → personalized expansion", ensuring that business applications are efficiently integrated into the workbench while being compatible with diverse and customized needs.

[0107] It should be noted that, for the sake of simplicity, the foregoing method embodiments are all described as a series of actions. However, those skilled in the art should understand that this disclosure is not limited to the described order of actions, because according to this disclosure, some steps can be performed in other orders or simultaneously. Furthermore, those skilled in the art should also understand that the embodiments described in the specification are all optional embodiments, and the actions and modules involved are not necessarily essential to this disclosure.

[0108] The above is an introduction to the method embodiments. The following describes the solution described in this disclosure further through device embodiments.

[0109] Figure 3 A block diagram of a micro-application management system 300 according to an embodiment of the present disclosure is shown. Figure 3 As shown, system 300 includes:

[0110] The receiving module 310 is configured to receive a launch command for a target micro-application; wherein the target micro-application is a micro-application among the at least one micro-application.

[0111] The acquisition module 320 is used to acquire the corresponding target micro-application configuration file according to the startup instruction;

[0112] The loading module 330 is used to load the target micro-application according to the target micro-application configuration file;

[0113] The display module 340 is used to display the interface of the target micro-application after the target micro-application has been loaded.

[0114] Those skilled in the art will clearly understand that, for the sake of convenience and brevity, the specific working process of the described module can be referred to the corresponding process in the foregoing method embodiments, and will not be repeated here.

[0115] According to embodiments of the present disclosure, the present disclosure also provides an electronic device and a non-transitory computer-readable storage medium storing computer instructions.

[0116] Figure 4 A schematic block diagram of an electronic device 800 that can be used to implement embodiments of the present disclosure is shown. The electronic device is intended to represent various forms of digital computers, such as laptop computers, desktop computers, workstations, personal digital assistants, servers, blade servers, mainframe computers, and other suitable computers. The electronic device may also represent various forms of mobile devices, such as personal digital processors, cellular phones, smartphones, wearable devices, and other similar computing devices. The components shown herein, their connections and relationships, and their functions are merely illustrative and are not intended to limit the implementation of the present disclosure described and / or claimed herein.

[0117] Device 800 includes a computing unit 801, which can perform various appropriate actions and processes based on a computer program stored in read-only memory (ROM) 802 or a computer program loaded from storage unit 808 into random access memory (RAM) 803. RAM 803 may also store various programs and data required for the operation of device 800. The computing unit 801, ROM 802, and RAM 803 are interconnected via bus 804. Input / output (I / O) interface 805 is also connected to bus 804.

[0118] Multiple components in device 800 are connected to I / O interface 805, including: input unit 806, such as keyboard, mouse, etc.; output unit 807, such as various types of monitors, speakers, etc.; storage unit 808, such as disk, optical disk, etc.; and communication unit 809, such as network card, modem, wireless transceiver, etc. Communication unit 809 allows device 800 to exchange information / data with other devices through computer networks such as the Internet and / or various telecommunications networks.

[0119] The computing unit 801 can be a variety of general-purpose and / or special-purpose processing components with processing and computing capabilities. Some examples of the computing unit 801 include, but are not limited to, a central processing unit (CPU), a graphics processing unit (GPU), various special-purpose artificial intelligence (AI) computing chips, various computing units running machine learning model algorithms, a digital signal processor (DSP), and any suitable processor, controller, microcontroller, etc. The computing unit 801 performs the various methods and processes described above, such as method 100. For example, in some embodiments, method 100 may be implemented as a computer software program tangibly contained in a machine-readable medium, such as storage unit 808. In some embodiments, part or all of the computer program may be loaded and / or installed on device 800 via ROM 802 and / or communication unit 809. When the computer program is loaded into RAM 803 and executed by the computing unit 801, one or more steps of method 100 described above may be performed. Alternatively, in other embodiments, the computing unit 801 may be configured to perform method 100 by any other suitable means (e.g., by means of firmware).

[0120] Various embodiments of the systems and techniques described above herein can be implemented in digital electronic circuit systems, integrated circuit systems, field-programmable gate arrays (FPGAs), application-specific integrated circuits (ASICs), application-specific standard products (ASSPs), systems-on-a-chip (SoCs), payload-programmable logic devices (CPLDs), computer hardware, firmware, software, and / or combinations thereof. These various embodiments may include implementations in one or more computer programs that can be executed and / or interpreted on a programmable system including at least one programmable processor, which may be a dedicated or general-purpose programmable processor, capable of receiving data and instructions from a storage system, at least one input device, and at least one output device, and transmitting data and instructions to the storage system, the at least one input device, and the at least one output device.

[0121] The program code used to implement the methods of this disclosure may be written in any combination of one or more programming languages. This program code may be provided to a processor or controller of a general-purpose computer, special-purpose computer, or other programmable data processing apparatus, such that when executed by the processor or controller, the program code causes the functions / operations specified in the flowcharts and / or block diagrams to be implemented. The program code may be executed entirely on a machine, partially on a machine, as a standalone software package partially on a machine and partially on a remote machine, or entirely on a remote machine or server.

[0122] In the context of this disclosure, a machine-readable medium can be a tangible medium that may contain or store a program for use by or in conjunction with an instruction execution system, apparatus, or device. A machine-readable medium can be a machine-readable signal medium or a machine-readable storage medium. A machine-readable medium can be, but is not limited to, electronic, magnetic, optical, electromagnetic, infrared, or semiconductor systems, apparatus, or devices, or any suitable combination of the foregoing. More specific examples of machine-readable storage media include electrical connections based on one or more wires, portable computer disks, hard disks, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM or flash memory), optical fiber, portable compact disk read-only memory (CD-ROM), optical storage devices, magnetic storage devices, or any suitable combination of the foregoing.

[0123] To provide interaction with a user, the systems and techniques described herein can be implemented on a computer having: a display device for displaying information to the user (e.g., a CRT (cathode ray tube) or LCD (liquid crystal display) monitor); and a keyboard and pointing device (e.g., a mouse or trackball) through which the user provides input to the computer. Other types of devices can also be used to provide interaction with the user; for example, feedback provided to the user can be any form of sensory feedback (e.g., visual feedback, auditory feedback, or tactile feedback); and input from the user can be received in any form (including sound input, voice input, or tactile input).

[0124] The systems and technologies described herein can be implemented in computing systems that include backend components (e.g., as a data server), or computing systems that include middleware components (e.g., an application server), or computing systems that include frontend components (e.g., a user computer with a graphical user interface or web browser through which a user can interact with embodiments of the systems and technologies described herein), or any combination of such backend, middleware, or frontend components. The components of the system can be interconnected via digital data communication of any form or medium (e.g., a communication network). Examples of communication networks include local area networks (LANs), wide area networks (WANs), and the Internet.

[0125] Computing systems can include clients and servers. Clients and servers are generally located far apart and typically interact via communication networks. Client-server relationships are created by computer programs running on the respective computers and having a client-server relationship with each other. Servers can be cloud servers, servers in distributed systems, or servers incorporating blockchain technology.

[0126] It should be understood that the various forms of processes shown above can be used to rearrange, add, or delete steps. For example, the steps described in this disclosure can be executed in parallel, sequentially, or in different orders, as long as the desired result of the technical solution disclosed in this disclosure can be achieved, and this is not limited herein.

[0127] The specific embodiments described above do not constitute a limitation on the scope of protection of this disclosure. Those skilled in the art should understand that various modifications, combinations, sub-combinations, and substitutions can be made according to design requirements and other factors. Any modifications, equivalent substitutions, and improvements made within the spirit and principles of this disclosure should be included within the scope of protection of this disclosure.

Claims

1. A micro application management method, the method being applicable to a micro application management system, characterized in that, The micro application management system is integrated with at least one micro application, and the method comprises: receiving a starting instruction for a target micro application; wherein the target micro application is a micro application in the at least one micro application; obtaining a corresponding target micro application configuration file according to the starting instruction; loading the target micro application according to the target micro application configuration file; after the target micro application is loaded, the interface of the target micro application is displayed.

2. The method of claim 1, wherein, The corresponding target micro application configuration file is obtained, comprising: determining whether the target micro application configuration file is stored locally; if the target micro application configuration file is stored, the target micro application configuration file is directly obtained from the local; if the target micro application configuration file is not stored, a configuration file obtaining instruction is sent to the micro application management center; according to the configuration file obtaining instruction, the micro application configuration file is obtained from the micro application management center, wherein the micro application configuration file comprises: registration information of the target micro application, and function description and dependency description of the target micro application.

3. The method of claim 1, wherein, before loading the target micro application, the method further comprises: performing integrity verification on the micro application configuration file; performing technical compatibility verification on the micro application configuration file.

4. The method of claim 1, wherein, The corresponding target micro application configuration file is obtained, comprising: obtaining the application identifier and the user identifier in the starting instruction; determining the target micro application to be started according to the application identifier; determining the user authority according to the user identifier; determining whether the user authority includes the authority to start the target micro application; if the authority to start the target micro application is included, the corresponding micro application configuration file is obtained.

5. The method of claim 1, wherein, The method further comprises: receiving an event published by the target micro application; publishing the event to all micro applications in the at least one micro application that subscribe to the event; or sharing the event to all micro applications in the at least one micro application.

6. The method of claim 1, wherein, The method further comprises: receiving a closing instruction for a target micro application; uninstalling the target micro application according to the closing instruction, and releasing the resources occupied by the target micro application.

7. The method of any one of claims 1 to 6, wherein, The method further comprises: obtaining the function importance and user usage habit of each micro application; determining the integration priority of each micro application according to the function importance and user usage habit of each micro application; selecting the at least one micro application from the micro applications according to the integration priority of each micro application; integrating the at least one micro application on the micro application management system.

8. A micro-application management system, characterized in that, The micro application management system is integrated with at least one micro application, and the system comprises: a receiving module for receiving a starting instruction for a target micro application; wherein the target micro application is a micro application in the at least one micro application; an obtaining module for obtaining a corresponding target micro application configuration file according to the starting instruction; a loading module for loading the target micro application according to the target micro application configuration file; a display module for displaying the interface of the target micro application after the target micro application is loaded.

9. An electronic device, comprising: Comprising: a memory and a processor, the memory has a computer program stored thereon, and the processor executes the program to implement the method according to any one of claims 1-7. 10.A computer readable storage medium, comprising: when instructions in the storage medium are executed by a processor corresponding to an electronic device, the electronic device is enabled to implement the micro application management and control method according to any one of claims 1-7.

Images