Filament Fcm Driver Laravel Package

Product Decisions This Supports

• Push notification capability for Filament admin users: Enables product teams to ship mobile and web push notifications (transactional alerts, operational notices, user-facing announcements) directly from a Laravel/Filament application without building a custom FCM integration.
• Broadcast vs. targeted notifications: v5.0.0 adds public notifications sent to every user with an FCM token, while single-user mobile notifications are queued again. This supports roadmap decisions around announcements, system-wide alerts, and per-user notifications with different delivery semantics.
• Platform upgrade planning: The v5 line targets Filament v5 and Laravel 12/13, with the Filament v4 line continuing on the v4 branch. Product and engineering can plan upgrades without being forced into an all-or-nothing migration.
• Build vs. buy for notifications: The package covers device token registration, FCM channel integration, service worker generation, queued delivery, and Filament UI actions. Teams can avoid maintaining bespoke notification plumbing and focus on product-specific messaging.
• Security and compliance decisions: Firebase service account keys are now stored on the private local disk, with backward compatibility for older uploads. This reduces the risk of credential exposure and supports security review for production rollout.
• Operational reliability: The restored queueing of single-user mobile notifications on filament-alerts.queue signals that delivery can be handled asynchronously, supporting decisions around queue infrastructure and notification volume.
• Dependency risk management: Allowing laravel-notification-channels/fcm ^5.0 or ^6.0 fixes install failures on locked lcobucci/jwt 4.x projects. This affects whether the package can be adopted in existing applications with constrained dependency trees.

When to Consider This Package

• Consider adoption when:
  • Your product runs on Filament v5 with Laravel 12/13 — or on Filament v4 via the maintained v4 branch — and you need push notifications in the admin or user-facing app.
  • You already use Firebase Cloud Messaging or are prepared to adopt it as the push provider.
  • You want Filament-native notification actions, device token management, and service worker setup without custom code.
  • You need both broadcast notifications to all token-holding users and queued single-user notifications.
  • You value the package handling service worker generation and private key storage, reducing implementation and security overhead.
  • You use tomatophp/filament-alerts ^5.0 on the v5 line; this is a hard requirement for the Filament v5 / Laravel 12/13 path.
• Look elsewhere when:
  • You are not using Filament, or your admin stack is not Filament-based.
  • You need multi-provider push delivery (APNs direct, OneSignal, Pusher Beams, etc.) rather than an FCM-focused driver.
  • You require advanced campaign management, segmentation, A/B testing, or marketing automation beyond user-level and broadcast notifications.
  • You cannot accept a dependency on tomatophp/filament-alerts ^5.0 for the v5 line, or you are locked to Filament v4 and cannot use the v4 branch long-term.
  • You need guaranteed delivery semantics, analytics, or compliance features that the package does not expose.
  • You have no mobile app or web push surface where FCM tokens are relevant.

How to Pitch It (Stakeholders)

• Executive summary: This package gives our Laravel/Filament product a production-ready push notification channel with minimal custom engineering. The v5.0.0 release aligns it with Filament v5 and Laravel 12/13, fixes a dependency install failure, adds broadcast notifications to all users with an FCM token, restores queued single-user notifications, and improves security by storing Firebase service account keys on the private local disk.
• Engineering summary: Adopt on the v5 line for Filament v5 / Laravel 12/13 projects, with tomatophp/filament-alerts ^5.0. Keep Filament v4 projects on the v4 branch. The release resolves lcobucci/jwt 4.x install conflicts, restores push actions on Filament v5, and moves service worker generation into php artisan filament-fcm-driver:install, reducing manual setup.
• Product value:
  • Faster time-to-market for notifications: device tokens, FCM channel, queued delivery, and Filament actions are handled.
  • Broader communication options: broadcast to all token-holding users plus targeted single-user notifications.
  • Lower security risk: private key storage is improved without breaking existing uploads.
  • Smoother upgrades: clear branch strategy for Filament v4 vs. v5 reduces migration risk.
• Risks and mitigations:
  • Dependency coupling: v5 requires filament-alerts ^5.0; plan the upgrade alongside Filament v5 and Laravel 12/13.
  • FCM dependency: The product must use Firebase Cloud Messaging; confirm provider strategy before committing.
  • Queue operations: Queued notifications require a working queue worker; ensure infrastructure is in place before relying on delivery.
  • Version branch discipline: Teams on Filament v4 must stay on the v4 branch and track its maintenance expectations.