Some components and services in Mobile PaaS (mPaaS) rely on features from third-party services. When you use these mPaaS components, they must authenticate with or request data from these third-party services. This topic describes these dependencies for each platform.
Android
UC kernel
The UC kernel verifies the UCKEY, which requires authentication with a third-party service.
UC Crash
If you do not use the UC kernel but integrate the UC Crash SDK separately, it also reports data to a third-party service.
Location-based service (LBS)
The mPaaS LBS component uses location services from AMAP. When you use the LBS service, it must request data from AMAP servers.
Mini Program
The map and location features in the miniapp service use location services from AMAP. When you use these miniapp features, they must request data from AMAP servers.
Social sharing
The mPaaS social sharing component lets you share content through channels such as Weibo, WeChat, Alipay, QQ, text message, and DingTalk. This feature relies on third-party sharing SDKs. If a third-party sharing SDK requests data from its server, the mPaaS sharing component also makes that data request.
The following table lists the third-party sharing SDKs that the mPaaS social sharing component supports.
Third-party SDK | SDK description | Application scenario |
WeChat Sharing SDK | WeChat Share and Favorites lets users of a third-party app share text, images, music, videos, web pages, and miniapps to WeChat chats, Moments, or save them to WeChat Favorites. | Share content from your app to the WeChat client. |
QQ Sharing SDK | An interface for sharing messages to QQ. It supports sharing news, images, text, and applications with QQ friends or Qzone. | Share content from your app to the QQ client. |
Alipay Sharing SDK | Alipay Share lets users of a third-party app share images and web pages to Alipay. | Share content from your app to the Alipay client. |
Weibo Sharing SDK | Share content to Weibo. | Share content from your app to the Weibo client. |
DingTalk Sharing SDK | Share content to DingTalk. | Share content from your app to the DingTalk client. |
Message push
To improve push notification delivery rates, mPaaS integrates the push SDKs from Huawei, Xiaomi, OPPO, and vivo, which connect to the push services of these vendors. The Huawei and Xiaomi SDKs are integrated into the mPaaS framework. You must integrate the OPPO and vivo push SDKs separately.
The following table lists the third-party push SDKs that the mPaaS message push component supports.
Third-party SDK | SDK description | Application scenario |
Huawei Push SDK | Huawei Push Kit delivers real-time messages to user devices. This helps build good user relationships and improves user awareness and engagement. | Push messages to Huawei mobile phones. |
Xiaomi Push SDK | Xiaomi Push is a system-level channel on MIUI and is compatible with all platforms. It provides a stable, reliable, and efficient push service. | Push messages to Xiaomi mobile phones. |
OPPO Push SDK | The OPPO Push SDK establishes a stable and reliable persistent connection between the server and the operating system to push real-time messages to app clients on OPPO's ColorOS. The push service helps developers improve app engagement and retention, and enhances the product experience. | Push messages to OPPO mobile phones. |
vivo Push SDK | vivo Push is a message push service for developers. It establishes a stable and reliable persistent connection between the cloud and the client to deliver real-time messages to applications. It supports billions of notifications and messages, reaching mobile users in seconds. | Push messages to vivo mobile phones. |
iOS
Mini Program
The map and location features in the miniapp service use location services from AMAP. When you use these miniapp features, they must request data from AMAP servers.
Location-based service (LBS)
The mPaaS LBS component uses location services from AMAP. When you use the LBS service, it must request data from AMAP servers.
Social sharing
The mPaaS social sharing component lets you share content through channels such as Weibo, WeChat, Alipay, QQ, text message, and DingTalk. This feature relies on third-party sharing SDKs. If a third-party sharing SDK requests data from its server, the mPaaS sharing component also makes that data request.
The following table lists the third-party sharing SDKs that the mPaaS social sharing component supports.
Third-party SDK | SDK description | Application scenario |
WeChat Sharing SDK | WeChat Share and Favorites lets users of a third-party app share text, images, music, videos, web pages, and miniapps to WeChat chats, Moments, or save them to WeChat Favorites. | Share content from your app to the WeChat client. |
QQ Sharing SDK | An interface for sharing messages to QQ. It supports sharing news, images, text, and applications with QQ friends or Qzone. | Share content from your app to the QQ client. |
Alipay Sharing SDK | Alipay Share lets users of a third-party app share images and web pages to Alipay. | Share content from your app to the Alipay client. |
Weibo Sharing SDK | Share content to Weibo. | Share content from your app to the Weibo client. |
DingTalk Sharing SDK | Share content to DingTalk. | Share content from your app to the DingTalk client. |
Conflict-free version of the Express Payment component from Alipay Open Platform
mPaaS provides conflict-free versions of some components from the Alipay Open Platform. If the original component requests data from a third-party server, the mPaaS conflict-free version also makes that request.