Weave Code
Code Weaver
Helps Laravel developers discover, compare, and choose open-source packages. See popularity, security, maintainers, and scores at a glance to make better decisions.
Feedback
Share your thoughts, report bugs, or suggest improvements.
Subject
Message

Pusher Laravel Package

bentools/pusher

Send Web Push notifications to multiple recipients across providers (Chrome/GCM, Mozilla) using async/parallel Guzzle requests. Supports multiple API keys, ping/notification/server messages, and per-recipient delivery reporting for unsubscribes. Unmaintained.

View on GitHub
Deep Wiki
Context7

Product Decisions This Supports

  • Feature Development: Enables asynchronous push notifications for web apps (e.g., real-time alerts, user engagement features) without blocking the main request thread.
  • Roadmap Prioritization: Justifies investing in push notifications as a core feature if the product relies on user retention or real-time updates (e.g., SaaS dashboards, collaboration tools).
  • Build vs. Buy: Avoids reinventing the wheel for WebPush API integration, reducing dev time and technical debt. However, due to the package’s archived status, a fork or custom build may be necessary for long-term reliability.
  • Use Cases:
    • Notifying users of critical updates (e.g., payment confirmations, system alerts).
    • Offline-first messaging (e.g., progressive web apps).
    • Bulk notifications (e.g., marketing campaigns, admin broadcasts).

When to Consider This Package

Adopt if:

  • Your PHP/Laravel app needs asynchronous WebPush (Chrome/Firefox) with minimal setup.
  • You prioritize parallel request handling (Guzzle 6) for scalability.
  • You’re okay with experimental code and can fork/maintain it.
  • You need recipient-specific error handling (e.g., unsubscribing failed pushes).

Look elsewhere if:

  • You require active maintenance or enterprise-grade support (consider web-push-libs/web-push-php or commercial alternatives like Firebase Cloud Messaging).
  • Your stack isn’t PHP/Laravel (e.g., Node.js, Python).
  • You need cross-platform support (e.g., iOS/APNs) beyond Chrome/Firefox.
  • Compliance or security audits demand actively updated dependencies.

How to Pitch It (Stakeholders)

For Executives: "This package lets us send real-time push notifications to users’ browsers asynchronously—without slowing down our app. It’s lightweight, supports bulk messaging, and helps us retain users with timely alerts (e.g., ‘Your order is shipped’). While not actively maintained, we can fork it to ensure stability. The trade-off is minimal upfront cost vs. building this feature from scratch."

For Engineering: *"bentools/pusher is a PHP wrapper for WebPush API that uses Guzzle 6 for async, parallel requests. It’s a good fit if we need to:

  • Send notifications to Chrome/Firefox users without blocking requests.
  • Handle errors per recipient (e.g., auto-unsubscribe failed pushes).
  • Avoid reinventing async push logic. Downside: It’s archived, so we’d need to maintain it or fork it. Alternatives like web-push-php are more mature but less performant for bulk sends."*
Weaver

How can I help you explore Laravel packages today?

Conversation history is not saved when not logged in.
Prompt
Add packages to context
No packages found.
craftcms/url-validator
directorytree/privacy-filter-classifier
directorytree/privacy-filter
datacore/hub-sdk
develia/commons
cuci/prototurk-sdk
cuci/prototurk-sdk-symfony
develia/geo-bundle
dreamzy/livewire-charts
touchestate-sdk/php-sdk
22h/doctrine-garbage-collection-bundle
agtp/agtp-php
agtp/mod-php
splash/sonata-admin
splash/metadata
splash/openapi
splash/scopes
splash/toolkit
testo/output-teamcity
testo/bridge-symfony