Mobyt Notifier Laravel Package

Product Decisions This Supports

• Unified Notification Infrastructure: Enables Laravel applications to leverage Symfony Notifier’s Mobyt bridge for SMS, consolidating notification channels (email, SMS, push) under a single, maintainable framework. Reduces technical debt from fragmented SMS solutions (e.g., Twilio, AWS SNS).
• Cost-Effective SMS Scaling: Supports Mobyt’s tiered message quality (N/L/LL) to optimize costs for high-volume use cases like:
  • Transactional alerts (e.g., OTPs, order confirmations) → Use L (medium) for balance.
  • Marketing campaigns → Use LL (low) to reduce spend.
  • Urgent notifications (e.g., fraud alerts) → Use N (high) for priority delivery.
• Build vs. Buy: Buy—avoids custom SMS transport development while integrating with Laravel’s existing Notification system. Ideal for teams using Laravel but needing enterprise-grade SMS reliability (Mobyt is used by banks/telecoms).
• Roadmap Enablers:
  • Phase 1: Replace ad-hoc SMS services with a standardized, configurable Mobyt channel.
  • Phase 2: Extend to support scheduled SMS or A/B testing via MobytOptions.
  • Phase 3: Integrate with Laravel Horizon/Queues for async SMS workflows (e.g., bulk sends).
• Compliance & Reliability: Mobyt’s infrastructure reduces risk of SMS delivery failures or regulatory issues (e.g., carrier restrictions, spam filters), critical for fintech/healthcare apps.

When to Consider This Package

• Adopt if:

  • Your primary SMS provider is Mobyt (or you’re evaluating it for cost/reliability).
  • You’re using Laravel 10+ (PHP 8.2+) and can upgrade to PHP 8.4+ for Symfony 8 compatibility.
  • You need low-code integration with Mobyt’s API (no custom HTTP clients).
  • Your team is familiar with Laravel Notifications and can extend it with Symfony bridges.
  • You prioritize unified notification channels (e.g., email + SMS via same framework).

• Look elsewhere if:

  • You’re not using Mobyt—consider native SDKs (e.g., Twilio, AWS SNS) or Laravel-specific packages.
  • You need advanced SMS features (e.g., MMS, rich media, interactive messages) unsupported by Mobyt.
  • Your team lacks Symfony/Laravel Notifications expertise—integration requires understanding of Symfony Notifier’s transport system.
  • Dependents = 0: Limited community adoption; evaluate long-term support risks (e.g., Mobyt API changes).
  • You require real-time analytics—this package is transport-only; pair with Mobyt’s dashboard or a third-party tool.
  • PHP version constraints: If stuck on PHP <8.4, use an older Symfony version (e.g., 6.4) but risk compatibility gaps.

How to Pitch It (Stakeholders)

For Executives:

*"This package lets us send SMS notifications through Mobyt—a reliable, enterprise-grade provider—using Laravel’s existing Notification system. It’s a low-risk, high-efficiency solution:

• Unifies SMS with other notifications (email, Slack) under one framework, reducing complexity.
• Cuts SMS costs with Mobyt’s tiered delivery options (N/L/LL), saving 20–50% vs. premium providers for bulk sends.
• Reduces support overhead: Mobyt’s infrastructure handles deliverability, cutting failures/spam complaints.
• Future-proof: Aligns with Laravel’s roadmap and avoids custom SMS code. ROI: Faster time-to-market for SMS features, lower operational costs, and scalability for high-volume use cases like alerts or marketing."*

For Engineering:

*"Symfony’s Mobyt Notifier Bridge gives us a drop-in SMS transport for Laravel with minimal effort. Key benefits:

• Zero custom code: Uses Laravel’s Notification system + Symfony Notifier (already in our stack).
• Config-driven: Set up via .env (e.g., MOBYT_DSN)—no hardcoded credentials.
• Extensible: Add Mobyt-specific options (e.g., message quality) via MobytOptions.
• Laravel-compatible: Works with Illuminate\Notifications if we register it as a custom channel.

Tradeoffs:

• Symfony dependency: Requires PHP 8.4+ (Laravel 10+). If stuck on older PHP, we’d need to downgrade Symfony versions.
• Undocumented Laravel integration: Since this is a Symfony package, we’ll need to build a Laravel channel wrapper (e.g., extend NotificationChannel).
• Limited adoption: No Laravel-specific examples, so we’ll need to spike integration (e.g., test with a demo app).

Action Items:

1. Spike: Test integration in a Laravel app using Symfony Notifier’s demo as a reference.
2. Cost Analysis: Compare Mobyt’s pricing tiers (N/L/LL) against current SMS providers (e.g., Twilio, AWS SNS).
3. Architecture: Plan to register Mobyt as a Laravel Notification channel (e.g., MobytChannel) and document the setup.
4. Fallback Plan: Define retry logic or alternative SMS providers if Mobyt’s API fails."

For Product/Design:

*"This integration enables scalable, cost-controlled SMS notifications without sacrificing reliability. Key use cases:

• Transactional SMS: OTPs, order updates (use L for cost savings).
• Marketing Campaigns: Bulk promotions (use LL to reduce spend).
• Critical Alerts: Fraud notifications (use N for priority delivery). Impact:
• Faster iterations: No need to build/maintain custom SMS logic.
• Better UX: Mobyt’s infrastructure improves deliverability, reducing missed alerts.
• Data insights: Mobyt’s dashboard can track SMS performance (pair with analytics tools)."*

Key Risk Mitigation:

• Spike integration before full adoption (test with a non-critical feature).
• Monitor Mobyt’s API stability and set up alerts for outages.
• Document fallback procedures (e.g., queue failed SMS for retry with a backup provider).