Three-party application integration method and device based on Android, equipment and medium

Abstract

The invention discloses a three-party application integration method and device based on Android, equipment and a medium, belongs to the technical field of application integration, and aims to solve the technical problem of how to avoid an installation blocking process in a use process and ensure use and update of multiple application services while ensuring use of an Android native function. According to the technical scheme, the method comprises the following steps of: constructing an application management warehouse: constructing a project remote application management warehouse which is associated to an Android mobile phone end application platform and is used for managing third-party applications; issuing the application: packaging the third-party application, and issuing the third-party application to the established remote application warehouse; warehouse address configuration: the Android mobile phone end application platform configures a remote warehouse address; application integration: when an Android mobile phone end application platform is started, loading application configuration data of an application warehouse, reading a background interface of the application platform, and loading a third-party application needing to be displayed; and application opening: clicking the third-party application, and directly opening the third-party application on the application by using an Android reflection mechanism.

Description

Technical Field

[0001] The present invention relates to the field of application integration technology, and in particular to an Android-based three-party application integration method, device, equipment and medium. Background Art

[0002] In the terminology of Maven (a Java project management tool), a repository is a place. A Maven repository is a third-party library that a project depends on, and the location of this library is called a repository. In Maven, any dependency, plugin, or output of a project build can be called a component. Maven repository can help manage components (mainly JAR, a common archive file format in the Java platform, used to store multiple Java class files, related resources, and metadata). It is where all JAR files (WAR, ZIP, POM, and other archive file formats) are placed.

[0003] In Android applications, resource files cannot be directly inflated (used to convert layout files into corresponding view objects in Android), nor can they be applied using R (application resource files), because the application context (Context) is different. Resource files can be packaged (*.pak (a data packaging or compression format, often used to store resource files of games, applications or other software) files and APK (a file format for installing and distributing applications on the Android operating system) together), so that the resource files can be unzipped to the specified folder without installing the APK, and then the folder address can be passed to the third-party application, so that the third-party application can still read and use these resources through the File (file) inputstream (input) stream.

