Notify Bundle Laravel Package

Product Decisions This Supports

• Real-time notifications infrastructure: Enables push notifications (e.g., WebSocket-based alerts) alongside email/SMS via Mercure, reducing reliance on third-party services like Firebase or Pusher.
• Unified notification system: Consolidates disparate notification channels (push, email, etc.) under a single Laravel bundle, simplifying maintenance and reducing technical debt.
• Cost optimization: Avoids per-user fees from SaaS notification providers by leveraging open-source Mercure (Symfony’s real-time protocol).
• Roadmap alignment: Ideal for projects prioritizing real-time features (e.g., live dashboards, collaborative tools) or offline-capable notifications (e.g., mobile apps).
• Build vs. buy: Justifies buying this over custom development if the team lacks Mercure expertise or needs rapid integration with existing Laravel apps.

When to Consider This Package

• Avoid if:
  • Your app requires high-scale push notifications (Mercure’s default pub/sub may not match Firebase/Pusher’s reliability).
  • You need native mobile push (APNS/FCM) or SMS gateways (this bundle focuses on web/email).
  • Your team lacks Symfony/Laravel familiarity (setup requires Mercure bundle + JWT configuration).
  • You’re already using a mature notification service (e.g., Laravel Echo + Pusher) with no plans to migrate.
• Consider if:
  • You’re building a web-first app (e.g., SaaS, admin panels) needing real-time updates.
  • Your stack is Laravel + Symfony components (Mercure integration is seamless).
  • You want to reduce vendor lock-in by self-hosting notifications.

How to Pitch It (Stakeholders)

For Executives: "This bundle lets us add real-time notifications (like live alerts or updates) to our Laravel app without third-party fees. By using Mercure—a lightweight, open-source protocol—we avoid per-user costs from services like Pusher. It’s a drop-in solution that works with our existing email system, cutting dev time and future-proofing our stack. Low risk: MIT-licensed, actively maintained, and backed by Symfony’s ecosystem."

For Engineering: *"The austral/notify-bundle gives us:

• Mercure-powered push notifications (no WebSocket server setup needed—Symfony handles it).
• Unified config for push/email/SMS (via austral/email-bundle).
• Lightweight: ~500 LOC, no heavy dependencies. Tradeoff: Mercure isn’t as battle-tested as Pusher for global scale, but it’s perfect for our internal tools. Docs are sparse, but the code is clean and extensible. I’d propose a 2-week spike to validate integration with our current auth/JWT flow."*