Filament Echarts Laravel Package

Product Decisions This Supports

• Analytics/reporting roadmap: Informs whether the next dashboard iteration ships with Filament's native Chart.js widgets or a richer charting layer. ECharts unlocks chart types Filament does not offer out of the box — heatmaps, Sankey, candlestick, radar, gauge, treemap, geo maps, and large-series line/bar with dataZoom and brush selection.
• Build vs. buy (vs. assemble): Frames charting as a commodity integration rather than bespoke work. The package is MIT-licensed and thin, so the real decision is "adopt, vendor, or fork" — not "license or build."
• Feature-level use cases: Operations dashboards (throughput, funnel, cohort heatmaps), finance views (candlesticks, waterfall-style comparisons), geo/regional breakdowns, and dense time-series where native widgets choke or lack zoom/pan.
• Standardization call: Whether to standardize all admin-panel visualization on one charting engine. Mixing Chart.js and ECharts raises theming, dark-mode, and accessibility inconsistency — a design-system decision, not just a library pick.
• Maintenance/risk budgeting: With ~15 stars and 0 dependents, this is a source dependency, not a strategic platform bet. That drives a roadmap decision: allocate a small spike + fork-and-own contingency before committing to it in a customer-facing surface.
• Localization and UX parity: ECharts ships strong i18n, tooltip, and export (image) behavior — relevant if the roadmap includes non-English admin users or "download chart" asks.
• Sellable differentiator: Richer, interactive dashboards can be positioned as a plan-tier feature (advanced analytics) rather than table-stakes admin tooling.

When to Consider This Package

Consider it when:

• The product already runs Filament v3+ on Laravel and dashboard work is happening inside the admin panel, not a separate SPA.
• You need chart types Filament's native widgets can't express (heatmap, Sankey, geo, treemap, candlestick, gauge) or interaction beyond static tooltips (zoom, brush, legend toggling on large series).
• You need performance at scale — thousands of points per series — where a Canvas-based engine like ECharts materially outperforms the default.
• Your team is comfortable owning a small integration: reading/writing Blade + Alpine + a config array, and forking under MIT if the maintainer goes quiet.
• Time-to-value matters more than vendor support: a working dashboard in days, no license cost, no procurement.

Look elsewhere when:

• You are not on Filament (or on a Filament version the package doesn't target) — the integration value collapses to "just use echarts directly."
• Chart.js widgets are sufficient. Standard bar/line/pie/doughnut dashboards don't justify a second charting engine, extra JS payload, and a second theming system.
• You require a supported vendor, SLA, security review, or audited release cadence. 15 stars, 0 dependents, and a single maintainer fail most enterprise procurement gates.
• You need server-side rendering for PDF/email reports. Verify whether the package renders client-side only; ECharts SSR requires a Node/headless path this package likely doesn't provide.
• Your charts must be accessible-first (screen-reader tables, WCAG-compliant fallbacks) — Canvas-rendered charts need deliberate remediation work regardless of library.

Adoption gate (recommended): a 1–2 day spike covering install, one heatmap, dark mode, and a mobile viewport. Proceed only if it passes and you accept a fork-maintenance line item.

How to Pitch It (Stakeholders)

For executives (one paragraph):

We can add advanced, interactive analytics to the admin product without new license spend or a front-end rewrite. Apache ECharts is a mature, widely deployed open-source charting engine; this package wires it into Filament, the framework our admin panel already uses. The realistic outcome is richer dashboards — heatmaps, geo breakdowns, zoomable time series — delivered in days rather than a quarter. The caveat is maturity: the integration is small and MIT-licensed, so we should treat it as code we're willing to own, budget a short validation spike, and keep a fork path. Low cost, low lock-in, real upside on the analytics roadmap; the main risk is maintenance attention, not money.

For engineering:

Thin MIT wrapper exposing ECharts option arrays as Filament widgets. Upside: Canvas rendering, huge chart-type coverage, dataZoom/brush, solid theming hooks, no license friction. Downsides: low adoption (≈15 stars, 0 dependents), single maintainer, so pin the version and be ready to vendor the Blade/Alpine glue. Ask before adopting: does it support our Filament version, does it handle dark mode and asset loading via Vite, and how does it behave with 5k+ points?

For design/product owners:

Expect a visible step up in dashboard expressiveness and interactivity. Trade-off: a second charting engine alongside Filament's built-in charts means we should align colors, typography, and empty states deliberately, and define an accessibility fallback (data table or summary) for Canvas charts.