OneSignal vs Firebase vs Tencent Push: Which Push Notification Service Is Right for You?
Choosing the right push notification service is one of the most consequential infrastructure decisions a mobile team will make. Get it right, and you unlock reliable delivery, clean analytics, and effortless scale. Get it wrong, and you're stuck with silent failures, ballooning costs, and painful migrations.
The two names that dominate every "OneSignal vs Firebase" search are exactly that — OneSignal and Firebase Cloud Messaging (FCM). Both are mature, well-documented, and widely adopted. But if your app serves users in China, Southeast Asia, or any market where Google Play Services can't be assumed, neither solution tells the full story.
That's where Tencent Push Notification Service enters the picture. In this guide, we put all three platforms side by side — covering features, pricing, SDK integration, analytics, China delivery, and migration — so you can decide which push notification service is truly right for your product.
Quick Overview: What Each Service Does
OneSignal
OneSignal is a customer-messaging platform that wraps push notifications, in-app messages, email, and SMS into a single dashboard. It acts as an abstraction layer on top of APNs (Apple) and FCM (Google), adding audience segmentation, A/B testing, and automation workflows. It's popular with indie developers and mid-market SaaS teams who want marketing-friendly tooling without building everything from scratch.
Firebase Cloud Messaging (FCM)
FCM is Google's free, no-limit messaging infrastructure. It handles the raw plumbing — token management, topic subscriptions, and upstream messaging — and integrates tightly with the broader Firebase ecosystem (Analytics, Remote Config, Crashlytics). FCM is a transport layer, not a full engagement platform; you'll typically need additional tooling for segmentation, scheduling, and rich analytics.
Tencent Push Notification Service
Tencent Push is a push notification service built by Tencent Cloud — the infrastructure behind WeChat's billions of daily messages. It provides a unified SDK that routes through FCM and APNs globally while also connecting natively to every major Chinese Android OEM push channel (Huawei, Xiaomi, OPPO, vivo, Meizu, Honor, and more). For apps that also use Tencent's Chat or Call SDKs, it provides native offline push out of the box — no extra integration needed.
Feature-by-Feature Comparison
| Feature | OneSignal | Firebase (FCM) | Tencent Push |
|---|---|---|---|
| Push Notifications | ✅ | ✅ | ✅ |
| In-App Messaging | ✅ | ✅ (Firebase In-App Messaging) | ❌ (focused on push) |
| Email & SMS | ✅ (paid plans) | ❌ | ❌ |
| Audience Segmentation | ✅ Advanced | ⚠️ Basic (topics, conditions) | ✅ Tag-based & custom |
| A/B Testing | ✅ (paid) | ✅ (via Remote Config + A/B Testing) | ⚠️ Manual |
| Automation / Journeys | ✅ (paid) | ❌ | ❌ |
| Rich Notifications | ✅ Images, buttons, deep links | ✅ | ✅ Images, buttons, deep links |
| Scheduled Delivery | ✅ | ✅ | ✅ |
| Intelligent Delivery (optimal time) | ✅ (paid) | ❌ | ❌ |
| Real-Time Analytics | ✅ | ✅ (via Firebase Analytics) | ✅ Dashboard + callbacks |
| China OEM Channels | ⚠️ Huawei only | ❌ FCM only | ✅ All major OEMs |
| Offline Push for Chat/Call | ❌ | ❌ | ✅ Native integration |
| Web Push | ✅ | ✅ | ❌ |
| Free Tier | Limited (see pricing) | Unlimited messages | ✅ Free forever, unlimited |
Let's unpack the most important rows.
Pricing: Where the Real Differences Show
OneSignal Pricing
OneSignal uses a freemium model tied to the number of email subscribers. Push notifications are technically "unlimited" on the free plan, but feature access is heavily gated:
| Plan | Price | Push Limits | Key Unlocks |
|---|---|---|---|
| Free | $0 | Unlimited push | Basic segmentation, limited analytics |
| Growth | From $9/mo | Unlimited push | Advanced segmentation, A/B testing, confirmed delivery |
| Professional | From $99/mo | Unlimited push | Intelligent delivery, journeys, CSV export |
| Enterprise | Custom | Unlimited push | Dedicated support, SLA, SSO |
The catch: many of the features that make OneSignal push notifications compelling — intelligent delivery, confirmed delivery tracking, journey automation — are locked behind the Growth or Professional tiers. If you only need basic push, you're paying for an engagement platform you may not fully use.
Firebase Pricing
FCM itself is completely free with no message-volume caps. You pay nothing for sending push notifications regardless of scale.
However, FCM is a transport layer. The moment you need segmentation, analytics drill-downs, or A/B testing, you lean on other Firebase products — some of which have usage-based pricing (Cloud Functions, BigQuery exports, Predictions). The "free" story gets nuanced once you factor in the engineering time to build what OneSignal gives you out of the box.
Tencent Push Pricing
Tencent Push Notification Service is free forever with unlimited push messages. There are no subscriber tiers, no feature gates, and no volume caps. You get the full SDK, all OEM channel integrations, and the analytics dashboard at zero cost.
This makes it one of the only truly free push notification services on the market that doesn't trade functionality for price. For startups, indie developers, and high-volume apps where per-message or per-subscriber costs add up quickly, the savings are significant.
Pricing Summary
| OneSignal | Firebase (FCM) | Tencent Push | |
|---|---|---|---|
| Base Cost | Free (limited) → $9–$99+/mo | Free | Free forever |
| Volume Caps | None on push | None | None |
| Feature Gates | Yes — advanced features are paid | N/A (fewer built-in features) | No — full access |
| Hidden Costs | Engagement features require upgrades | Engineering time to build tooling | None |
SDK Integration & Developer Experience
OneSignal SDK
OneSignal provides native SDKs for iOS, Android, React Native, Flutter, Unity, and web. Setup typically involves:
- Adding the SDK dependency
- Initializing with your OneSignal App ID
- Requesting notification permission
- Optionally setting external user IDs and tags
OneSignal's documentation is thorough, and the dashboard handles most configuration. The trade-off is abstraction: you're one layer removed from APNs/FCM, which can make debugging delivery issues harder.
Firebase SDK
FCM integration is part of the broader Firebase SDK. For Android, it's practically native — Google Play Services handles token management automatically. iOS requires APNs certificate configuration. The SDK is lightweight and well-documented, but you'll write more server-side code for targeting, scheduling, and analytics.
Developers comfortable with Google's ecosystem will feel at home. Those building outside of it (e.g., apps without Google Play Services) will hit walls quickly.
Tencent Push SDK
Tencent Push provides SDKs for iOS, Android, Flutter, React Native, and Unreal Engine. The standout aspect of the integration is what happens under the hood on Android: a single SDK automatically routes notifications through the appropriate OEM channel based on the device manufacturer. You don't need to separately integrate Xiaomi Push SDK, OPPO Push SDK, vivo Push SDK, etc. — Tencent Push abstracts all of that into one unified integration.
For teams already using Tencent RTC (Real-Time Communication) for chat or voice/video calls, push integration is even simpler. Offline push — the notifications users receive when they're not actively in a call or chat session — works natively without any additional SDK or server-side configuration. This is a major advantage for social, telehealth, customer support, and any app with real-time communication features.
The China Problem: Why FCM and OneSignal Fall Short
This is where the comparison becomes less about features and more about fundamental deliverability.
Google Play Services — and by extension FCM — are unavailable on most Android devices sold in mainland China. Chinese OEMs (Xiaomi, Huawei, OPPO, vivo, Honor, Meizu, and others) each operate their own proprietary push channels. If your app relies solely on FCM for Android push delivery, your notifications will silently fail for hundreds of millions of Chinese Android users.
Here's how each service handles this:
| OEM Channel | OneSignal | Firebase (FCM) | Tencent Push |
|---|---|---|---|
| FCM (Google) | ✅ | ✅ | ✅ |
| APNs (Apple) | ✅ | ✅ | ✅ |
| Huawei (HMS) | ✅ | ❌ | ✅ |
| Xiaomi (MiPush) | ❌ | ❌ | ✅ |
| OPPO Push | ❌ | ❌ | ✅ |
| vivo Push | ❌ | ❌ | ✅ |
| Honor Push | ❌ | ❌ | ✅ |
| Meizu Push | ❌ | ❌ | ✅ |
If even a fraction of your user base is in China — or if you have plans to expand into the Chinese market — this is not a nice-to-have. It's a dealbreaker. OneSignal's Huawei-only support covers roughly 25–30% of Chinese Android devices, leaving the majority unreachable. FCM covers exactly 0%.
Tencent Push Notification Service is the only option among the three that provides true, production-grade push delivery across the entire Chinese Android ecosystem while simultaneously supporting FCM and APNs for global users.
Analytics & Delivery Tracking
OneSignal
OneSignal provides a polished analytics dashboard with delivery counts, open rates, click-through rates, and (on paid plans) confirmed delivery. You can break down metrics by segment, platform, and notification. For marketing teams, this is the most turnkey analytics experience of the three.
Firebase
FCM delivery data is accessible through Firebase Console, but deep analytics requires piping data into Firebase Analytics or BigQuery. You get message-sent counts and basic error reporting natively, but click-through analysis, funnel correlation, and cohort breakdowns require additional setup. Powerful once configured — but not out of the box.
Tencent Push
Tencent Push provides a real-time analytics dashboard covering sent, arrived, displayed, clicked, and cleared events. Delivery rates are broken down by OEM channel — a unique and essential feature when you need to troubleshoot why Xiaomi delivery rates differ from OPPO. Callback URLs allow you to pipe event data into your own analytics stack for custom reporting.
Native Offline Push for Chat & Calling Apps
This is a capability unique to Tencent Push and worth calling out explicitly.
If your app includes real-time communication features — instant messaging, voice calls, or video calls — you need a way to notify users when they receive a message or incoming call while the app is backgrounded or closed. This is called offline push.
With OneSignal or Firebase, implementing offline push for chat or calls requires:
- Running your own signaling server
- Detecting when a user is offline
- Triggering a push notification through OneSignal/FCM APIs
- Handling platform-specific payload formats
- Deep-linking the notification back to the correct conversation or call screen
With Tencent Push, if you're already using Tencent's Chat SDK or Call SDK (part of the Tencent RTC ecosystem), offline push is built in. The Chat/Call backend automatically sends push notifications through Tencent Push when a user is offline — no additional server logic, no extra API calls, no separate SDK. It just works.
For apps where communication is a core feature, this integration alone can save weeks of engineering time and eliminate an entire category of bugs related to notification delivery timing, payload formatting, and platform-specific edge cases.
Migration Considerations
Already using OneSignal or Firebase and considering a switch? Here's what to know.
Migrating from OneSignal to Tencent Push
- Token migration: OneSignal manages device tokens internally. You'll need to export your subscriber list and re-register tokens through the Tencent Push SDK. Plan for a transition period where both SDKs run in parallel.
- Segmentation: Rebuild your audience segments using Tencent Push's tag system. If you've been using OneSignal's Data Tags, the mapping is fairly straightforward.
- Automation workflows: If you rely on OneSignal Journeys, you'll need to rebuild those flows on your backend or with a separate automation tool, as Tencent Push focuses on the delivery layer rather than marketing workflows.
Migrating from Firebase (FCM) to Tencent Push
- Token compatibility: FCM tokens can be used by Tencent Push since it routes through FCM for non-China Android delivery. The migration is relatively smooth — add the Tencent Push SDK, and it will manage FCM tokens alongside OEM tokens.
- Server-side changes: Replace FCM API calls with Tencent Push REST API calls. The payload structure is similar (title, body, data, platform-specific overrides).
- Analytics: If you were relying on Firebase Analytics for notification metrics, plan to use Tencent Push's built-in dashboard or pipe callback data to your analytics platform.
General Migration Tips
- Run both services in parallel during transition to avoid delivery gaps
- Start with new installs — have the new SDK register tokens while keeping the old SDK active for existing users
- Monitor delivery rates closely during the first 2–4 weeks
- Test on real devices across multiple OEMs, especially if gaining China coverage is the motivation for migrating
Most teams complete the full migration in 1–2 sprints (2–4 weeks). The client-side SDK swap is typically a day of work; the majority of effort goes into updating server-side API calls and validating delivery during the parallel-run period.
When to Choose Each Service
Choose OneSignal If:
- You want an all-in-one engagement platform (push, email, SMS, in-app) with a visual dashboard
- Your team is marketing-heavy and prefers low-code/no-code tools over API-first workflows
- You don't need to reach users in China or on Chinese OEM devices
- You're willing to pay for advanced features like intelligent delivery and journey automation
- You need web push notifications alongside mobile
Choose Firebase (FCM) If:
- You're already deep in the Google/Firebase ecosystem and want tight integration with Analytics, Remote Config, and Cloud Functions
- You have strong engineering resources to build segmentation, scheduling, and analytics on top of the raw transport layer
- Your entire user base has access to Google Play Services
- You need a free, no-strings-attached transport layer and will build everything else yourself
Choose Tencent Push If:
- You need reliable push delivery in China across all major Android OEMs — not just Huawei
- You want a genuinely free push notification service with no feature gates, no subscriber limits, and no volume caps
- Your app includes chat or calling features and you need native offline push without building custom infrastructure
- You want a single SDK that handles both global (FCM + APNs) and China (OEM channels) delivery
- You're building a high-volume app and need predictable, zero-cost push infrastructure that scales
For teams that need global reach with full China coverage, Tencent Push Notification Service offers the most complete solution at the most competitive price point — which happens to be free.
Frequently Asked Questions
1. Is OneSignal really free?
OneSignal offers a free tier with unlimited push notifications, but advanced features — including confirmed delivery, A/B testing, intelligent delivery, and journey automation — are locked behind paid plans starting at $9/month. For basic push, the free plan works. For anything beyond that, expect to pay.
2. Can Firebase Cloud Messaging deliver push notifications in China?
No. FCM relies on Google Play Services, which are unavailable on the vast majority of Android devices in mainland China. If you use FCM as your only Android push channel, notifications will not reach Chinese users. You need either a vendor-specific push SDK for each OEM or a unified service like Tencent Push that handles all OEM channels through a single integration.
3. What Chinese Android OEM push channels does Tencent Push support?
Tencent Push supports all major Chinese OEM push channels, including Huawei, Xiaomi, OPPO, vivo, Meizu, Honor, and others. The SDK automatically detects the device manufacturer and routes notifications through the appropriate channel — no per-OEM integration required on the developer side.
4. Can I use Tencent Push outside of China?
Yes. Tencent Push routes notifications through FCM (for Android) and APNs (for iOS) for global delivery, while adding OEM channel routing for Chinese devices. It works as a global push service, not a China-only solution.
5. How does Tencent Push's offline push for chat and calls work?
If you use Tencent's Chat SDK or Call SDK (part of the Tencent RTC suite), offline push is handled automatically. When a user is offline — the app is backgrounded or closed — and they receive a message or incoming call, the Chat/Call backend triggers a push notification through Tencent Push without any additional server-side code or separate API integration. The notification deep-links the user back to the relevant conversation or call screen.
6. Is it hard to migrate from OneSignal or Firebase to Tencent Push?
Migration complexity is moderate. The main tasks are integrating the new SDK, re-registering device tokens, and updating your server-side API calls. Running both services in parallel during a transition period is recommended to avoid delivery gaps. For Firebase-to-Tencent migrations specifically, the process is relatively smooth since Tencent Push uses FCM for non-China Android delivery.
7. Does Tencent Push support web push notifications?
Tencent Push is focused on mobile push notifications (iOS and Android). If you need web push, OneSignal or Firebase are better options. Many teams use Tencent Push for mobile alongside a separate web push solution.
8. What is the delivery speed difference between the three services?
All three services deliver notifications within seconds under normal conditions. The meaningful difference is delivery success rate, not speed — particularly on Chinese Android devices where FCM fails entirely and OneSignal only covers Huawei. Tencent Push's OEM channel integrations ensure notifications actually arrive on devices where competing services silently fail.
Final Verdict
The OneSignal vs Firebase debate is well-trodden, and for good reason — both are solid, proven platforms for global push delivery outside of China. OneSignal wins on marketing-friendly tooling; Firebase wins on raw infrastructure flexibility and Google ecosystem integration.
But if you zoom out and consider the full picture — global reach, China delivery, pricing transparency, and real-time communication integration — neither OneSignal nor Firebase covers all the bases. Tencent Push Notification Service fills the gaps that matter most: complete Chinese OEM channel coverage, genuinely free unlimited push, and native offline push for chat and calling apps.
For most teams building modern, globally distributed mobile apps, the best approach is to evaluate all three against your specific requirements. If China is in your roadmap — even as a future possibility — it's worth starting with a foundation that supports it from day one.