[0004] DexClassLoader is a class loader (ClassLoader) in Android development, used to load Dex files (Dalvik Executable File, an executable file format optimized for the Dalvik virtual machine). In the Android system, the code of the application is usually compiled into Dalvik (a virtual machine used by the Android operating system) bytecode and packaged into a Dex file. DexClassLoader can dynamically load and run these Dex files (jar / apk / dex, Android's executable file). DexClassLoader inherits from BaseDexClassLoader (an abstract class in Android, used to dynamically load classes in DEX files. It is the base class of DexClassLoader and provides basic functions for loading and managing DEX files). It provides a way to load Dex files in non-system paths. Compared with the system's default class loader, DexClassLoader allows applications to load external Dex files at runtime, thereby dynamically loading and running unknown classes and code. Using DexClassLoader, developers can store Dex files in the application's private directory, SD (memory) card, or anywhere else, and load the classes in them by specifying the path of the Dex file. DexClassLoader can only load compiled Dex files, not Java source code directly.

[0005] The methods of installing third-party applications on the Android mobile application platform in the market are investigated and analyzed, mainly including native applications (Natvive App), H5 applications (Web App or .zip package), plug-in transformation applications (such as 360Replugin plug-in), mini-programs (such as WeChat mini-programs, Baidu mini-programs, Alipay mini-programs), etc. However, in the process of use, it is found that each integration method has its own advantages and disadvantages: Native App (native application) and Web App (application developed in H5 language) have obvious advantages in user experience, but in actual projects, some clients will be frequently upgraded due to business changes, resulting in poor user experience. Web App has a poor experience in business related to mobile phone hardware, or even cannot be used, such as poor fluency of audio and video, intelligent inspection, and printer cannot be used. Plug-in transformation applications are heavily dependent on the provider of third-party plug-ins. Once the provider does not support the integration of third-party SDK (jar package or source code), it will be very difficult to transform it, or even impossible to integrate and use it. Mini Programs are private programs in which the platform and the Mini Programs are bidirectionally bound. The development of Mini Programs is controlled by the platform provider (such as WeChat and Alipay), and there are risks such as unstable technical framework, insecure data, and inability to integrate SDKs.

[0006] Therefore, how to ensure the use of Android native functions while avoiding the blocking process of installation during use and ensuring the use and update of multiple application services is a technical problem that needs to be solved urgently. Summary of the invention

[0007] The technical task of the present invention is to provide an Android-based third-party application integration method, device, equipment and medium to solve the problem of how to ensure the use of Android native functions while avoiding the blocking process of installation during use and ensuring the use and update of multiple application services.

[0008] The technical task of the present invention is achieved in the following way: a third-party application integration method based on Android, which is to publish the third-party application to the warehouse, integrate the third-party application into the Android mobile phone application platform in a similar way to dependency integration, and directly open the third-party application without installation through the Android reflection mechanism; the details are as follows:

[0009] Build an application management warehouse: Build a remote application management warehouse for the project, link it to the Android mobile application platform, and manage third-party applications. The project remote warehouse can be implemented in a variety of ways, depending on the project's needs and environment.

[0010] Release applications: package third-party applications and release them to the established remote application repository;

[0011] Configure warehouse address: Android mobile application platform configures remote warehouse address;

[0012] Integrated application: When the Android mobile application platform is started, the application configuration data of the application warehouse is loaded, and the application platform background interface is read at the same time, the third-party application to be displayed is loaded, multi-threading is started, and it is silently downloaded from the warehouse. That is, the Android mobile phone uses a similar remote dependency method to download and update third-party applications;

[0013] Open the app: Click on a third-party app and use the Android reflection mechanism to open the third-party app directly on the app without installation.

[0014] As a preferred option, the construction of the application management warehouse is as follows:

[0015] Download and install the warehouse management tool; the warehouse management tool uses Nexus Repository Manager;

[0016] Configure the warehouse;

[0017] Create a warehouse;

[0018] Configure the client.

[0019] Preferably, when opening an application, the apk package to be opened is found in the specified storage directory on the Android phone, and the Android reflection mechanism is used to open the third-party application to be used; wherein, the apk package is a file format used to install and distribute application programs on the Android operating system.

[0020] Preferably, open the application as follows:

[0021] Specify the apk file path;

[0022] The optimized dex file output directory is used to store the optimized dex file, and the corresponding directory is an application-private directory;

[0023] Create a DexClassLoader instance;

[0024] Load the target class;

[0025] Create an instance of the class;

[0026] Get the target method and call it.

[0027] Preferably, dex is an executable file format used by the Dalvik virtual machine; the Dalvik virtual machine is a virtual machine on the Android operating system that is used to execute the bytecode of Android applications.

[0028] Preferably, DexClassLoader is a class in Android that is used to dynamically load dex files and load the classes in them;

[0029] DexClassLoader allows loading an uninstalled apk file or other dex file from a specified path at runtime and adding the classes in it to the application's classpath.

[0030] An Android-based third-party application integration device, which publishes third-party applications to a warehouse, integrates third-party applications into an Android mobile phone application platform in a similar way to dependency integration, and directly opens third-party applications without installation through the Android reflection mechanism; the device includes:

[0031] The construction module is used to build a remote application management warehouse for the project, which is linked to the Android mobile application platform and used for the management of third-party applications. The project remote warehouse is implemented in a variety of ways, depending on the needs and environment of the project.

[0032] The publishing module is used to package third-party applications and publish them to the established remote application repository;

[0033] Configuration module, used to configure the remote warehouse address through the Android mobile application platform;

[0034] The integration module is used to load the application configuration data of the application warehouse when the Android mobile phone application platform is started, and read the application platform background interface at the same time, load the third-party applications that need to be displayed, start multi-threading, and download silently from the warehouse. That is, the Android mobile phone uses a similar remote dependency method to download and update third-party applications;

[0035] The open module is used to click on third-party applications and use the Android reflection mechanism to directly open third-party applications on the application without installation.

[0036] Preferably, the building module includes:

[0037] The download submodule is used to download and install the repository management tool. The repository management tool uses NexusRepository Manager.

[0038] Configuration submodule 1, used to configure the warehouse;

[0039] Create a submodule to create a warehouse;

[0040] Configuration submodule 2, used to configure the client;

[0041] The opening module finds the apk package to be opened in the storage directory specified by the Android phone, and uses the Android reflection mechanism to open the third-party application to be used; the apk package is a file format used to install and distribute applications on the Android operating system; the opening module includes:

[0042] The path specification submodule is used to specify the apk file path;

[0043] The directory output submodule is used to output the optimized dex file to a directory. The corresponding directory is used to store the optimized dex file, and the corresponding directory is an application-private directory. Dex is the executable file format used by the Dalvik virtual machine. The Dalvik virtual machine is a virtual machine on the Android operating system that is used to execute the bytecode of Android applications.

[0044] The instance creation submodule is used to create a DexClassLoader instance. DexClassLoader is a class in Android that is used to dynamically load dex files and load the classes in them. DexClassLoader allows loading an uninstalled apk file or other dex file from a specified path at runtime and adding the classes in them to the class path of the application.

[0045] Load submodule to load target class;

[0046] Create a submodule to create instances of the class;

[0047] Get the submodule to get the target method and call it.

[0048] An electronic device comprising: a memory and at least one processor;

[0049] Wherein, the memory stores a computer program;

[0050] The at least one processor executes the computer program stored in the memory, so that the at least one processor performs the Android-based third-party application integration method as described above.

[0051] A computer-readable storage medium stores a computer program, and the computer program can be executed by a processor to implement the Android-based three-party application integration method as described above.

[0052] The Android-based third-party application integration method, device, equipment and medium of the present invention have the following advantages:

[0053] The application of the present invention integrates and opens third-party applications on the mobile phone in a manner similar to a remote warehouse, which can not only use the native functions of Android, but also avoid the blocking process of installation during use. The download and update of third-party applications are controlled in real time on the remote warehouse, which is convenient for maintenance and updates by third-party manufacturers. The mobile phone only needs to install the mobile application platform once to ensure the use and update of multiple application services. BRIEF DESCRIPTION OF THE DRAWINGS

[0054] The present invention is further described below in conjunction with the accompanying drawings.

[0055] Attached Figure 1 This is a flowchart of the third-party application integration method based on Android. DETAILED DESCRIPTION

[0056] The Android-based third-party application integration method, device, equipment and medium of the present invention are described in detail below with reference to the accompanying drawings and specific embodiments of the specification.

[0057] Embodiment 1:

[0058] As attached Figure 1 As shown, this embodiment provides a third-party application integration method based on Android, which is to publish the third-party application to the warehouse, integrate the third-party application into the Android mobile phone application platform in a similar way to dependency integration, and directly open the third-party application without installation through the Android reflection mechanism; the details are as follows:

[0059] S1. Build an application management warehouse: Build a remote application management warehouse for the project, which is linked to the Android mobile application platform for the management of third-party applications. The project remote warehouse can be implemented in a variety of ways, depending on the needs and environment of the project.

[0060] S2. Application publishing: package third-party applications and publish them to the established remote application repository;

[0061] S3. Configure warehouse address: The Android mobile application platform configures the remote warehouse address;

[0062] S4. Integrated application: When the Android mobile application platform is started, the application configuration data of the application warehouse is loaded, and the application platform background interface is read at the same time, the third-party application to be displayed is loaded, multi-threading is started, and it is silently downloaded from the warehouse. That is, the Android mobile phone uses a similar remote dependency method to download and update third-party applications;

[0063] S5. Open the application: Click on the third-party application and use the Android reflection mechanism to open the third-party application directly on the application without installation.

[0064] The construction of the application management warehouse in step S1 of this embodiment is specifically as follows:

[0065] S101, download and install a warehouse management tool; wherein the warehouse management tool adopts Nexus RepositoryManager;

[0066] S102, configure warehouse;

[0067] S103, create a warehouse;

[0068] S104. Configure the client.

[0069] Among them, the Android reflection mechanism, as the application of the Java reflection mechanism on the Android platform, mainly refers to the ability of Android applications to dynamically access, detect and modify their own or other classes' states or behaviors during operation. The following is a detailed explanation of the Android reflection mechanism:

[0070] Basic concept of reflection mechanism: Reflection mainly refers to the ability of a program to access, detect and modify its own state or behavior. In the field of computer science, reflection is a type of application that can self-describe and self-control. Such applications use a certain mechanism to describe and detect their own behavior, and can adjust or modify the state and related semantics of the behavior described by the application according to the state and results of its own behavior.

[0071] Application of reflection mechanism in Android: In Android development, reflection mechanism is widely used in the following aspects:

[0072] Accessing private members: In the source code of the Android SDK, many classes or methods are marked as @hide, making them invisible in the generated SDK. Through reflection, developers can bypass this restriction and access and use these private members.

[0073] For example, reflection can be used to access private fields or methods of a class and perform operations on them.

[0074] Dynamically loading classes: Reflection allows programs to dynamically load classes at runtime without statically determining the existence of the class at compile time. This is very useful for implementing advanced features such as plug-ins and modularization.

[0075] Decoupling: In an Android project, different modules may need to call each other. Through reflection, decoupling and calling between modules can be achieved without directly relying on other module codes.

[0076] Testing: In unit tests or integration tests, reflection can be used to access and modify internal states that are not normally visible, allowing for deeper testing.

[0077] Implementation method of reflection mechanism: In Android, the reflection mechanism is mainly implemented through Java's reflection API, which mainly includes classes such as Class, Field, Method and Constructor.

[0078] Class class: represents a class and is used to obtain class metadata information, such as the class name, parent class, interface, field, method, etc. There are three main ways to obtain a Class object: calling the getClass() method through the object, using the Class.forName() method, and using the .class literal.

[0079] Field class: represents the member variables (attributes) of a class. You can get and set the values ​​of private fields through reflection, even if these fields are declared as private in the class.

[0080] Method class: represents the method of a class. Private methods of a class can be called through reflection, and parameters can be passed and return values ​​can be received.

[0081] Constructor class: represents the construction method of a class. Object instances can be created dynamically at runtime through reflection.

[0082] In summary, the Android reflection mechanism is an important application of the Java reflection mechanism on the Android platform, which allows Android applications to dynamically access, detect, and modify the state or behavior of themselves or other classes at runtime. Through the reflection mechanism, developers can achieve more flexible code design and more powerful function extensions. However, it is also necessary to pay attention to the performance issues and code readability issues that may be caused by the reflection mechanism.

[0083] When opening the application in step S5 of this embodiment, the apk package to be opened is found in the specified storage directory on the Android phone, and the Android reflection mechanism is used to open the third-party application to be used; wherein the apk package is a file format used to install and distribute application programs on the Android operating system.

[0084] The specific details of opening the application in step S5 of this embodiment are as follows:

[0085] S501, specify the apk file path;

[0086] S502, output directory of optimized dex file, the corresponding directory is used to store the optimized dex file, and the corresponding directory is an application-private directory;

[0087] S503, create a DexClassLoader instance;

[0088] S504, load the target class;

[0089] S505, creating an instance of the class;

[0090] S506: Get the target method and call it.

[0091] The dex in step S502 of this embodiment is an executable file format used by the Dalvik virtual machine; the Dalvik virtual machine is a virtual machine on the Android operating system, which is used to execute the bytecode of the Android application.

[0092] The DexClassLoader in step S503 of this embodiment is a class in Android, which is used to dynamically load the dex file and load the class therein;

[0093] DexClassLoader allows loading an uninstalled apk file or other dex file from a specified path at runtime and adding the classes in it to the application's classpath.

[0094] Embodiment 2:

[0095] This embodiment provides an Android-based third-party application integration device, which publishes third-party applications to a warehouse, integrates third-party applications into an Android mobile phone application platform in a similar way to dependency integration, and directly opens third-party applications without installation through the Android reflection mechanism; the device includes:

[0096] The construction module is used to build a remote application management warehouse for the project, which is linked to the Android mobile application platform and used for the management of third-party applications. The project remote warehouse is implemented in a variety of ways, depending on the needs and environment of the project.

[0097] The publishing module is used to package third-party applications and publish them to the established remote application repository;

[0098] Configuration module, used to configure the remote warehouse address through the Android mobile application platform;

[0099] The integration module is used to load the application configuration data of the application warehouse when the Android mobile phone application platform is started, and read the application platform background interface at the same time, load the third-party applications that need to be displayed, start multi-threading, and download silently from the warehouse. That is, the Android mobile phone uses a similar remote dependency method to download and update third-party applications;

[0100] The open module is used to click on third-party applications and use the Android reflection mechanism to directly open third-party applications on the application without installation.

[0101] The building modules in this embodiment include:

[0102] The download submodule is used to download and install the repository management tool; the repository management tool uses NexusRepository Manager;

[0103] Configuration submodule 1, used to configure the warehouse;

[0104] Create a submodule to create a warehouse;

[0105] Configuration submodule 2 is used to configure the client.

[0106] The opening module in this embodiment finds the apk package to be opened in the storage directory specified by the Android mobile phone, and uses the Android reflection mechanism to open the third-party application to be used; wherein the apk package is a file format for installing and distributing applications on the Android operating system; the opening module includes:

[0107] The path specification submodule is used to specify the apk file path;

[0108] The directory output submodule is used to output the optimized dex file to a directory. The corresponding directory is used to store the optimized dex file, and the corresponding directory is an application-private directory. Dex is the executable file format used by the Dalvik virtual machine. The Dalvik virtual machine is a virtual machine on the Android operating system that is used to execute the bytecode of Android applications.

[0109] The instance creation submodule is used to create a DexClassLoader instance. DexClassLoader is a class in Android that is used to dynamically load dex files and load the classes in them. DexClassLoader allows loading an uninstalled apk file or other dex file from a specified path at runtime and adding the classes in them to the class path of the application.

[0110] Load submodule to load target class;

[0111] Create a submodule to create instances of the class;

[0112] Get the submodule to get the target method and call it.

[0113] Embodiment 3:

[0114] This embodiment also provides an electronic device, including: a memory and a processor;

[0115] Wherein, the memory stores computer-executable instructions;

[0116] The processor executes the computer-executable instructions stored in the memory, so that the processor executes the Android-based third-party application integration method in any embodiment of the present invention.

[0117] The processor may be a central processing unit (CPU), or other general-purpose processors, digital signal processors (DSP), application-specific integrated circuits (ASIC), field-programmable gate arrays (FPGA) or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. The processor may be a microprocessor or any conventional processor, etc.

[0118] The memory can be used to store computer programs and / or modules. The processor realizes various functions of the electronic device by running or executing the computer programs and / or modules stored in the memory, and calling the data stored in the memory. The memory can mainly include a program storage area and a data storage area, wherein the program storage area can store an operating system, at least one application required for a function, etc.; the data storage area can store data created according to the use of the terminal, etc. In addition, the memory can also include a high-speed random access memory, and can also include a non-volatile memory, such as a hard disk, a memory, a plug-in hard disk, a smart memory card (SMC), a secure digital (SD) card, a flash memory card, at least one disk storage period, a flash memory device, or other volatile solid-state storage devices.

[0119] Embodiment 4:

[0120] This embodiment also provides a computer-readable storage medium, which stores a plurality of instructions, which are loaded by a processor, so that the processor executes the Android-based three-party application integration method in any embodiment of the present invention. Specifically, a system or device equipped with a storage medium can be provided, on which a software program code that implements the functions of any of the above embodiments is stored, and a computer (or CPU or MPU) of the system or device reads and executes the program code stored in the storage medium.

[0121] In this case, the program code itself read from the storage medium can realize the function of any one of the above-mentioned embodiments, and thus the program code and the storage medium storing the program code constitute a part of the present invention.

[0122] The storage medium embodiments for providing the program code include a floppy disk, a hard disk, a magneto-optical disk, an optical disk (such as CD-ROM, CD-R, CD-RW, DVD-ROM, DVD-RYM, DVD-RW, DVD+RW), a magnetic tape, a non-volatile memory card, and a ROM. Alternatively, the program code can be downloaded from a server computer via a communication network.

[0123] In addition, it should be clear that the functions of any of the above embodiments can be implemented not only by executing the program code read by the computer, but also by enabling an operating system operating on the computer to complete part or all of the actual operations based on instructions from the program code.

[0124] In addition, it can be understood that the program code read from the storage medium is written to a memory provided in an expansion board inserted into the computer or written to a memory provided in an expansion unit connected to the computer, and then based on the instructions of the program code, a CPU installed on the expansion board or the expansion unit is enabled to perform part or all of the actual operations, thereby realizing the functions of any of the above-mentioned embodiments.

[0125] Finally, it should be noted that the above embodiments are only used to illustrate the technical solutions of the present invention, rather than to limit it. Although the present invention has been described in detail with reference to the aforementioned embodiments, those skilled in the art should understand that they can still modify the technical solutions described in the aforementioned embodiments, or replace some or all of the technical features therein with equivalents. However, these modifications or replacements do not cause the essence of the corresponding technical solutions to deviate from the scope of the technical solutions of the embodiments of the present invention.

Claims

1. A third-party application integration method based on Android, characterized in that: This method is to publish the third-party application to the warehouse, integrate the third-party application into the Android mobile application platform in a similar way to dependency integration, and open the third-party application directly without installation through the Android reflection mechanism; the details are as follows: Build an application management warehouse: Build a remote application management warehouse for the project, link it to the Android mobile application platform, and manage third-party applications; Release applications: package third-party applications and release them to the established remote application repository; Configure warehouse address: Android mobile application platform configures remote warehouse address; Integrated application: When the Android mobile application platform is started, the application configuration data of the application warehouse is loaded, and the application platform background interface is read at the same time, the third-party application to be displayed is loaded, multi-threading is started, and it is silently downloaded from the warehouse. That is, the Android mobile phone uses a similar remote dependency method to download and update third-party applications; Open the app: Click on a third-party app and use the Android reflection mechanism to open the third-party app directly on the app without installation.

2. The Android-based third-party application integration method according to claim 1, characterized in that: The details of building an application management warehouse are as follows: Download and install the warehouse management tool; the warehouse management tool uses Nexus Repository Manager; Configure the warehouse; Create a warehouse; Configure the client.

3. The Android-based third-party application integration method according to claim 1, characterized in that: When opening an application, the apk package to be opened is found in the specified storage directory on the Android phone, and the Android reflection mechanism is used to open the third-party application to be used; among them, the apk package is a file format used to install and distribute application programs on the Android operating system.

4. The Android-based third-party application integration method according to any one of claims 1 to 3, characterized in that: Open the app as follows: Specify the apk file path; The optimized dex file output directory is used to store the optimized dex file, and the corresponding directory is an application-private directory; Create a DexClassLoader instance; Load the target class; Create an instance of the class; Get the target method and call it.

5. The Android-based third-party application integration method according to claim 4, characterized in that: dex is the executable file format used by the Dalvik virtual machine; the Dalvik virtual machine is a virtual machine on the Android operating system that is used to execute the bytecode of Android applications.

6. The Android-based third-party application integration method according to claim 4, characterized in that: DexClassLoader is a class in Android that is used to dynamically load dex files and load the classes in them; DexClassLoader allows loading an uninstalled apk file or other dex file from a specified path at runtime and adding the classes in it to the application's classpath.

7. An Android-based third-party application integration device, characterized in that: The device publishes third-party applications to the warehouse, integrates third-party applications into the Android mobile application platform in a similar way to dependency integration, and directly opens third-party applications without installation through the Android reflection mechanism; the device includes: Build a module to build a remote application management warehouse for the project, link it to the Android mobile application platform, and manage third-party applications; The publishing module is used to package third-party applications and publish them to the established remote application repository; Configuration module, used to configure the remote warehouse address through the Android mobile application platform; The integration module is used to load the application configuration data of the application warehouse when the Android mobile phone application platform is started, and read the application platform background interface at the same time, load the third-party applications that need to be displayed, start multi-threading, and download silently from the warehouse. That is, the Android mobile phone uses a similar remote dependency method to download and update third-party applications; The open module is used to click on third-party applications and use the Android reflection mechanism to directly open third-party applications on the application without installation.

8. The Android-based third-party application integration device according to claim 7, characterized in that: Building blocks include: The download submodule is used to download and install the repository management tool. The repository management tool uses Nexus RepositoryManager. Configuration submodule 1, used to configure the warehouse; Create a submodule to create a warehouse; Configuration submodule 2, used to configure the client; The opening module finds the apk package to be opened in the storage directory specified by the Android phone, and uses the Android reflection mechanism to open the third-party application to be used; the apk package is a file format used to install and distribute applications on the Android operating system; the opening module includes: The path specification submodule is used to specify the apk file path; The directory output submodule is used to output the optimized dex file to a directory. The corresponding directory is used to store the optimized dex file, and the corresponding directory is an application-private directory. Dex is the executable file format used by the Dalvik virtual machine. The Dalvik virtual machine is a virtual machine on the Android operating system that is used to execute the bytecode of Android applications. The instance creation submodule is used to create a DexClassLoader instance. DexClassLoader is a class in Android that is used to dynamically load dex files and load the classes in them. DexClassLoader allows loading an uninstalled apk file or other dex file from a specified path at runtime and adding the classes in them to the class path of the application. Load submodule to load target class; Create a submodule to create instances of the class; Get the submodule to get the target method and call it.

9. An electronic device, characterized in that: include: memory and at least one processor; Wherein, the memory stores a computer program; The at least one processor executes the computer program stored in the memory, so that the at least one processor performs the Android-based three-party application integration method as described in any one of claims 1 to 6.

10. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores a computer program, which can be executed by a processor to implement the Android-based three-party application integration method as described in any one of claims 1 to 6.

Images