Notifire + FCM with Laravel

If you want to send Push Notifications from your Laravel app to mobile or web clients, the fastest and simplest way is to use Notifire. It integrates Laravel directly with Firebase Cloud Messaging (FCM), so you can keep working inside Laravel’s native Notifications system without reinventing the wheel.

What is Notifire and why use it?

Notifire is a Laravel package built to connect with FCM. You can send notifications with simple or advanced payloads (title, body, image, icon, sound, actions…). It also helps you manage device tokens efficiently, making token registration and storage in your database much easier.

Requirements

Before starting, make sure you have: - An active Firebase Project. - The Service Account JSON file stored securely (e.g., storage/firebase.json). - Laravel Sanctum configured, since token registration endpoints are tied to it.

Installation Steps

Installation takes only 3 commands:

composer require devkandil/notifire
php artisan vendor:publish --provider="DevKandil\NotiFire\FcmServiceProvider"
php artisan migrate

Managing Tokens

The package provides a ready-to-use Trait you can add to your User model for FCM token management. This is essential since every notification needs to target a specific device token. For multi-device users, it’s better to create a dedicated devices table instead of storing a single token on the users table.

Registering Tokens from Frontend

Notifire provides a ready endpoint POST /fcm/token, which is protected by Sanctum. Any device (web or mobile) generates a token from Firebase and sends it to your backend to store and associate with the authenticated user.

Sending Notifications

You can either use the Facade directly or integrate with Laravel’s native Notification system. Both ways let you add title, body, image, extra data, and even set priority.

$ok = Fcm::withTitle('New Alert')
    ->withBody('There is an update on your account')
    ->sendNotification($token);

Best Practices

- Always send notifications through queues to avoid UI latency.
- Store Firebase credentials securely, never commit them to Git.
- Rotate invalid tokens or clear them after user logout.
- Use FCM Topics when you need to broadcast to large user segments.

Common Issues

- Notifications not delivered: check Service Worker setup on web or re-register the token.
- 401/403 on /fcm/token: usually Sanctum misconfiguration or missing token.
- Slow delivery: use Queue Workers and separate notification sending from the main request cycle.

Conclusion

Notifire makes Laravel + FCM integration straightforward and organized. Once you set up token management and use queues properly, you’ll have a reliable and scalable Push Notification system for both mobile and web applications.