Today, the mPaaS plugin is officially available on Jetbrains Market Place!!

It started out as a simple integrated tool and gradually became a peripheral ecosystem centered around the mPaaS SDK. More and more confident to present themselves as “products” to developers.

Download link:

MPaaS for Android Studio is an Android Studio-based plug-in for rapid integration/updating of the mPaaS SDK, while providing a highly interactive entry point for the mPaaS console with developers.

In previous releases, we focused on how we could simplify the cumbersome operations of the early mPaaS, such as connecting the mPaaS SDK as quickly as possible for standardized projects before the AAR functionality was available.

But, we service clients could not have a single standardized development engineering, engineering structure is not the same, the introduction of external SDK and customer business custom SDK is protean, so many born, in mPaaS plug-in after solve the primary problem, need to each case handled one-on-one, both spent a lot of manpower, It lengthens the construction period.

The mPaaS team knows that if they don’t embrace the community and mass-standardize their output, the gap between mPaaS and the average developer will only grow and the problems will only grow.

Plug-ins will never do more than simple up-front work and will never be productized and truly serve the developer. So we made the following two changes:

  • The mPaaS SDK launches a standard AAR access method, which conversions access problems to the scope that can be solved by the community

  • The mPaaS plug-in is developed around the AAR access mode, providing convenient access experience. At the same time, the mPaaS plug-in hosts some functions of the console and connects the IDE to the mPaaS console.

The current mPaaS plug-in version provides the AAR, Inside, and PortalBundle access modes. This low-cost access mode is recommended for public cloud users. Private cloud users will still have three access modes and offer a full range of services.

SDK Component Management

We pull the AAR’s component management page into the “Project Structure” category. The reason is that if we use a GUI to manage Gradle dependencies, Android Studio will also present this panel to developers. This is the natural entry point for component management:

In the future, we will make the component management more hierarchical and provide the concept of “sub-components”, such as the SDK surrounding small programs, so that the hierarchical management is clearer.

Login to mPaaS functionality (under development)

The mPaaS plugin will soon bring the ability to log in to the IDE with the aim of connecting developers to the mPaaS console using Android Studio.

If your App wants to use mPaaS, you need to access the Config file downloaded from the mPaaS console. In the future, you can do it directly in Android Studio, no need to switch between your IDE and browser and do copy-paste and other tedious operations.

You can directly use the “Access mPaaS” wizard in the future to connect the application information created on the mPaaS to your project without any other details

MPaaS access small assistant (under test)

We’ve used the Assistant sidebar in Android Studio to give you a “Step by Step” way to access the SDK.

This step-by-step, unambiguous approach will be our preferred approach in the future, and if you want to integrate a component, you can integrate and code it without even looking at the documentation.

Add a few widgets

Since the current version does not support direct interaction with the mPaaS Ali Cloud Console, we have provided several widgets to help you provide some application/signature information to make it easier for you to access the mPaaS SDK.

  • If you need to upload the signed APK in the console, you can use the “Generate console with signed APK” function to generate a signed APK immediately, you only need to enter your signature information
  • If you need to use the UC kernel function, you can use the Generate UC Key signature information function to generate the information required for applying for UC keys
Note: mPaaS do not store any information about your signature, and the signature information you enter is only used to generate summaries, so you do not need to worry about signature information leakage.

Welcome to use mPaaS, we are on the road of continuous improvement, while providing powerful functions, as much as possible every step for you thoughtful, as much as possible to simplify access work, for you to experience mPaaS SDK to clear all obstacles.

Download the experience now!

Methods a

Search for “mPaaS” in Android Studio Plugin

Method 2

Click the link to download:…

If you have difficulty accessing the network, please refer to:

Obtaining the Offline Version