Airgram Bundle Laravel Package

Product Decisions This Supports

• Legacy System Integration: Accelerates integration with AirGram (a now-defunct SMS/notification service) for projects maintaining old SMS-based workflows (e.g., OTPs, alerts, or legacy customer notifications).
• Cost Optimization: Avoids reinventing a custom SMS gateway for niche use cases where AirGram was previously used, reducing dev effort.
• Migration Path: Enables gradual replacement of deprecated AirGram APIs in Symfony apps without full rewrite.
• Roadmap Pause: Justifies delaying SMS infrastructure upgrades if AirGram was a temporary solution (e.g., during a transition to Twilio/Vonage).
• Build vs. Buy: Favors "buy" for teams with limited SMS expertise or tight deadlines, trading long-term flexibility for short-term speed.

When to Consider This Package

• Avoid if:
  • AirGram is shut down (confirmed via Wayback Machine or service status). Use alternatives like Twilio, Nexmo, or AWS SNS.
  • Your project requires modern features (e.g., MMS, global coverage, or analytics) — this bundle is abandoned (last update: 2015).
  • You’re building a new product (not maintaining legacy systems). Risk of tech debt outweighs benefits.
  • Security/compliance is critical: No updates mean unpatched vulnerabilities (e.g., PHP 5.6+ compatibility unknown).
• Consider only if:
  • You’re maintaining a Symfony 2.x app with hardcoded AirGram dependencies.
  • The bundle is already in your codebase and you need to preserve functionality temporarily.
  • You’re in a highly constrained environment (e.g., no budget for SMS provider swaps).

How to Pitch It (Stakeholders)

For Executives: "This bundle lets us quickly re-enable AirGram SMS functionality in our legacy Symfony app without a full rewrite—buying us time to evaluate modern alternatives. It’s a stopgap for [specific feature X], not a long-term solution. Risk is low because [Y reason], but we’ll phase it out by [date]."

For Engineering: *"The BBIT AirGram Bundle is a Symfony 2.x wrapper for the defunct AirGram API. It’s not maintained (last update: 2015), so use it only for:

• Short-term fixes in legacy systems.
• Testing if AirGram was a viable option (it’s not—plan for Twilio/Nexmo). Pros: 5-minute setup, minimal code changes. Cons: Security risks, no support, dead service. Recommendation: Only adopt if you’re already using AirGram and need to avoid a rewrite. Otherwise, skip."*

For Developers:

**TL;DR**:
- **Install**: `composer require bbit/airgram-bundle:dev-master` (yes, `dev-master`).
- **Configure**: Add `BranchBitAirGramBundle` to `AppKernel.php` and set API keys.
- **Use**: `$this->get('bbit_airgam')->send('email@example.com', 'msg')`.
**Warning**: This is a **zombie package**. Use only for legacy systems. Replace ASAP.