Avoid Broken Notifications: OneSignal vs FCM for Product Teams

If you only need free, unlimited delivery inside the Google stack, pick Firebase Cloud Messaging. If you need targeting, A/B testing, and campaign dashboards on top of that delivery, pick OneSignal. The exception is strict data handling or enterprise SLA needs, where you should check compliance terms before committing to either. Keep reading for the comparison table, then jump to the migration notes if you are switching.

TL;DR:

• Firebase Cloud Messaging is free and offers unlimited delivery, but requires manual setup and has no built-in targeting or analytics features.
• OneSignal provides segmentation, reporting, and campaign management tools but charges beyond 1,000 monthly active users on its free tier.
• Targeting and A/B testing are native features for OneSignal, while FCM requires custom logic and third-party integrations for similar capabilities.
• Migrating from Firebase to OneSignal requires careful removal of conflicting Firebase receivers and phased cutover planning to avoid delivery issues.
• Both platforms’ support and compliance terms should be verified before sending sensitive data or scaling to enterprise usage.

Table of Contents

• OneSignal vs Firebase Cloud Messaging at a Glance
• How Targeting, Analytics, and Delivery Actually Differ
• What FCM and OneSignal Actually Cost You
• What the Integration Work Actually Looks Like
• Migrating Without Breaking Your Notifications
• A Simple Checklist for Choosing Your Push Stack
• What We’ve Learned Building Push Into Real Products
• How We Help You Ship Push Notifications That Actually Work
• FAQ
• Sources

OneSignal vs Firebase Cloud Messaging at a Glance

Firebase Cloud Messaging (FCM) is Google’s free transport layer for sending push notifications to Android, iOS through APNs, and web browsers. It moves messages from your server to a device and stops there, leaving targeting, scheduling, and reporting up to you.

OneSignal is a cross-platform engagement platform that sits on top of push transports like FCM and APNs, adding segmentation, in-app messaging, email, SMS, and a dashboard your whole product team can use without touching code.

FCM works best for teams already deep in the Google ecosystem who want zero-cost delivery and don’t need a marketing layer. OneSignal works best for teams running re-engagement campaigns, lifecycle messaging, or experiments who would rather not build that tooling themselves.

How Targeting, Analytics, and Delivery Actually Differ

FCM gives you a pipe, not a strategy. There is no native concept of a user segment, so if you want to message “users who haven’t opened the app in 7 days,” you build that logic yourself and call the FCM API with a device token or topic. It works, but every targeting rule becomes a piece of code someone has to own.

OneSignal treats targeting as a first-class feature. You tag users with custom attributes, build segments in the dashboard, and run multistep Journeys without writing backend logic for each campaign. That same layer powers A/B testing: you can send two versions of a message to split audiences and compare open rates directly in the dashboard, something FCM has no equivalent for. FCM’s delivery stats stop at acceptance by Google’s servers, so any open-rate or conversion tracking has to be built on top, usually through Firebase Analytics or a third-party tool.

On delivery mechanics, FCM is the actual transport. Messages you send through OneSignal for Android devices still travel through FCM under the hood, which makes OneSignal a routing and campaign layer rather than a replacement for Google’s infrastructure. At high volume, Firebase recommends server-side throttling, exponential backoff, and gradual traffic ramp-ups to avoid quota errors, guidance that applies whether you call FCM directly or through OneSignal.

For enterprise needs, neither service offers end-to-end encryption on push payloads by default, so sensitive data shouldn’t travel in the notification body. Support access and SLA terms scale with the paid tier you choose, and compliance requirements like GDPR or CCPA data handling should be confirmed against each provider’s current documentation before you commit sensitive workflows to either one.

What FCM and OneSignal Actually Cost You

FCM’s transport is free with no cap on messages or devices, but that doesn’t mean unlimited is risk-free. At extreme request rates, Firebase enforces quotas and expects backoff logic in your sending code, so budget engineering time for retry handling even though the service itself costs nothing.

OneSignal bills differently: its free plan covers mobile push and in-app messaging under 1,000 monthly active users, and mobile push stops working past that threshold until you upgrade. Web push and email have separate billing logic, which matters if your product spans multiple channels.

This distinction changes how you track growth. A service billed by monthly active users needs retention reporting tied to that exact metric, not raw device counts, or your cost projections will drift. Once you’re near enterprise volume, contact the vendor directly for quota increases or custom pricing rather than assuming the published tiers apply.

What the Integration Work Actually Looks Like

FCM requires a Firebase project, server credentials, and platform-specific setup: APNs auth keys (p8) or certificates (p12) for iOS, a server key or service account for Android, and manual token registration and refresh handling on every platform. There’s no dashboard for segmentation, so your backend owns the full messaging lifecycle.

