pins
pins keeps adding a storage backend per release while retiring its original API
A side-by-side editorial comparison of Fulcrum and Trackingplan — release velocity, themes, recent moves, and the top alternatives to consider.
| Feature | Fulcrum | Trackingplan |
|---|---|---|
| Sector | Analytics | Analytics |
| Velocity score | 6.3 | 5.0 |
| Sparks · 30d | 0 | 0 |
| Top themes | field-data-collection, esri-arcgis, offline-maps, on-device-inference | analytics-governance, consent-monitoring, ai-debugging, data-quality |
| Last editorial update | 15h ago | 20d ago |
| Website | — | Visit → |
Fulcrum's mobile train is all Esri migration cleanup, with on-device inference quietly changing format.
Fulcrum ships iOS, Android, and web releases on a near-weekly cadence, and this stretch is dominated by mapping work following the Google Maps retirement announced for September. Recent builds upgraded to ArcGIS SDK 300.0.0, moved the web map engine to current ArcGIS and deck.gl versions, and worked through the resulting stability issues — basemap loading, location resolution, black map screens, panning and zooming performance. The most consequential change is easy to miss: ONNX support for on-device machine learning inference was removed in favor of a new INFERENCE format that reads labels from an uploaded labels.txt.
Trackingplan turns tracking-plan validation into AI-assisted, consent-aware observability.
Trackingplan monitors analytics implementations for drift and now anchors its workflow on two pillars: an AI Debugger that supplies root-cause analysis and recommended fixes, and Consent Monitoring that watches CMPs for privacy compliance. Recent releases connect these — deep links from charts into RCA and Data Explorer, shareable warning links, and consolidated troubleshooting views.
Fulcrum ships iOS, Android, and web releases on a near-weekly cadence, and this stretch is dominated by mapping work following the Google Maps retirement announced for September. Recent builds upgraded to ArcGIS SDK 300.0.0, moved the web map engine to current ArcGIS and deck.gl versions, and worked through the resulting stability issues — basemap loading, location resolution, black map screens, panning and zooming performance. The most consequential change is easy to miss: ONNX support for on-device machine learning inference was removed in favor of a new INFERENCE format that reads labels from an uploaded labels.txt.
This is a platform consolidation being paid down one point release at a time. Having committed to Esri, Fulcrum is absorbing the instability that came with it, and each release reads as fixes to symptoms of the same migration. Underneath, the offline and field-capture story continues to get real attention — downloaded offline map layers can now be updated in place, and Photo FastFill moved to background processing so it no longer blocks editing.
Expect the release notes to stay fix-dominated through the September Google Maps cutoff, with the migration-related map defects tapering after it passes. Photo FastFill leaving early access is the most likely next substantive item.
Trackingplan monitors analytics implementations for drift and now anchors its workflow on two pillars: an AI Debugger that supplies root-cause analysis and recommended fixes, and Consent Monitoring that watches CMPs for privacy compliance. Recent releases connect these — deep links from charts into RCA and Data Explorer, shareable warning links, and consolidated troubleshooting views.
The product is moving from passive tracking-plan validation toward active, guided remediation. Each release tightens the loop between detecting a problem (a warning, a consent gap) and resolving it — AI Debugger is spreading from generic warnings to consent warnings, and the UI is being rebuilt around single-surface investigation rather than scattered reports.
Expect AI Debugger to reach more warning types and Consent Monitoring to add further CMP integrations, continuing the pattern of extending both features to new surfaces rather than shipping a new pillar.
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 Fulcrum or Trackingplan.
pins keeps adding a storage backend per release while retiring its original API
tsibble shipped one release in five and a half years - the data structure is finished
yardstick made fairness metrics a first-class part of tidymodels evaluation
tune extends tuning past the model itself to postprocessors, and adds a second parallel backend
leaflet relicensed to MIT and finished migrating off R's retired spatial stack
ggpubr reached 1.0.0 with p-value formatting presets for specific journals
See all Fulcrum alternatives → · See all Trackingplan 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 5.0), with 0 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 5.0), with 0 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 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.
Top Trackingplan alternatives in Analytics are ranked by recent ship velocity. Browse the "Trackingplan alternatives" section above for the current picks, or visit /alternatives/trackingplan for the full list with editorial commentary on each.