Getting Started

1.1 Initialize mPaaS

If you use the Native AAR connection type, you must initialize mPaaS.

Add the following code to the `Application` class:

public class MyApplication extends Application {
     
    @Override
    public void onCreate() {
        super.onCreate();
        
        MP.init(this,
            MPInitParam.obtain().setCallback(new MPInitParam.MPCallback() {
                @Override
                public void onInit() {
                    // Initialize the mini program public resource package             
                    H5Utils.setProvider(H5AppCenterPresetProvider.class.getName(),new TinyAppCenterPresetProvider());      
                }
            })
        );
    }
 
}

For more information, see Initialize mPaaS.

In the onPostInit method from the code above, the public resource package is configured as follows:

H5Utils.setProvider(H5AppCenterPresetProvider.class.getName(),new TinyAppCenterPresetProvider());

1.2 Configure mini program signature verification

In the assets/config path of your Android project, create a custom_config.json file and add the following content:

[
  {
    "value": "NO",
      "key": "h5_shouldverifyapp"
  }
]

For the value parameter, NO disables miniapp signature verification. YES enables miniapp signature verification. If you do not specify a value, the default is YES. During the development and testing phase, you can disable signature verification for quick integration. Before you publish the application, we recommend that you enable signature verification. For instructions on how to configure signature verification for miniapp packages, see Configure a miniapp package.

Configure the request interval for mini program packages

mPaaS lets you configure the request interval for mini program packages. You can configure this interval globally or for a single package.

• Global settings: You can add the following code to custom_config.json:

  {
  "value": "{\"config\":{\"al\":\"3\",\"pr\":{\"4\":\"86400\",\"common\":\"864000\"},\"ur\":\"1800\",\"fpr\":{\"common\":\"3888000\"}},\"switch\":\"yes\"}",
  "key": "h5_nbmngconfig"
  }

  The \"ur\":\"1800\" parameter sets the global update interval in seconds. The default value is 1800. You can modify this value to set the request interval for all mini program packages. The value can range from 0 to 86400, which corresponds to 0 to 24 hours. A value of 0 indicates that there is no limit on the request interval.

  Important

  Do not change other parameters.

• Individual setting: This setting is configured for a single miniapp package. In the console, go to Add Mini Program Package > Extension Information and enter {"asyncReqRate":"1800"} to set the request interval. For more information, see the Extension Information section in Create Mini Program Package.

To verify that the request interval configuration has taken effect, open a project that has the Mini Program integrated and filter the logcat logs for the H5BaseAppProvider keyword. If you see the following information, the configuration has taken effect.

lastUpdateTime: xxx updateRate: xxx

1.3 Configure AndroidManifest

If you use the Native AAR connection type, add the following configuration to the `AndroidManifest.xml` file:

<application>
    ···
    <meta-data android:name="nebula.android.meta.enable" android:value="true"/>
  ···
</application>

1.4 Apply for the UC kernel

Before you can use a mini program, you must apply for and configure the UC kernel. The UC kernel is required for Android mini program integration. For more information, see the Apply for the UC kernel document.

Using the UC kernel enables same-layer rendering capabilities for mini programs, such as embedding a webview or a map. It also provides a better rendering experience.

2.1 Go to the mini program console

Log on to the mPaaS console. In your target application, navigate to Mini Program > Mini Program Release from the navigation pane on the left.

2.2 Configure a virtual domain name

If this is your first time using the service, you must first configure a virtual domain name in Mini Program > Mini Program Release > Configuration Management. You must use a second-level domain that is managed by your enterprise.

2.3 Create a mini program

In the mPaaS console, perform the following steps:

1. In the navigation pane on the left, click Mini Program > Mini Program Release.

2. On the mini program package list page that appears, click Create.

3. In the Create Mini Program window, enter the mini program ID and name, and then click Submit. The mini program ID is any 16-digit number, such as 2018080616290001.

   

4. In the mini program app list, find the new mini program and click Add.

5. In the Basic Information section, complete the following configurations:

   • Version: Enter the version number of the mini program package, such as 1.0.0.0.

   • Client Scope: Select the minimum and maximum versions of the Android client for the mini program app. Client apps within this version range can start the mini program. Otherwise, the mini program cannot be started. You can set the minimum version to 0.0.0 and leave the maximum version empty. This means that all client versions can start this mini program.

     Note

     Make sure to enter the Android client version, not the mini program version.

   • Icon: Click Select File to upload the icon for the mini program package. You must upload an icon when you create a mini program for the first time. The following is a sample icon:

     

   • File: Upload the mini program package resource file. The file format must be .zip. An mPaaS sample mini program is available for download (click here to download). You can upload it directly.

     Note

     Before you upload, change the .zip file name of this sample mini program and the folder name inside the compressed package to the 16-digit ID of your mini program.

6. In the Configuration Information section, complete the following configurations:

   • Main Entry URL: Required. Specifies the homepage of the miniapp package. The URL must be in the format /index.html#xxx/xxx/xxx/xxx, where the xxx/xxx/xxx/xxx part after the # symbol is the first value in the pages array of the miniapp's app.json file. For example, the main entry URL for the mPaaS sample miniapp is /index.html#page/tabBar/component/index.

   • Keep the default settings for other configurations.

7. Select I have confirmed that the above information is accurate and will not be modified after submission.

8. Click Submit.

   

2.4 Publish the mini program

In the mPaaS console, perform the following steps:

1. In the navigation pane on the left, click Mini Program > Mini Program Release > Official Mini Program Package Management.

2. On the mini program package list page that appears, select the mini program package and version that you want to publish, and then click Create Release.

   

3. In the Create Release Task pane, complete the following configurations:

   • Release Type: Select the Official release type.

   • Release Description: Optional.

4. Click OK to create the release.