Webpush Laravel Package

Product Decisions This Supports

• Real-time engagement features: Enable push notifications for web apps (e.g., alerts, promotions, or transaction confirmations) without relying on third-party services like Firebase or OneSignal.
• Cross-browser compatibility: Support Chrome, Firefox, Edge, and Safari (with VAPID Subject for Apple compliance) for a unified notification system.
• Cost efficiency: Eliminate vendor lock-in or subscription fees for push notifications, leveraging open-source infrastructure.
• Roadmap alignment: Prioritize features like Declarative Web Push (future-proofing) or automated subscription cleanup to reduce maintenance overhead.
• Build vs. buy: Justify open-source adoption over proprietary solutions by highlighting customization (e.g., mutable notifications, TTL controls) and Laravel’s native integration.
• Use cases:
  • E-commerce: Cart abandonment alerts, order updates.
  • SaaS: Critical system notifications (e.g., "Your backup failed").
  • Social apps: Real-time activity updates (e.g., "Someone liked your post").
  • Internal tools: Admin dashboards with urgent alerts.

When to Consider This Package

• Adopt if:

  • Your app uses Laravel 12+ (PHP 8.2+) and targets web push notifications.
  • You need VAPID-compliant (secure) push notifications for Chrome/Firefox/Edge/Safari.
  • You want to avoid third-party dependencies (e.g., Firebase, OneSignal) for cost or compliance reasons.
  • Your team prefers Laravel’s native notification system over standalone services.
  • You require advanced customization (e.g., actions, badges, declarative messages).

• Look elsewhere if:

  • You need mobile push (iOS/Android) → Use Firebase Cloud Messaging (FCM) or Apple Push Notification Service (APNS).
  • Your app targets legacy browsers (IE11) or Laravel <12.
  • You lack backend infrastructure to generate/manage VAPID keys (Safari/iOS requires VAPID_SUBJECT).
  • You prioritize quick setup over customization (e.g., OneSignal’s dashboard).
  • Your use case involves high-frequency notifications (e.g., gaming) where Web Push may trigger browser restrictions.

How to Pitch It (Stakeholders)

For Executives: "This package lets us send web push notifications directly from Laravel—like SMS for the web—without third-party costs or lock-in. It’s secure (VAPID-compliant), works across all major browsers, and integrates seamlessly with our existing notification system. For example, we could use it to alert users about order updates or critical system issues, improving engagement without adding complexity. The open-source model also future-proofs us against vendor price hikes or API changes."

For Engineers: *"This is a battle-tested Laravel channel for Web Push that handles:

• VAPID key management (auto-generated, Safari-compliant).
• Subscription lifecycle (auto-cleanup of expired endpoints).
• Rich notifications (actions, badges, declarative messages for modern browsers).
• Laravel-native integration (works with via(), events like NotificationSent). It’s actively maintained (last release: May 2026), supports Laravel 12/13, and avoids proprietary dependencies. The trade-off is manual setup (VAPID keys, service worker client-side code), but the payoff is full control and no hidden fees."*