- Can I use this package to create customer-facing forms without writing frontend code?
- Yes, this package lets you design forms entirely in Filament’s admin panel and render them on the frontend using Blade, Inertia, or SPAs. You’ll need basic frontend templates to display the forms, but no custom form logic is required for simple use cases.
- What Laravel and Filament versions does this package support?
- The package requires Laravel 11+ and Filament 4.x/5.x. It’s not compatible with Filament 3.x or older Laravel versions. Always pin the `filament/filament` package to an exact version in `composer.json` to avoid breaking changes.
- How do I handle form validation? Does it work with Laravel’s Form Requests?
- Validation is fully integrated with Laravel’s ecosystem. You can use standard Laravel validation rules, Form Requests, or Eloquent validation. The package ensures consistency with your existing backend validation logic.
- Is this package suitable for multi-step or conditional forms?
- Basic multi-step forms are supported, but complex conditional logic may require custom Filament field extensions. The package leverages Filament’s `HasFields` contract, so you can extend functionality for advanced workflows.
- How do I export form responses to CSV? Are there performance concerns?
- CSV exports use `maatwebsite/excel`, which integrates seamlessly with Laravel. For large datasets, monitor memory usage—test with your expected response volume to avoid timeouts. Bulk exports may need optimization.
- Can I use this package with Inertia.js or Vue/React for SPAs?
- Yes, but you’ll need to pass form definitions to your frontend via props (Inertia) or API endpoints (SPAs). The package doesn’t provide a headless API out of the box, so custom integration may be required for dynamic frontend rendering.
- What if I don’t use Filament in my Laravel project? Should I switch?
- This package is tightly coupled to Filament, so adopting it requires Filament in your stack. Evaluate whether Filament’s learning curve and admin panel benefits justify the switch for your use case.
- How do I customize form fields beyond the default Filament components?
- Extend the package using Filament’s `HasFields` contract to create custom fields. Document your custom field requirements, as they may need specific handling in both the admin and frontend.
- Are there any database migration requirements? What if I’m using an existing schema?
- The package doesn’t enforce migrations—it uses Eloquent models for form definitions and responses. You can adapt existing schemas with minimal changes, but publishing the migrations will set up the default tables for form storage.
- What are the alternatives to this package for dynamic forms in Laravel?
- Alternatives include `spatie/laravel-form-builder` (for simpler forms), `orchid/platform` (if using Orchid), or building custom solutions with Laravel Livewire or Inertia. This package stands out for its deep Filament integration and admin-driven workflow.