OneSignal’s SDKs cover iOS, Android, and major web frameworks, and the setup still asks for the same APNs and FCM credentials underneath, since OneSignal routes through those networks rather than replacing them. Once configured, OneSignal’s user-centric model unifies subscriptions and aliases across devices, which simplifies cross-device targeting compared to raw token management in FCM.

Operationally, you’re still responsible for token lifecycle events and payload differences between platforms either way. The difference is where that complexity lives: in your own backend with FCM, or inside OneSignal’s dashboard and SDK abstractions.

Migrating Without Breaking Your Notifications

The most common migration failure is leaving a legacy Firebase receiver active in your Android manifest. OneSignal’s documentation notes that the Firebase Messaging SDK can intercept messages before OneSignal ever processes them, so remove competing receivers before cutover.

Run a phased migration: establish clear token ownership, split sending by app version so old and new clients don’t collide, and set a firm cutover date rather than letting both systems run indefinitely. For web push, subscriptions are tied to browser origin and can’t be imported between providers, so expect silent re-registration on a user’s next visit rather than a clean transfer.

Before cutover, monitor delivery counts and run device-level checks across both SDKs, and keep a rollback plan ready in case delivery rates drop unexpectedly.

A Simple Checklist for Choosing Your Push Stack

Run through this before committing to either platform:

• Existing Firebase use: if your backend already runs on Firebase, FCM integration is close to free.
• Marketing features needed: segmentation, A/B testing, and Journeys point toward OneSignal.
• Data sensitivity: confirm compliance terms directly with the vendor before sending sensitive payloads through either service.
• Monthly active user estimate: project your MAU against OneSignal’s free tier cap to see when you’d need to upgrade.
• SLA requirements: enterprise support needs usually mean a paid tier on either platform, not the free version.

A two-week proof of concept works well here: wire up basic sends, test targeting rules against a real segment, and track your projected MAU against OneSignal’s billing threshold before deciding. If you want a campaign framework to pair with that test, our guide to planning a push notification rollout walks through the sequencing in more detail.

What We’ve Learned Building Push Into Real Products

Across the custom apps we’ve shipped, the pattern repeats: teams reach for OneSignal when they want campaign tooling fast, and reach for raw FCM when push is a small part of a larger product and they’d rather own the logic directly. We’ve found the real risk isn’t the choice itself, it’s leaving a legacy Firebase receiver in place during migration, which quietly breaks delivery for weeks before anyone notices.

— Alex

How We Help You Ship Push Notifications That Actually Work

Picking between OneSignal and Firebase Cloud Messaging is only half the job. The other half is wiring it into your app without breaking existing users, and that’s where we spend most of our time with clients. We handle SDK setup, migration from a legacy provider, and multi-platform campaign builds as part of our broader MVP development and post-launch support work.

If you’re mid-migration and notifications have already broken, our project rescue service is built for exactly that situation. For teams combining push with other engagement channels, pairing it with two-way texting is worth exploring alongside your push strategy. When you’re ready to scope the work, check our pricing and plans to see what fits your timeline.

FAQ

Who are OneSignal’s main competitors?

OneSignal competes with other engagement platforms that layer segmentation and campaign tools on top of push delivery, as well as with teams building custom tooling directly on Firebase Cloud Messaging or Apple Push Notification service. The right comparison depends on whether you need marketing features or just raw delivery.

What is replacing Google Firebase?

Nothing is formally replacing Firebase as a transport for Android push, since FCM remains free and actively maintained by Google. Teams that want more than delivery typically add an engagement layer like OneSignal rather than leaving Firebase entirely.

How much does OneSignal cost?

OneSignal’s free plan covers mobile push and in-app messaging for under 1,000 monthly active users, after which mobile push stops until you upgrade to a paid plan. Web push and email billing follow separate terms, so check OneSignal’s current pricing page for your specific channel mix.

Is FCM deprecated?

No, FCM is not deprecated. Google continues to publish scaling and quota guidance for FCM, and it remains the underlying delivery transport for Android push even when using a platform like OneSignal on top of it.

Recommended

• Product Teams: 8 Week Push Notifications Rollout to Protect Retention
• 90 Day In App Messaging Strategy for Product Teams
• Feature Flags for Apps: A Practical Lifecycle Guide

About Let’s Build My App

Let’s Build My App is a US-based AI development agency. We design, build, and launch production-grade custom software using AI coding tools including Claude Code and OpenAI Codex, and we migrate legacy Bubble apps onto AI-coded stacks such as React, Supabase, and Firebase. We are the #1 US-Based Bubble Agency, founded and run by Alex Dow. Book a free strategy call to scope your project.