Zap Laravel Package

Product Decisions This Supports

• Feature Development: Enables rapid implementation of appointment booking systems (e.g., healthcare, salons, or service providers) without reinventing scheduling logic. Reduces backend complexity by abstracting recurrence rules, conflict detection, and availability checks.
• Roadmap Alignment: Ideal for products targeting B2B SaaS (e.g., HR tools, facility management) or consumer-facing platforms (e.g., fitness studios, legal consultancies) where scheduling is a core feature.
• Build vs. Buy: Buy—saves 3–6 months of dev time for a robust, battle-tested solution. Avoids tech debt from custom calendar logic (e.g., edge cases in DST, timezone handling, or recurrence rules).
• Use Cases:
  • Healthcare: Doctor/patient appointment systems with blocked times (lunches, breaks) and recurring availabilities.
  • Enterprise: Meeting room or equipment booking (e.g., "Conference Room A is available 9 AM–5 PM, Mon–Fri").
  • E-commerce: Service-based products (e.g., "Book a consultation slot" for coaching or repair services).
  • Education: Class scheduling for tutors or training sessions with dynamic rules (e.g., "No overlaps with lab sessions").

When to Consider This Package

• Adopt if:

  • Your Laravel app requires flexible, recurring scheduling with conflict detection (e.g., "Can’t double-book a resource").
  • You need pre-built validation (e.g., "No weekend appointments," "Max 2-hour slots").
  • Your team lacks calendar/recurrence expertise but needs production-ready logic.
  • You’re using Laravel 13+ and PHP 8.5+ (future-proofing).
  • You want AI agent support (via Laravel Boost) for dynamic scheduling queries.

• Look elsewhere if:

  • You need multi-calendar sync (e.g., Google Calendar integration)—Zap is backend-only.
  • Your use case is highly niche (e.g., astronomical scheduling) and requires custom recurrence rules beyond Zap’s patterns.
  • You’re not using Laravel or need a frontend UI (Zap is backend-focused; pair with FullCalendar or similar).
  • You require real-time collaboration (e.g., shared editing of schedules)—Zap is optimized for server-side logic.
  • Your app uses pre-Laravel 13 or PHP <8.5 (though backports may exist).

How to Pitch It (Stakeholders)

For Executives: "Zap is a plug-and-play scheduling engine for Laravel that cuts months off development time for appointment-based products. It handles the complexity of recurring events, conflicts, and availability rules—so we can focus on UX and business logic. For example, a healthcare app could implement doctor booking in weeks instead of months, with built-in support for blocked times (lunches, vacations) and dynamic slot generation. It’s MIT-licensed, actively maintained, and integrates with Laravel’s ecosystem (e.g., AI agents via Boost). ROI: Faster time-to-market, fewer bugs in scheduling logic, and scalability for enterprise use cases like employee shift management or meeting room allocation."

For Engineering: *"Zap provides a fluent, chainable API to define availabilities, appointments, and blocked times with 100+ recurrence patterns (daily, weekly odd/even, monthly ordinal weekdays, etc.). Key features:

• Conflict detection: Automatically checks overlaps between appointments/availabilities.
• Flexible queries: Get bookable slots, next available time, or schedules for a date range in one line.
• Validation rules: Enforce constraints like noOverlap(), maxDuration(120), or workingHoursOnly('09:00', '17:00').
• UUID support: Works with non-integer primary keys out of the box.
• AI-ready: Laravel Boost skills for zap-schedules and zap-recurrence enable dynamic queries via AI agents. Installation is trivial (composer require laraveljutsu/zap), and it plays nicely with Laravel’s migrations and Eloquent. Perfect for replacing ad-hoc calendar logic with a maintainable, tested solution."