Firebase Cloud Messaging

Firebase Cloud Messaging (FCM) is Google's cross-platform push-notification and messaging service, part of the broader Firebase/Google Cloud platform. It delivers notification messages and data messages (up to 4096 bytes) to iOS, Android, and web clients, and is the de-facto default transport for Android push because it sits on top of Google Play Services. Targeting works three ways, by individual registration token, by device group, or by topic subscription (with boolean topic conditions of up to five topics). It is fully free with no per-message charges or message-count caps on both the Spark and Blaze plans, which makes it the baseline choice for startups, indie developers, and any team that already lives inside the Google/Firebase ecosystem.

Where FCM wins is reach, price, and ecosystem gravity: zero cost at any scale, tight integration with Google Analytics (notification funnel analysis, conversion tracking), A/B testing of notification variants, BigQuery export for delivery data, and first-party Admin SDKs across Node, Java, Python, Go and C# plus a clean HTTP v1 REST API. Where it loses is the engagement layer. FCM is plumbing, not a marketing suite, the console composer and dashboard are widely criticized as thin, there is no built-in segmentation/journey tooling, and rich features that competitors like OneSignal bundle (advanced segmentation, in-app, email/SMS orchestration) are absent. Delivery is best-effort: the docs make no uptime/SLA promise for FCM specifically, the default project quota is 600k messages/minute (429 RESOURCE_EXHAUSTED above that), and developers regularly report delayed or dropped notifications, especially on iOS (where APNs limits apply) and on Android devices with aggressive battery/Doze optimization.

Net: FCM is the right default if you want free, reliable-enough, broadly-supported push and are willing to build your own segmentation and analytics on top, or pair it with a higher-level CEP. It is the wrong choice if you want turnkey lifecycle messaging out of the box, or need contractual delivery-latency guarantees. Most teams either use it raw for transactional/data pushes or wrap it inside a managed engagement platform that uses FCM as the underlying delivery channel.