ApexCharts
ApexCharts built a paid tier in three releases, then started enforcing it
A side-by-side editorial comparison of billboard.js and Fulcrum — release velocity, themes, recent moves, and the top alternatives to consider.
| Feature | billboard.js | Fulcrum |
|---|---|---|
| Sector | Analytics | Analytics |
| Velocity score | 0.0 | 6.3 |
| Sparks · 30d | 0 | 1 |
| Top themes | charting, canvas-rendering, tree-shaking, pre-release-train | field-data-collection, gis, esri-integration, mobile-apps |
| Last editorial update | 1h ago | 3d ago |
| Website | Visit → | — |
billboard.js is adding a canvas renderer — an SVG chart library admitting SVG has a ceiling.
The library is mid-flight on a 4.0.0 pre-release train, and the defining addition is a canvas rendering mode alongside the existing SVG output. The same first candidate made grid, regions and category modules tree-shakable, added file extensions to type declarations, and exported shape option types from the main entry. Everything published since has been canvas follow-up: background image positioning, rendering and touch-interaction parity, candlestick labels aligned to wick endpoints.
Fulcrum is retiring Google Maps and betting its field app entirely on Esri.
Fulcrum's field data collection platform is mid-consolidation onto a single mapping engine. The legacy Google Maps engine retires on September 1, 2026, and any organization still defaulting to it on web or mobile will be switched to Esri Maps automatically; Google's satellite, hybrid, and street basemaps survive as options in the Esri layer picker. Everything else this cycle is routine — weekly web release notes covering map layer and billing fixes, and phased mobile releases addressing stability, offline symbology, and KML display.
The library is mid-flight on a 4.0.0 pre-release train, and the defining addition is a canvas rendering mode alongside the existing SVG output. The same first candidate made grid, regions and category modules tree-shakable, added file extensions to type declarations, and exported shape option types from the main entry. Everything published since has been canvas follow-up: background image positioning, rendering and touch-interaction parity, candlestick labels aligned to wick endpoints.
Two constraints are being addressed at once. Canvas is the answer to dataset sizes where per-point DOM nodes stop being viable, and the fact that three consecutive candidates are spent on parity fixes shows how much behaviour an SVG-native library has to re-implement to make the alternative renderer feel identical. Tree-shakable modules attack the other constraint — bundle weight — which matters to exactly the same teams choosing a chart library on performance grounds.
Expect further candidates before 4.0.0 stable, still weighted toward canvas parity in interaction and label placement, since that is where every candidate so far has landed.
Fulcrum's field data collection platform is mid-consolidation onto a single mapping engine. The legacy Google Maps engine retires on September 1, 2026, and any organization still defaulting to it on web or mobile will be switched to Esri Maps automatically; Google's satellite, hybrid, and street basemaps survive as options in the Esri layer picker. Everything else this cycle is routine — weekly web release notes covering map layer and billing fixes, and phased mobile releases addressing stability, offline symbology, and KML display.
The Esri consolidation buys capabilities the Google engine could not offer: line and polygon snapping, GPS tracks with background tracking, offline basemaps, a redesigned mobile Location Editor, and direct connectivity to ArcGIS Online and Enterprise feature service layers. That positions Fulcrum as an ArcGIS-adjacent field client rather than a general mobile forms tool. The release cadence is high but the substance is thin between the engine migration and a steady drip of fixes.
Expect migration prompts and default-switch warnings to escalate through August as the deadline approaches, and MMPK layer support to leave early access once Esri is the only engine to support it on.
Other Analytics products tracked by Sparkpulse, ranked by recent ship velocity. Each card links to a full editorial trajectory and lets you pivot into a head-to-head comparison with either billboard.js or Fulcrum.
ApexCharts built a paid tier in three releases, then started enforcing it
Citus keeps three Postgres branches alive while chasing each new major
Three releases in a year, all of them about the Vega dependency — the feed shows nothing else.
Kylin ships once a year with empty release notes and a native engine nobody is being told about.
Iceberg's release cadence is now backports and CVE patches across three live minor lines.
Feature releases every two months in 2024; one bugfix release in the last twelve.
See all billboard.js alternatives → · See all Fulcrum alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. Fulcrum is currently shipping more aggressively (velocity 6.3 vs 0.0), with 1 editorial sparks in the last 30 days against 0. See the at-a-glance table above for a side-by-side breakdown of velocity, recent sparks, and editorial themes.
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. Fulcrum is currently shipping more aggressively (velocity 6.3 vs 0.0), with 1 editorial sparks in the last 30 days against 0. For your specific use case, the alternatives sections above list other Analytics products to evaluate alongside.
Top billboard.js alternatives in Analytics are ranked by recent ship velocity. Browse the "billboard.js alternatives" section above for the current picks, or visit /alternatives/billboard-js for the full list with editorial commentary on each.
Top Fulcrum alternatives in Analytics are ranked by recent ship velocity. Browse the "Fulcrum alternatives" section above for the current picks, or visit /alternatives/fulcrum for the full list with editorial commentary on each.