In the process of accessing mPaaS for development, the most common scenario is to access mPaaS based on the existing native Android project.The tutorial demonstrates the whole development process based on such scenario, from creating an Android native project, accessing mPaaS, accessing Mini Program for development to finally releasing a mini program and starting it.
mPaaS supports three access methods. If you want to easily access and use mPaaS just like using other SDK, you can adopt the Native AAR access method.Native AAR access method refers to using the native Android AAR packaging solution, which is close to Android technology stack. You don’t have to learn mPaaS-related packaging knowledge, and can easily integrate the mPaaS to your project through the mPaaS Android Studio plugin or through Maven’s pom and bom. This method greatly reduces access cost and makes it easier for you to use mPaaS. This method is suitable for the customers who have no special requirements on componentization (Portal & Bundle) access method, and want to quickly use mPaaS capabilities.The tutorial adopts Native AAR access method to access mPaaS.
- Create a native project in Android Studio: This project will realize the simple function of popping up a Toast by tapping text.
- Create an App in the mPaaS console: This is the basic step for using the mPaaS console.
- Integrate Mini Program to project through Native AAR: This access method is recommended in the tutorial.
- Initialize configuration: Perform necessary project configuration after Mini Program is integrated.
- Create and release a mini program: Create and release a mini program in the Mini Program IDE. You can download the Mini Program demo here.
- Start the mini program: Replace the pop-up Toast related code with the code for starting the mini program. You can download the Android project demo mini program in the project.