Push Bundle Laravel Package

Product Decisions This Supports

• Legacy System Migration: Integrate push notifications into an existing Symfony 2/3 application (since this bundle is tied to older Symfony versions) without building a custom solution.
• Cost-Effective Push Notifications: Avoid vendor lock-in or proprietary services (e.g., Firebase Cloud Messaging) by leveraging open-source alternatives like Mozilla Push or Google’s legacy GCM.
• Roadmap for Deprecation: If migrating to a modern stack (Symfony 5+), this bundle could serve as a temporary solution while evaluating alternatives (e.g., Symfony Messenger + Firebase Admin SDK).
• Internal Tooling: Use for non-critical internal tools or prototypes where push notifications are a secondary feature, justifying the use of an outdated but functional package.
• Compliance/Privacy: Preference for self-hosted or open-source push notification handling to avoid third-party data processing (e.g., GDPR compliance).

When to Consider This Package

• Avoid if:
  • Your project uses Symfony 4+ or Laravel (this bundle is Symfony 2/3-only; Laravel alternatives like laravel-notification-channels/webpush exist).
  • You need modern push protocols (e.g., WebPush, Firebase Cloud Messaging v1 API, or Apple Push Notification Service).
  • Your team lacks resources to debug/extend a 6-year-old, unmaintained package (last release: 2016).
  • You require active community support, documentation, or security updates (0 stars, 0 dependents, archived repo).
  • Your use case demands scalability (e.g., millions of subscriptions) without custom optimizations.
• Consider alternatives:
  • For Symfony 4+: symfony/messenger + web-push-php.
  • For Laravel: laravel-notification-channels/webpush.
  • For self-hosted WebPush: pywebpush or web-push (Node.js).

How to Pitch It (Stakeholders)

For Executives: "This bundle offers a quick, low-cost way to add push notifications to our legacy Symfony 2/3 app using open-source protocols like Mozilla Push or Google’s deprecated GCM. It’s a viable stopgap if we’re constrained by time/budget and can’t invest in a modern rewrite. However, we’d need to weigh the risks of technical debt against the effort to migrate to a supported solution. Recommend exploring this only if push notifications are a non-critical feature or if we’re phasing out this legacy system soon."

For Engineering: *"The cmnty/push-bundle provides a thin wrapper around the cmnty/push library, which supports Mozilla Push and legacy GCM. Key trade-offs:

• Pros: Simple YAML config, Doctrine integration for subscriptions, and MIT license.
• Cons: No longer maintained (last release 2016), limited to Symfony 2/3, and lacks modern protocols (e.g., WebPush).
• Pitch: Use this only if:
  1. You’re stuck on Symfony 2/3 and need a quick push solution.
  2. You’re okay with maintaining a fork or replacing it in 6–12 months.
  3. Your use case aligns with Mozilla Push/GCM (not WebPush or Firebase).
• Alternatives: For new projects, prioritize symfony/messenger + web-push-php or Laravel’s WebPush channel. For this legacy app, we could also evaluate a lightweight custom solution using pywebpush or web-push-php directly."*