Rad Laravel Package

Product Decisions This Supports

• Standardized AJAX Protocol: Enables consistent error handling, user feedback (toasts), and redirects across frontend-backend interactions, reducing frontend development friction.
• Symfony Integration: Accelerates development for PHP/Symfony teams by providing a pre-built, opinionated solution for AJAX responses, avoiding reinventing the wheel.
• Frontend-Backend Alignment: The TypeScript interface ensures type safety and shared understanding between teams, reducing miscommunication.
• Error Tracking Optimization: Avoids flooding error monitoring tools with 400 errors for AJAX requests, improving observability.
• Roadmap for Modularity: If building a component library or API-first architecture, this package can serve as a foundation for reusable AJAX patterns.
• Build vs. Buy: Justifies buying (using this package) over building a custom AJAX protocol for Symfony projects, especially if the team lacks frontend-backend alignment tools.

When to Consider This Package

• Symfony-Based Projects: Only relevant if your stack includes Symfony; not applicable to Laravel or other PHP frameworks.
• AJAX-Heavy Applications: Ideal for SPAs, dashboards, or admin panels where AJAX interactions are frequent and require consistent UX patterns (e.g., toasts, redirects).
• Frontend-Backend Collaboration: Useful if your team has both PHP/Symfony backend and TypeScript/JavaScript frontend developers who need shared contracts.
• Need for Standardization: Adopt if your project lacks a unified way to handle AJAX errors, success states, or user feedback (e.g., no standardized toast messages or redirect logic).
• Low Maintenance Overhead: Prefer this over custom solutions if you want minimal upkeep for AJAX response handling.
• Avoid If:
  • Your project uses Laravel (this is Symfony-specific; Laravel alternatives like spatie/laravel-response may fit better).
  • You need highly customizable AJAX responses (this enforces a specific protocol).
  • Your team prefers RESTful APIs over AJAX protocol-driven interactions.
  • You’re already using a different frontend framework (e.g., React with a custom API layer) that doesn’t align with the mojave client.

How to Pitch It (Stakeholders)

For Executives: "This package standardizes how our Symfony backend communicates with the frontend via AJAX, reducing bugs and development time. It enforces a consistent protocol for errors, user feedback (like toasts), and redirects—improving UX reliability. By adopting this, we align our frontend and backend teams under a shared contract, cutting miscommunication and speeding up feature delivery. It’s a lightweight, low-risk way to professionalize our AJAX interactions, with minimal maintenance overhead."

For Engineering/Tech Leads: *"The becklyn/rad package gives us a battle-tested AJAX response protocol for Symfony, complete with TypeScript types for the frontend. Key benefits:

• Consistency: Standardized error handling, toasts, and redirects across all AJAX calls.
• Observability: Avoids 400 errors in monitoring tools by using 200 OK for all AJAX responses.
• Frontend-Backend Sync: Shared TypeScript interface reduces integration friction between our Symfony backend and frontend teams.
• Quick Integration: Works out-of-the-box with Symfony and pairs with the mojave client for the frontend. Tradeoff: It’s Symfony-only, so we’d need to evaluate Laravel alternatives if we’re not locked into Symfony. For our current stack, this is a no-brainer for reducing tech debt in AJAX-heavy flows."*