Product Decisions This Supports
- The vendor question is unchanged; the integration question is now settled. Skebby remains a credible Italian/EU SMS gateway and a direct input to "do we ship SMS this quarter, and for which journeys?" (OTP/2FA, order confirmations, delivery updates for Italian-speaking users). What v4.0.0 clarifies is that this package is a Symfony bundle, not a Laravel package — so for a Laravel codebase the build-vs-buy call collapses to "call Skebby's REST API directly."
- Platform scoping is now explicit, not inferred. The release notes state Symfony 5.4|6.0 support. That is a product-level fact: any Laravel service is out of scope for this dependency, full stop. If we run Symfony services, this becomes a candidate for a spike; if we don't, it is documentation only.
- Vendor selection still needs its own analysis. Skebby vs. Twilio/Vonage/MessageBird/AWS SNS on per-message cost to Italian numbers, alphanumeric sender ID registration, two-way SMS, delivery receipts, and GDPR/data-residency posture. This package only ever prices out the Skebby side of that comparison.
- New surface area: account and credit operations. v4.0.0 exposes the User's API alongside the SMS API, which turns "send SMS" into a broader ops story — balance/credit visibility, low-credit alerting, spend tracking, and sender-ID/account configuration. That is a genuine product requirement for finance and support ("we must not silently stop sending OTPs because the account hit zero"), and it is now something we can scope rather than assume.
- Provider abstraction recommendation is reinforced, not weakened. A single-maintainer wrapper that has just changed framework target (and bumped a major version) is the textbook case for keeping SMS behind a
NotificationChannel/transport interface. Adopt the Skebby API, not this package.
- Framework lifecycle risk to surface. Symfony 5.4 and 6.0 are both past end-of-life; a bundle whose stated compatibility targets EOL frameworks inherits that risk. "Fixes dependencies" is a positive maintenance signal, but it does not make the target stack current.
- Breaking-change flag. This is a major version bump with a framework pivot. If anything anywhere pinned v3, treat migration as a non-trivial task, not a patch.
When to Consider This Package
Consider it if:
- You are running a Symfony 5.4 or 6.0 service (not Laravel) and want a timeboxed spike or API reference to validate Skebby as a vendor.
- You need both SMS sending and account/user endpoints (credit balance, sender configuration) demonstrated against Skebby's contract.
- You are comfortable forking it, pinning it, and owning it — treating it as sample code rather than a dependency.
Look elsewhere if:
- You are on any Laravel version. This is a Symfony bundle; it will not register a Laravel service provider or config. This is now a confirmed mismatch, not a version-support caveat.
- You are on modern Symfony (6.4 LTS / 7.x) or PHP 8.2+; the stated support matrix stops at 6.0.
- You need maintenance guarantees, security patching, delivery webhooks, retries, queueing, multi-provider failover, or volume pricing.
- You need audited compliance (consent logs, opt-out sync) or non-Italian routes.
Better paths: call Skebby's documented REST API directly with Laravel's Http client (~150 lines plus config, tests, and logging); on Symfony, use the framework's HTTP client behind your own transport. If you want a maintained integration instead, use an established notification channel via Twilio/Vonage. Reserve this package for a timeboxed spike and as a readable reference for both the SMS and User APIs.
How to Pitch It (Stakeholders)
To executives: SMS remains a plausible near-term channel for OTP and transactional messages to our Italian users, and Skebby is a credible EU-based vendor with EU data residency. The v4.0.0 release is a maintenance and scope update, not a vindication: it explicitly targets Symfony 5.4/6.0, which means it was never a Laravel package and is not one now. It does add account/credit APIs, which is useful for operations (balance monitoring, spend visibility). Recommendation: do not take a production dependency on the package in a Laravel codebase. Approve a 2–3 day spike to validate the Skebby contract — SMS plus credit/balance endpoints — and build a small internal transport behind our notification layer. Budget the vendor agreement, not the package.
To engineering: Treat this repo as documentation of Skebby's API — now covering both the User's API (account, credit, sender configuration) and the SMS send API — not as a library. Implement a SkebbyTransport behind an SMS interface using Laravel's HTTP client, with config-driven credentials, retries, structured logging, balance/low-credit checks surfaced to ops, and tests against recorded responses. Note the v4.0.0 major bump and Symfony pivot: if any Symfony service pinned v3, budget a migration; if none did, treat this as a reference read and move on. Vendor swap cost stays near zero and the abandoned-dependency risk is removed entirely.