Filament Spark Pie Laravel Package

Product Decisions This Supports

• Admin dashboard & analytics roadmap: v2.0.0 adds Filament v3 support plus a spark pie component for Filament's new infolist builder, which moves this package from "dashboard widget only" to "record-level visual summary." That unlocks a concrete feature decision: surfacing at-a-glance distribution data (status mix, category split, quota usage) directly on a resource view page, not just on a top-level dashboard.
• Build vs buy for in-panel visualizations: the scope is deliberately narrow — a single compact pie/spark visual. The buy decision is cheap and reversible; building equivalent output in-house means maintaining chart config, theming, and Filament v3 upgrade churn that this package now absorbs for us.
• Upgrade sequencing: the v2.0.0 release is effectively a platform-alignment release (Filament v3). It gates our decision on when we can adopt it — it is only usable once our admin panel is on Filament v3, so it should be scheduled with, not ahead of, that migration.
• Use cases to validate in discovery: infolist "summary header" panels on Customer/Order/Subscription detail pages; compact distribution indicators where a full chart would crowd the layout; dashboards that need one more visual without adding a heavyweight charting dependency.
• Not a decision driver: no indication of export, drill-down, time-series, or accessibility features in this release. Do not let this package anchor a reporting/BI roadmap discussion.

When to Consider This Package

Consider it when all of the following hold:

• You are on, or actively migrating to, Filament v3 — v2.0.0 targets it and the release notes give no indication of dual support.
• Your need is a single compact pie/spark visual, either as a dashboard widget or embedded via the infolist builder.
• You want a low-ceremony, low-footprint addition and are comfortable with a small, single-maintainer open-source dependency in the admin surface (not the customer-facing critical path).
• You can pin the version and absorb an occasional breaking upgrade as part of your Filament upgrade cycle.

Look elsewhere when:

• You are staying on Filament v2 — treat v2.0.0 as a hard break and remain on the 0.0.x line, accepting that it is now unmaintained going forward.
• You need real charting: multi-series, time-series, tooltips, legends, export, or configurable axes. Use a mature chart wrapper (e.g. an ApexCharts/Chart.js Filament plugin) rather than stretching a spark visual past its purpose.
• You require vendor SLAs, security review artifacts, or long-term support commitments — nothing in this release suggests those exist.
• You need documented migration paths. The release notes are two bullet points with a raw changelog link and no upgrade guide; budget engineering time to verify behavior yourself.
• Version-number caution: the jump from 0.0.4 to 2.0.0 is almost certainly an alignment with Filament's major version rather than a signal of maturity. Do not read it as production-hardening, API stability, or a broad test/coverage story.

How to Pitch It (Stakeholders)

For executives (one paragraph): This is a small, free, open-source add-on that lets us draw a compact pie/spark visual inside our admin panel — either on dashboards or directly on a customer/order record page. The new version exists mainly because our admin framework (Filament) moved to v3, so this is a timing dependency, not new capability we have to go chase. The upside is presentational: faster, cheaper at-a-glance insight for internal users, with no new vendor contract and negligible cost. The risk is equally small but real — it is a niche, single-maintainer package, so we should treat it as a nice-to-have on internal screens and never let a critical workflow depend on it.

For engineering (the ask): v2.0.0 brings Filament v3 compatibility and a new spark pie component for the infolist builder. Before we adopt: (1) confirm our Filament version and pin the package accordingly — v2.0.0 is v3-only, so anyone on Filament v2 stays on 0.0.4; (2) there is no migration guide, deprecation list, or documented breaking-change detail beyond a compare link, so the "breaking change" is assumed by major-version bump — verify rendering on a branch; (3) assess the maintenance posture (single maintainer, two-line release note) and decide whether to vendor/fork if we adopt widely; (4) timebox a spike on one infolist page to confirm theming, dark mode, and responsive behavior before we commit it to a shipped feature.