JPush
JPush is a China mobile push notification service from Jiguang.
China context: JPush provides a China-market alternative to Firebase Cloud Messaging for mobile push notifications.
Global service map
Does Firebase Cloud Messaging work in China?
. Regenerated with each Chinaready Landscape publish.
Quick answer: Firebase Cloud Messaging (FCM) does not work in mainland China. Two things break it at once: the Google-hosted FCM endpoints are blocked from mainland networks, and mainland Android phones ship without Google Play Services, which FCM needs on the device to receive a push. iOS is the exception — an FCM-to-APNs path can still reach mainland iPhones. For Android coverage, map to a domestic push provider that aggregates the Chinese OEM channels: JPush, Alibaba Cloud Mobile Push, Getui. Availability in China: Unavailable.
Availability in China: Unavailable
Also searched as: fcm.
Replacing FCM for mainland China push notifications
Why FCM fails in mainland China
Teams usually discover this when China Android installs simply stop receiving notifications while the same build works everywhere else. There are two independent causes, and fixing only one does not help.
- Blocked transport. FCM's registration and delivery endpoints sit on Google infrastructure that is not reliably reachable from mainland networks.
- Missing device runtime. FCM delivery on Android depends on Google Play Services holding a persistent connection. Mainland-market phones from Xiaomi, OPPO, vivo, Honor, and Huawei ship without Google Play Services, so there is nothing on the device to receive the message even if the network allowed it.
Chinaready's Firebase measurements from a mainland China node show FCM among the core Firebase services that are blocked or otherwise inaccessible. Treat FCM as unavailable for mainland Android rather than degraded.
iOS is a real exception
Mainland iPhones still reach the Apple Push Notification service, so a push that travels FCM → APNs → iPhone can work. This matters for iOS-heavy products, but it does not rescue Android. If you keep FCM for iOS, be explicit that your China Android audience is uncovered until you add a domestic provider.
How domestic push providers solve it
Mainland push is not one connection — it is a fan-out across each handset maker's own channel (Huawei HMS Push, Xiaomi, OPPO, vivo, Honor), plus a self-maintained socket as a fallback. Domestic providers exist mainly to aggregate those channels behind a single API so you do not integrate five vendor SDKs yourself. Using the OEM channel is also what gets a notification through aggressive background-process killing, which is the other common reason mainland notifications silently disappear.
| Provider | Characteristics | Best fit |
|---|---|---|
| JPush (极光推送) | Long-established independent China push platform with OEM channel aggregation, rich SDK coverage, and REST APIs familiar to teams migrating off FCM | Default first evaluation for most FCM migrations |
| Alibaba Cloud Mobile Push (阿里云移动推送) | Managed push within the Alibaba Cloud console, with OEM channel support and the usual cloud IAM, logging, and billing integration | Stacks already running on Alibaba Cloud |
| Getui (个推) | Independent provider with OEM channel aggregation and delivery analytics; commonly benchmarked against JPush | Teams comparing two independent vendors before committing |
| Umeng U-Push (友盟+ U-Push) | Push inside the Umeng+ mobile growth suite, so push sits alongside analytics and audience segmentation | Products already using Umeng+ for China analytics |
What the migration actually involves
This is not a credentials swap. Expect to plan for:
- Per-OEM registration. Each handset maker's push channel needs its own developer account and app registration before delivery rates improve.
- A second device token space. Your backend needs to store and route domestic push tokens separately from FCM tokens, usually keyed by build or by user region.
- A build or runtime split. Most teams ship a China build with the domestic SDK and keep FCM elsewhere, rather than bundling both into one global binary.
- Notification-permission behaviour. Mainland Android permission prompts and background restrictions differ by OEM, so measured delivery rates matter more than documented ones.
If FCM is one of several Firebase services in your stack, review the whole suite rather than only push — Authentication, Firestore, Storage, Functions, and Remote Config have the same mainland problem, and the Firebase pages linked below cover each one.
Candidates on this page are alternatives-page orientation options for research. Confirm SDK platform coverage, delivery-rate reporting, data-handling terms, and pricing before production adoption.
Firebase Cloud Messaging alternatives in China
Mapped Chinaready candidates
Alibaba Cloud Mobile Push
Alibaba Cloud Mobile Push (EMAS) is Alibaba Cloud's native push notification service for Android, iOS, and HarmonyOS. It integrates major Chinese Android vendor channels and is designed for high delivery rates within mainland China.
China context: Native Alibaba Cloud / EMAS push for China apps. Integrates Huawei, Xiaomi, OPPO, vivo, Honor and other OEM channels, works without Google Play Services, and offers a REST API suited to enterprise stacks already on Alibaba Cloud. For global apps it is commonly paired with APNs and FCM overseas; this product primarily focuses on mainland delivery.
Getui
Getui (个推) is one of China's largest independent mobile push notification providers. It aggregates manufacturer push channels across Huawei, Xiaomi, OPPO, vivo, Honor, and other Android vendors to maximize delivery rates and is widely adopted by Chinese consumer apps.
China context: Independent China push SaaS widely used by consumer apps. Aggregates OEM push channels for high mainland delivery, with Android and iOS support plus user segmentation, scheduled push, and analytics. Strong fit for consumer apps, e-commerce, news, and content platforms replacing OneSignal or FCM in China.
Umeng U-Push
Umeng U-Push is Alibaba-backed mobile push infrastructure integrated with the Umeng analytics ecosystem. Besides notification delivery, it provides user segmentation, analytics, and marketing automation features, and supports manufacturer push channels on Android.
China context: Alibaba-backed push module in the Umeng ecosystem. Supports Android OEM channels plus Android, iOS, and HarmonyOS, with segmentation, scheduled campaigns, analytics integration, and marketing automation. Good fit for marketing/growth teams and apps already using Umeng Analytics when replacing OneSignal or FCM in China.
Related lookups
FAQ
Does Firebase Cloud Messaging work in China?
No for mainland Android. Chinaready labels Firebase Cloud Messaging as Unavailable for mainland China. The Google-hosted FCM endpoints are not reliably reachable from mainland networks, and mainland-market Android phones ship without Google Play Services, which FCM requires on the device to receive a push. Mainland iPhones can still be reached through the FCM-to-APNs path, so iOS is a partial exception.
Why do FCM push notifications not arrive on Chinese Android phones?
Two independent reasons, and fixing one does not help. First, FCM's registration and delivery endpoints sit on Google infrastructure that is blocked from mainland networks. Second, FCM delivery on Android depends on Google Play Services maintaining a persistent connection, and mainland-market phones from Xiaomi, OPPO, vivo, Honor, and Huawei ship without it. Aggressive OEM background-process killing then removes any remaining fallback path.
What are the best China alternatives to Firebase Cloud Messaging?
Chinaready Landscape currently maps Firebase Cloud Messaging to JPush, Alibaba Cloud Mobile Push, Getui, Umeng U-Push. These providers aggregate the Chinese OEM push channels (Huawei HMS Push, Xiaomi, OPPO, vivo, Honor) behind one API, which is what gets a notification delivered on a device with no Google Play Services. Replacement fit varies by product, so treat this as a research shortlist rather than a one-to-one endorsement.
Can I keep FCM for iOS and use a China provider only for Android?
Yes, and many teams do. Mainland iPhones still reach the Apple Push Notification service, so an FCM-to-APNs path can work for iOS while a domestic provider covers China Android. Your backend then needs to store and route two token spaces, usually keyed by build or user region.
Is migrating from FCM to a China push provider just a credentials change?
No. Plan for per-OEM developer accounts and app registrations, a second device token space in your backend, and usually a separate China build carrying the domestic SDK rather than one global binary. Measured delivery rates on real mainland devices matter more than documented ones, because OEM permission prompts and background restrictions differ.
Where should teams go after shortlisting FCM alternatives?
Review the rest of the Firebase suite in the same pass, since Authentication, Firestore, Storage, Functions, and Remote Config have the same mainland problem. Compare the OneSignal and AWS SNS pages if your push layer sits behind an aggregator, then use the Push Notifications & Multichannel Messaging section of the Chinaready Guide for where this fits in a China stack. If the path remains unclear, book a call with Chinaready.