All Products
Document Center

Access method introduction

Last Updated: Apr 24, 2022

The mobile development platform mPaaS supports the following three access modes. This topic describes these three modes and provides recommendations for selecting an appropriate access mode.

Native AAR method

Native AAR access mode 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 access mode 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) access mode.


The native AAR access is supported by 10.1.68 or later versions.

mPaaS Inside method

mPaaS Inside access is the transition scheme from component-based access to native ARR access.

When compared with native AAR access, the mPaaS Inside access has the same way using the runtime code layer. The difference is in the packaging scheme. mPaaS Inside access method uses the mPaaS gradle packaging plug-in to perform the dex merge packaging, while the native AAR access method uses the AAR packaging method of the native Android system. If the mPaaS packaging method is not specially necessitated, we recommend that you use the preceding native AAR packaging method.

The use of the mPaaS Inside access requires the using of an mPaaS gradle packaging tool, which has some requirements on the gradle version and version.


mPaaS Inside access is supported by 10.1.60 and later versions.

Component-based access - Portal&Bundle

The component-based access 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 access requires the using of an mPaaS gradle packaging tool, which has some requirements on the gradle version and version.

How to select an access mode

If mPaaS is expected to be easily accessed and used as other SDKs, we recommend that you use native AAR access mode.

The concept of large-scale concurrent development is important for you to reconstruct your project using mPaaS. We recommend that you use component-based mode.

mPaaS Inside is the transition scheme for these two access modes and no longer recommended, unless otherwise specified.