Smsir Php Laravel Package

Product Decisions This Supports

• Ship OTP/2FA and transactional SMS now vs. defer — for a Laravel app serving Iranian users, this is a low-cost enabler for phone-based signup, login verification, order confirmations, and status alerts.
• Build vs. buy for SMS plumbing — effectively a free "buy": a thin Laravel integration (config publishing, service provider, notification channel/facade) instead of an in-house HTTP client. Cuts story points on undifferentiated work.
• Vendor standardisation — adopting it is implicitly a decision to standardise on SMS.ir as the messaging provider, not just a library choice. Treat it as a vendor commitment.
• Roadmap sequencing — unlocks onboarding/activation epics (OTP) and notification epics that often gate conversion and retention metrics.
• MVP vs. hardened production — useful as a prototype accelerator; promotion to production is a separate decision requiring an internal owner.
• Dependency risk posture — unofficial package, ~17 stars, last release Feb 2023. The real decision is "adopt as forked source we own" vs. "skip and build a thin internal client."

When to Consider This Package

Consider adopting when:

• You have a Laravel (or plain PHP) app with Iranian end users and SMS.ir is your chosen or acceptable provider.
• You need OTP, transactional alerts, or bulk SMS and want working integration in hours.
• It's an MVP, prototype, or internal tool where a stale wrapper is tolerable.
• You will vendor/fork under MIT, own the code, and add your own contract tests.
• The team can read a small wrapper and patch it against SMS.ir's API docs if the API drifts.

Look elsewhere when:

• Messaging is production-critical and requires SLAs, deliverability guarantees, or vendor support.
• You need active maintenance, security patching, or an escalation path — 17 stars and a 2023 last release are weak support signals.
• You want a multi-provider strategy (Kavenegar, Melipayamak, etc.) or regional portability; a provider-agnostic internal interface is cheaper long-term.
• You're outside Laravel, or need capabilities the wrapper likely doesn't cover (webhooks, templating, delivery receipts, contact management).
• Compliance/audit requirements make "unofficial, single-maintainer, unmaintained" unacceptable.

How to Pitch It (Stakeholders)

Executives: This is a free, MIT-licensed shortcut to SMS.ir integration in Laravel — the fastest path to phone-based signup/OTP and transactional notifications for Iranian users, potentially saving days of engineering effort per integration. The caveat is material: it is unofficial, has a very small community (~17 stars), and has not had a release since February 2023. Treat it as reusable starting code we own, not a supported dependency. Recommendation: green-light for MVP and timeline-sensitive work with a modest budget for internal ownership — vendor the code, add tests, watch SMS.ir API changes. Do not elevate it to a platform-level dependency without a named maintainer.

Engineering: It's a thin wrapper — service provider, config, facade/notification channel. Pin the version and fork it into our repo; wrap it behind our own SmsSender interface so a provider swap is a config change; add contract tests against the live SMS.ir API to detect drift. Assume no upstream patches will arrive for us.