Filament Rating Laravel Package

Product Decisions This Supports

• Build vs. buy for rating capture UX. This package turns a recurring, deceptively fiddly UI pattern (star rating input, validation, persistence, display) into an installed dependency. The decision it informs is whether your team hand-rolls rating widgets in every Filament admin panel or standardizes on a small, focused plugin.
• Feature scoping for feedback and review surfaces. RatingInputColumn (v0.2.0) means ratings can be captured inline from a table row without opening an edit form — a meaningful workflow decision for moderation queues, support triage, and QA scoring screens. Ask whether inline rating capture replaces a full edit-page flow in your next iteration.
• Roadmap sequencing for review/feedback features. The 0.2.0 additions map cleanly onto a feature ladder: capture (RatingInputColumn) → interpretation (labels()) → visual signal (colors()) → segmentation (RatingFilter with exact()) → reporting (RatingDistribution with counts/percentages()). This gives a PM a credible phased roadmap where each phase is a config change, not a build.
• Accessibility investment without a dedicated workstream. labels() are announced by screen readers and shown on hover. That is an accessibility and clarity win that would otherwise need design and QA time. It supports the decision to ship rating capture earlier rather than deferring for an a11y pass.
• Admin analytics without a BI dependency. RatingDistribution with percentages() delivers a ratings breakdown inside the panel, which can defer or shrink the scope of an external dashboarding request — a genuine cost-avoidance decision.
• Product language decisions. Defining a word per rating via labels() is a product-content decision (what does 3 stars mean to us?), and this package makes that vocabulary reusable across input, display, filter, and summarizer. Worth a short PM/design sign-off rather than leaving it to engineering defaults.
• Use cases worth evaluating: customer satisfaction capture, supplier/vendor scoring, content quality review, support ticket prioritization, internal QA checklists, marketplace seller ratings in an ops console.

When to Consider This Package

Adopt when:

• Your admin/back-office is built on Filament. This is a Filament plugin, not a general Laravel package — without Filament there is nothing to adopt here, and that dependency should be confirmed before any evaluation time is spent.
• You need star ratings in forms, tables, filters, and summary views and want one consistent vocabulary (labels(), colors()) across all four.
• You want inline rating capture in list views where a full edit form is friction — moderation, triage, and review queues.
• Accessibility and localization of rating meaning matter, and you'd rather configure labels than build a component.
• You value a small, single-purpose dependency over a broad reviews/sentiment suite you'd only use 10% of.

Look elsewhere or defer when:

• No Filament in the stack. Evaluate general Livewire/Blade rating components or a custom implementation instead.
• You need reviews as a product domain, not a widget: threaded review bodies, media attachments, moderation state machines, spam detection, verified-purchase logic, sentiment analysis. This package captures and summarizes a number; it does not model a review.
• Pre-1.0 API stability is a blocker. v0.2.0 is early. Method names (clearable(), disabled(), exact(), percentages(), showLabel()) may still move. Acceptable for internal admin tooling; riskier if you're exposing it through a public or partner-facing surface.
• You need weighting, multi-criteria ratings (e.g. separate shipping/product/support scores rolled up), or statistical aggregation like Bayesian averages. Not indicated in this release.
• Governance constraints — no third-party plugins, or vendor review required. A plugin adds a maintenance and supply-chain line item; a small internal component may clear review faster.
• Ratings are business-critical and need SLAs or audit trails. Prefer a first-party component you control.

How to Pitch It (Stakeholders)

For executives (one paragraph): We identified a small, low-cost Filament plugin that gives us star ratings across our admin tooling — capture, display, filtering, and summary charts — without a build. Release 0.2.0 is a substantial step up: ratings can now be set directly from a table row, star meanings can carry our own wording and colors, and we get a "4 stars and up" filter and a distribution breakdown out of the box. The commercial case is speed and avoided cost: this replaces custom component work in several screens and removes a UI detail that teams routinely underestimate. The trade-off is maturity — this is a pre-1.0 package, so it suits internal operational surfaces well and public-facing or regulated surfaces less well.

For engineering: Small, focused dependency; the 0.2.0 surface is RatingInputColumn, labels(), colors(), RatingFilter (including exact()), and RatingDistribution (counts or percentages()), with summarizers inheriting the column's labels and colors — so a single configuration point keeps capture and reporting consistent. It's a Filament plugin, so scope is confined to panels already on Filament. Note it's pre-1.0: pin the version, wrap usage thinly so a rename is a one-file change, and budget for occasional upgrade churn rather than assuming API stability.

For design and content: labels() makes rating meaning a configurable, reusable product decision rather than a hardcoded string — one word per rating, applied consistently to the field, the display, and the summarizer, and announced to screen readers. That's a genuine accessibility and clarity gain for very little effort. Worth a short session to agree the vocabulary and the colors() thresholds before we ship.

Recommendation: Trial on one internal Filament panel, pinned to v0.2.0, with a thin wrapper around the components. Reassess at 1.0 or once two or three screens depend on it.