- About this article
- Conclusion first
- Positioning within Google
- Who is affected?
- Cautions for Web Push
- How does it compare to Microsoft / Azure?
- Safe Testing
- Official Google Resources
- What should you do next?
- Deep Dive into Specific Primary Information
- Papanda TRY: Visualizing Push Notification Paths with Animation
- What kind of service is it overall?
About this article
This article was created using an automated generation workflow powered by generative AI.
Firebase Cloud Messaging (FCM) is a cross-platform service for sending messages to apps on Android, Apple platforms, and the Web. It can be used not only for notifications displayed to users, but also for data messages processed by the app.
Information verification reference date: 2026-09-19
Conclusion first
FCM is a mechanism where messages are sent from a trusted server environment and received by the Firebase SDK on the device. It supports targeting to a single device, groups, or topics, and can be used to drive re-engagement via notifications or as a trigger for data synchronization.
| Component | Role |
|---|---|
| Client app | Receives messages via the FCM SDK and acquires registration tokens, etc. |
| Trusted server | Sends messages using the Admin SDK or FCM HTTP v1 API |
| Notification message | A format that allows the OS/SDK to easily handle notification display |
| Data message | Processes the payload within the app code |
| Topic | Delivers messages to multiple devices subscribed to a specific topic |
flowchart LR Server[信頼できるServer] -->|Admin SDK / HTTP v1| FCM[Firebase Cloud Messaging] FCM --> Android[Android] FCM --> Apple[Apple platform] FCM --> Web[Web Push] App[Client app] -->|registration| FCM
Positioning within Google
Firebase is responsible for delivering notifications and messages to apps. Authentication handles user verification, Firestore/Realtime Database handles data storage, and FCM handles delivery to devices. Transmission processing can be executed from trusted environments such as Cloud Run or Cloud Functions.
Who is affected?
General Users and Administrative Staff: Experienced as new arrival or update notifications in apps. Notification permissions and opting out are also directly tied to the user experience.
IT Administrators: Responsible for checking Firebase Projects, sending permissions, credentials, auditing, and the handling of payloads containing personally identifiable information.
Developers: Implement SDKs, registration tokens, topics, foreground/background processing, and Admin SDK/HTTP v1.
Cautions for Web Push
Web push requires a browser capable of using the Push API and HTTPS. VAPID keys are also involved in FCM Web configuration. It is crucial not to store private keys in client code or public repositories.
How does it compare to Microsoft / Azure?
It can be compared with services like Azure Notification Hubs regarding the objective of delivering push notifications to multiple platforms. However, FCM features deep integration with the Firebase ecosystem including Android, while Apple and Web implementations rely on platform-specific mechanisms. It is easier to understand when compared across three layers: sending servers, delivery services, and clients.
Safe Testing
Follow the official Getting Started guide using a verification project and a test device, and send a notification to a single test device from the Firebase Console or a trusted server. The success condition is that the test notification arrives only on the target device. Change only one location first, which is the notification body text.
Ensure that registration tokens and server credentials are not posted in articles, logs, or public GitHub repositories. Do not include unnecessary personal or sensitive information in notification payloads.
Official Google Resources
What should you do next?
First, select one target platform and perform a single send and receive operation using a verification project and a test device. Next, review token management, topic design, notification permissions, server-side authentication, and delivery failure handling.
Deep Dive into Specific Primary Information
Firebase Cloud Messaging (FCM) is a mechanism for sending notifications and data messages to apps. The sender makes a request from a trusted server environment to the FCM backend, and the client-side app receives the message. It is also important to maintain operational practices where registration tokens are not stored in public logs or Git.
Google Official Primary Information
Papanda TRY: Visualizing Push Notification Paths with Animation
We will create an HTML instructional tool where a fictional message moves across three points: App server -> FCM -> device. Without using actual device tokens or notification sending credentials, it also displays that tokens are data requiring confidentiality and privacy considerations.
What kind of service is it overall?
Firebase Cloud Messaging is a Firebase messaging service that delivers notifications and data messages from a server to client apps on Android, Apple, the Web, and other platforms. Beginners can think of it as a 'delivery network for sending new updates to apps,' which makes it easier to understand by dividing it into three components: the sending server, FCM, and the client.
