The mobile development platform mPaaS supports the following three integration methods. This topic describes these three modes and provides recommendations for selecting an appropriate integration method.
Native AAR integration method
Native AAR integration method uses the packaging scheme of native Android AAR. This scheme allows Android developers to use the technology stack that they are already familiar with. It is not necessary for developers to learn the packaging knowledge related to mPaaS. Developers can integrate mPaaS into their projects by using the mPaaS Plugin in Android Studio or using Maven pom and bom directly. The native AAR integration method allows developers to use mPaaS more easily with reduced cost. This mode is recommended for customers who want to start the use of mPaaS quickly and have no demand for component-based (Portal&Bundle) integration method.
The native AAR mode is supported by 10.1.68 or later versions.
Componentized integration method - Portal & Bundle
The component-based integration means that mPaaS divides an app into one or more Bundle projects that run independently and one Portal project based on the Open Service Gateway Initiative (OSGi) technology. mPaaS will manage the lifecycle and dependency of each Bundle project, and use the Portal project to merge all Bundle project packages into a single executable .apk package. This method is applicable to concurrent development projects with large-scale multiplayers.The use of component-based integration requires the using of an mPaaS gradle packaging tool, which has some requirements on the gradle version and com.android.tools.build:gradle version.
How to select an integration method
If mPaaS is expected to be easily accessed and used as other SDKs, we recommend that you use native AAR integration method.
The concept of large-scale concurrent development is important for you to reconstruct your project using mPaaS. We recommend that you use componentized integration method.
Comparison of integration methods
Native AAR integration | Componentized integration | |
Source | Official Google integration method | Alipay |
Packing speed | Slowest among the three, which is exactly the same as the native integrate | The packing speed is fast, and the packing time is scattered |
Project composition | App module and library module | Portal (the shell of an App) and Bundle (various business components) |
Dependent Gradle version | Can be upgraded to the latest official version | 4.4/6.3. It cannot be upgraded by yourself |
Dependent AGP toolchain | Can be upgraded to the latest official version | AGP 3.0.1/3.5.x (cannot be upgraded to other versions by yourself) |
Android Support Library | Usable | The version (23) provided by mPaaS must be used and cannot be upgraded by yourself. |
Android X | Full support | Not support |
databinding | Full support | v1 |
kotlin | Full support | Recommended not to use |
Android Gradle Plugin, a gradle plugin for Android packaging.
With
android.enableJetifier=trueandandroid.useAndroidX=true.