You can conveniently integrate the function of Mobile Delivery Service to your client by installing the client SDK provided by the Mobile Delivery Service platform.
The process of Mobile Delivery Service is as follows:
Add the corresponding SDK on the client, the capability of integrating Mobile Delivery Service upgrade or H5 offline packages.
Package and generate version upgrade packages, offline packages, etc. in the mPaaS plug-in, and upload them to the release console.
Create a release task on the console for gray release, official release, etc.
The client then pulls the new release package for upgrade and offline release.
In addition, you can use the switch configuration service to modify the client-side code processing logic. By adding the required switch configuration items on the console, targeted distribution can be achieved.
Operation flow
The following diagram shows the process of Mobile Delivery Service release of version upgrade packages and offline packages:
Operations on console
You can perform the following operations on the Mobile Delivery Service console:
Version upgrade packages > Manage releases: Manage and release the configuration of new client version.
Offline packages > Manage offline packages: Package different businesses into different offline packages, and deliver the offline packages through the Mobile Delivery Service platform to update the client-side resources.
Switch configuration > Manage configurations: Configure, modify or push various switches. You can deliver the packages by platform, whitelist, percentage or other condition.
Manage whitelists: Manage whitelists so that you can easily create hundreds of thousands of whitelist data for the use in Mobile Delivery Service.
Manage release rules: Pedefine various configuration data required for Mobile Delivery Service so that you don’t have to manually input the data every time, with work efficiency improved and error rate decreased.