Mary Laravel Package

Product Decisions This Supports

• Accelerate UI/UX consistency: Standardize UI components across Laravel/Livewire applications, reducing design system drift and developer onboarding time.
• Build vs. Buy: Avoid reinventing UI components (e.g., modals, tables, forms) by leveraging a battle-tested, Tailwind/DaisyUI-powered library.
• Roadmap for internal tooling: Prioritize adoption for admin dashboards, CRUD interfaces, or public-facing forms where polished UI is critical.
• Livewire-first strategy: Align with Livewire’s reactive paradigm by replacing custom Blade components with pre-built, optimized alternatives.
• Accessibility & compliance: Reduce risk of non-compliance by using components with built-in ARIA attributes (e.g., dropdowns, modals, carousels).
• Developer experience (DX): Enable frontend engineers to prototype faster with reusable, documented components (e.g., mary-toast, mary-drawer).
• Theming flexibility: Support dark/light mode or brand customization via Tailwind’s utility classes without sacrificing consistency.

When to Consider This Package

Adopt if:

• Your team uses Livewire and needs pre-built, Tailwind/DaisyUI components (e.g., forms, modals, tables).
• You prioritize rapid UI development over custom CSS/JS for common patterns (e.g., dropdowns, date pickers).
• Your project requires accessibility compliance (e.g., screen reader support in modals, dropdowns).
• You’re migrating from custom Blade components to a standardized system with minimal refactoring.
• Your stack includes Laravel 10+ and Livewire 3/4 (verified compatibility).

Look elsewhere if:

• You need highly customized animations (Mary uses DaisyUI/Tailwind’s defaults).
• Your app relies on non-Livewire frontend frameworks (e.g., React, Vue).
• You require enterprise-grade support (package is community-driven; no SLA).
• Your design system mandates non-Tailwind CSS (e.g., Bootstrap, custom SCSS).
• You’re building a public SaaS where branding uniqueness is critical (components may feel "generic").

How to Pitch It (Stakeholders)

For Executives: "MaryUI lets us ship polished, consistent interfaces 30–50% faster by replacing custom UI code with pre-built, Livewire-optimized components. It’s like hiring a senior frontend designer for every form, modal, and dashboard—without the overhead. With 1.5K+ GitHub stars and active maintenance, it’s a low-risk way to elevate our product’s UX while reducing tech debt. Think of it as ‘Figma for Livewire.’"

For Engineers: *"MaryUI gives us Tailwind-powered, Livewire-first components (modals, tables, date pickers, etc.) with zero CSS/JS reinvention. Key perks:

• Livewire-native: Components sync seamlessly with Livewire’s reactivity (e.g., real-time updates in modals).
• DaisyUI/Tailwind: Consistent styling with zero custom CSS for 90% of use cases.
• Battle-tested: Used by 1.5K+ projects; handles edge cases (e.g., RTL, accessibility).
• Future-proof: Actively maintained (Laravel 13/Livewire 4 support). Example: Replace your custom CreateUserForm with <mary-input wire:model="name"> and gain validation, error handling, and styling for free."*

For Designers: "MaryUI lets us enforce our design system without fighting with devs over pixel-perfect implementations. It’s a library of DaisyUI-inspired components that match our Tailwind-based system, so we can focus on high-level UX—like micro-interactions—while the team gets consistent buttons, cards, and modals out of the box."