Shariff Laravel Package

Product Decisions This Supports

• PHP 8.3/8.4 Compatibility: Aligns with modern Laravel ecosystems (Laravel 10+ defaults to PHP 8.2+), reducing technical debt and enabling long-term maintenance. Critical for teams adopting newer PHP versions or migrating legacy systems.
• Facebook Graph API v25.0 Integration: Ensures continued access to Facebook share metrics amid API deprecations, future-proofing compliance with evolving platform policies (e.g., reduced organic reach transparency).
• Deprecated Service Cleanup: Removes unsupported services (StumbleUpon, Flattr) to streamline codebase and reduce maintenance overhead, simplifying configuration for stakeholders.
• PSR-12 Code Standards: Improves readability and onboarding for new developers, accelerating feature development or custom integrations (e.g., adding new social platforms).
• Roadmap for Modernization: Drops PHP 7.4/8.0 support, signaling a shift toward performance optimizations (e.g., typed properties, JIT compilation) that benefit high-traffic applications.
• Use Cases Expanded:
  • Enterprise Laravel Apps: Justify PHP 8.3+ upgrades by leveraging this package’s compatibility.
  • Regulated Industries: Mitigate risks from Facebook API changes (e.g., healthcare, finance) by ensuring up-to-date share data.
  • Open-Source Contributions: Use the package as a template for custom social analytics tools with modern PHP practices.

When to Consider This Package

• Adopt if:

  • Your Laravel app requires PHP 8.2+ (or plans to upgrade) and needs privacy-compliant social metrics.
  • You rely on Facebook shares and want to avoid API disruptions (v25.0 is current as of 2024).
  • Your team can maintain PHP 8.3/8.4 (no PHP 7.x support).
  • You want to reduce technical debt by using a package with active updates (last release Oct 2023, now v11.0.0).
  • StumbleUpon/Flattr were previously used but can be replaced by other services (e.g., Mastodon, Bluesky).

• Look elsewhere if:

  • You’re stuck on PHP 7.4/8.0 (no support; consider downgrading to v10.0.0 or a fork).
  • You need StumbleUpon/Flattr support (removed; use a custom solution or alternative packages).
  • Your primary concern is real-time data (Facebook API v25.0 may introduce latency; monitor their status).
  • You lack resources to upgrade PHP versions or handle API changes (e.g., Facebook’s evolving permissions).

How to Pitch It (Stakeholders)

For Executives:

*"The latest release of Shariff (v11.0.0) brings our social sharing analytics in line with modern PHP standards and Facebook’s latest API—ensuring we stay compliant and performant without third-party risks. Key upgrades:

• Future-proof: Supports PHP 8.3/8.4, aligning with our [tech stack roadmap].
• Facebook-ready: Uses Graph API v25.0 to avoid data gaps from platform changes.
• Cleaner code: Removes outdated services (StumbleUpon/Flattr) to simplify maintenance.

This reduces our dependency on legacy systems and keeps us ahead of regulatory shifts. For example, Heise.de uses this to maintain GDPR compliance while tracking shares—now with even better performance.

Ask: Should we prioritize this update alongside our [PHP 8.3 migration] to lock in these benefits?"*

Key Outcomes:

• ✅ Compliance: Up-to-date Facebook API access.
• ✅ Performance: PHP 8.3+ optimizations for high-traffic sites.
• ✅ Cost: No vendor lock-in; open-source with transparent updates.
• ✅ Risk Reduction: Removes deprecated services, lowering maintenance costs.

For Engineering:

*"v11.0.0 is a low-risk, high-reward upgrade with these critical changes:

• PHP 8.2+ Required: Drops PHP 7.4/8.0 support (aligns with Laravel 10+). If you’re not ready, we can pin to v10.0.0 or fork.
• Facebook Graph API v25.0: Updates the Facebook service to the latest version. Action needed: Test this in staging—Facebook’s API changes often break share counts (e.g., v14.0 migration issues).
• PSR-12 Codebase: Easier to extend (e.g., adding Mastodon support) or debug.
• Deprecated Services Removed: StumbleUpon/Flattr are gone. If these were critical, we’ll need a replacement (e.g., custom API calls).

Implementation Plan:

1. Upgrade PHP (if not already on 8.2+): Use Laravel’s upgrade guide.
2. Test Facebook API: Verify share counts for key pages in staging. Monitor Facebook’s changelog for v26.0.
3. Update Dependencies: Run composer update and check for conflicts.
4. Deprecation Review: Audit your config for removed services (e.g., shariff.facebook vs. shariff.stumbleupon).

Risks:

• Facebook API deprecations (mitigate by testing early and setting up alerts).
• PHP upgrade blockers (e.g., third-party packages). Use phpstan to catch issues pre-deployment.

Alternatives:

• Downgrade to v10.0.0: If PHP 8.2+ isn’t feasible.
• Custom Fork: If you need StumbleUpon/Flattr (last supported in v10.0.0).

Let’s prototype this in [Project Y] to validate the Facebook API changes before rolling out globally."*