Mobile Platform as a Service:Overview of integration method

native AAR method

The native AAR integration method uses the standard Android AAR packaging solution. This approach aligns with the common technology stack for Android developers. Developers do not need to learn about mPaaS-specific packaging. You can integrate mPaaS into your project using the mPaaS Android Studio plugin or directly through Maven POM and BOM files. This type lowers the barrier to entry and makes it easier to use mPaaS. It is ideal for developers who want to quickly use mPaaS features and do not need the component-based (Portal & Bundle) integration method.

Component-based method (Portal & Bundle)

The component-based method is a framework based on the Open Service Gateway Initiative (OSGi). It divides an app into one or more independent business Bundle projects and a single Portal project. mPaaS manages the lifecycle and dependencies of each Bundle project. The Portal project then merges all Bundle projects into a single, runnable .apk package. This type is suitable for large-scale projects that require parallel development by multiple teams. To use the component-based method, you must import the mPaaS Gradle packaging tool. This type requires specific versions of Gradle and the com.android.tools.build:gradle plugin.

How to choose a integration method

Use the native AAR method if you want to integrate mPaaS as easily as any other SDK. Use the component-based method if you are using mPaaS to refactor your project for large-scale parallel development.

Comparison of integration methods