Filament Selectify Laravel Package

Product Decisions This Supports

• Feature decisions: Add more usable selector controls to Filament admin forms—toggles, radio-style choices, and other selection inputs—without building custom Livewire/Blade components. Useful for settings pages, status pickers, role/permission presets, notification preferences, plan selection, filters, and onboarding flows.
• Roadmap prioritization: Treat admin UX polish as a low-effort, high-leverage improvement rather than a design-system project. A small MIT package can validate demand before committing roadmap capacity to custom UI work. The v3.0.0 release adds Filament v4 compatibility, which extends the window in which this remains a cheap option as the platform upgrades.
• Build vs. buy: Favor adoption when the team already uses Filament and the need is standard selection UX. Avoid custom component work unless the interaction is core to the product or needs behavior the package does not support.
• Standardization: Use the package to reduce inconsistent toggle/radio implementations across internal tools and admin panels, improving operator accuracy and reducing form friction. v3.0.0 is the version to standardize on for Filament v4 environments; keep Filament v3 deployments pinned to the v2.x line.
• Experimentation: Pilot the fields in one high-traffic admin form to measure usability impact and implementation effort before broader adoption—ideally alongside your Filament v4 upgrade so the compatibility validation is a single effort.

When to Consider This Package

• Consider it when the product already runs on Filament and needs better selection controls in admin or internal workflows.
• Version alignment matters more than before. v3.0.0 is a major release whose headline change is Filament v4 compatibility, so it almost certainly drops Filament v3 support. Confirm the exact constraint matrix (Filament, Laravel, PHP) before upgrading, and expect to move the package and Filament together rather than independently.
• Adopt when the team values fast delivery, MIT licensing, small surface area, and recent maintenance over enterprise support. The v3.0.0 release is a positive maintenance signal: an outside contributor shipped the v4 compatibility work, so the project is not solely dependent on one maintainer for platform upgrades.
• Validate accessibility, localization, dark mode, and theme behavior in staging—particularly on v3.0.0, where a major version bump plus a new Filament major means visual regressions are the most likely failure mode.
• Look elsewhere if you are not using Filament, need complex custom interactions, require an enterprise SLA, have a strict dependency policy, or need proven adoption at scale. With 47 stars, treat it as a useful niche package: low integration cost, but also low community redundancy and higher maintainer-risk sensitivity.
• Be cautious if your Filament upgrade timeline is uncertain—sitting on Filament v3 means sitting on v2.x of this package, which may stop receiving fixes. If your design system already owns these components, the upgrade is not worth the churn.

How to Pitch It (Stakeholders)

For executives: This is a low-cost, MIT-licensed UI enhancement for Filament-based admin tools. It can improve operator efficiency and form usability while avoiding custom frontend build costs. The newest major release adds support for Filament v4, so the package stays viable through your next platform upgrade. Start with a timeboxed pilot on one admin screen and expand only if it proves useful.

For engineering: It provides drop-in Filament form fields for alternative toggle/radio-style selection UX, reducing bespoke Livewire/Blade work. v3.0.0 is a major version: it targets Filament v4, so plan the upgrade as a coordinated change with your Filament bump rather than an isolated dependency update. Note that this is a breaking change with no announced deprecation path for v2.x—keep Filament v3 environments pinned to v2.0.9 until they migrate. The integration surface is small, the license is permissive, and the v4 work landed via an outside contributor, which slightly reduces single-maintainer risk on future platform upgrades.

Decision ask: Approve a short evaluation spike on one high-value admin form, run against whichever Filament major you are on (v3.0.0 for v4, v2.0.9 for v3). Measure implementation effort, compatibility, and user feedback before standardizing across the admin panel, and pin versions explicitly so a future major release cannot break forms silently.