Filament Form Builder Laravel Package

Product Decisions This Supports

• Build vs. buy for dynamic forms and submissions: v1.4.0 strengthens the case for buying/adopting this package instead of building an in-house form builder. Teams get field rendering (Blade, Livewire, panel/preview), JSON-backed form definitions, submission storage, filters, and detail views without owning the full stack.
• Feedback, survey, and application workflows: The optional packstub/filament-rating integration adds star inputs, average/distribution columns, a “4 stars & up” filter, and star display in submission details. This supports product decisions around collecting and triaging ratings for workshops, tickets, applications, or service feedback.
• Form UX and layout decisions: Configurable columns for radio and checkbox choices (up to four columns, responsive to one on small screens) lets PMs improve long-form completion rates without engineering work. The layout is stored in the field options/JSON, so it travels with form definitions.
• Roadmap sequencing for submissions analytics: The star column sorts numerically by score across MySQL and Postgres, which supports prioritization views and reporting. PMs can decide to expose rating-based filters and distribution summaries earlier because the package already handles the display layer.
• Low-risk enhancement decisions: The rating integration is detected, never required, and the stored score is unchanged. PMs can ship visual rating improvements without a data migration or committing to a specific rating UI package. The detailEntry() extension point also gives engineering a path for custom field detail displays.
• Use cases: workshop/ticket registration forms, internal request intake, customer feedback surveys, application forms, event session ratings, and any Filament-based admin workflow that needs configurable forms plus a submissions table.

When to Consider This Package

Consider this package when:

• The product is built on Laravel and Filament, especially with Livewire-based admin panels.
• You need configurable/dynamic forms with multiple field types, previews, and a submissions table, rather than a one-off static form.
• You want fast iteration on form UX — for example, multi-column choice layouts or rating display — without custom frontend work.
• You need submission review, filtering, and detail views inside an admin panel, and want rating/filter support out of the box.
• You prefer optional integrations over hard dependencies. The rating package is detected at runtime, and stored scores remain unchanged if it is installed or removed.
• You want form definitions stored in JSON/options so layouts and field settings persist with the form rather than in code.
• You are deciding build vs. buy for internal form tooling and want to avoid maintaining renderers, table columns, filters, and previews yourself.

Look elsewhere when:

• The application is not on Laravel/Filament or cannot use Livewire for the renderer and admin experience.
• You need complex multi-step workflows, conditional logic, approvals, or integrations beyond form definition, rendering, submissions, and basic review.
• You require deep customization of every renderer and table interaction; at that point a bespoke form layer may be cleaner.
• You need ratings to write back to the score or enforce rating-specific validation as a first-class data contract; this release deliberately keeps the stored score unchanged and treats stars as a presentation layer.
• You cannot accept an optional third-party UI dependency for rating display, even one that is detected and non-required.

How to Pitch It (Stakeholders)

For executives: This package lets us ship configurable forms and a submissions review experience on top of our existing Laravel/Filament stack instead of building a form builder from scratch. The latest release adds optional star-rating display, rating filters, and responsive multi-column choice layouts — improvements that make feedback and application workflows more usable without changing our data model. It is a buy/adopt decision that reduces time-to-market for internal and customer-facing form workflows.

For engineering: v1.4.0 keeps the rating integration optional and non-invasive: packstub/filament-rating is detected, never required, and the stored score is unchanged. We get star input, star columns, numeric sorting across MySQL/Postgres, a “4 stars & up” filter, and a detailEntry() extension point for custom field details. Choice fields can now render radio/checkbox options in up to four responsive columns, with the layout stored in the field’s JSON options. The docs were also tightened. The main engineering considerations are Livewire/Filament coupling, the optional rating package dependency, and how much workflow complexity we expect beyond form rendering and submissions review.