billboarder
An htmlwidget whose release notes are mostly billboard.js version bumps, quiet since 2021.
Comparison · Analytics
Fulcrum vs pins
A side-by-side editorial comparison of Fulcrum and pins — release velocity, themes, recent moves, and the top alternatives to consider.
Fulcrum vs pins: at a glance
| Feature | Fulcrum | pins |
|---|---|---|
| Sector | Analytics | Analytics |
| Velocity score | 6.3 | 0.0 |
| Sparks · 30d | 0 | 0 |
| Top themes | field-data-collection, esri-arcgis, offline-maps, on-device-inference | data-versioning, cloud-storage, databricks, serialization |
| Last editorial update | 15h ago | 50m ago |
| Website | — | Visit → |
What is Fulcrum?
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.
What is pins?
pins keeps adding a storage backend per release while retiring its original API
pins publishes and versions R objects to a board, where a board is whatever storage you have. The recent releases read as a steady list of new boards - Google Cloud Storage, Google Drive, Databricks Volumes, Connect vanity URLs - alongside serialization changes that track which formats R users actually want: parquet via nanoparquet, and qs replaced by qs2.
Fulcrum vs pins: editorial side-by-side
Fulcrum
6.3ANALYTICS
Fulcrum's mobile train is all Esri migration cleanup, with on-device inference quietly changing format.
◆ Current state
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.
◆ Where it's heading
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.
◆ Prediction
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.
pins
0.0ANALYTICS
pins keeps adding a storage backend per release while retiring its original API
◆ Current state
pins publishes and versions R objects to a board, where a board is whatever storage you have. The recent releases read as a steady list of new boards - Google Cloud Storage, Google Drive, Databricks Volumes, Connect vanity URLs - alongside serialization changes that track which formats R users actually want: parquet via nanoparquet, and qs replaced by qs2.
◆ Where it's heading
Two long-running processes, neither dramatic. Backend coverage expands toward wherever teams already store artifacts, which increasingly means Databricks and cloud object storage rather than a shared drive. Meanwhile the legacy pin() API from before the board model has been in a staged deprecation across at least three releases, escalated each time rather than removed.
◆ Prediction
Expect another board or two as storage platforms are requested, and the legacy pin() functions to finally become errors; the format list will keep tracking whichever serializer the R community settles on.
Alternatives to Fulcrum and pins
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 pins.
bbotk
bbotk is generalizing from an optimizer toolkit into an evaluation framework.
bayesplot
bayesplot keeps widening its posterior-check catalogue while absorbing each ggplot2 break.
animation
Contribution-driven maintenance on a package whose last structural change was magick support.
tsibble
tsibble shipped one release in five and a half years - the data structure is finished
yardstick
yardstick made fairness metrics a first-class part of tidymodels evaluation
See all Fulcrum alternatives → · See all pins alternatives →
Recent activity from Fulcrum and pins
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 23h agoFulcrumAndroid: update offline map layers in place, non-blocking Photo FastFill
- 1d agoFulcrumiOS fix: slow location resolution blocked record saves
- 6d agoFulcrumWeb: SSO email wording and ArcGIS/deck.gl version bumps
- 7d agoFulcrumAndroid fixes: ArcGIS stability, signature button, photo markup
- 7d agoFulcrumiOS fixes: basemap loading and black map screen
- 8d agoFulcrumiOS: ArcGIS SDK 300.0.0 and ONNX replaced by a new INFERENCE format
- 5mo agopinsqs2 replaces qs; pins can be written in multiple formats
- 1y agopinsPin previews on Connect; Databricks host normalization
- 1y agopinsAdds board_databricks() and switches parquet to nanoparquet
- 2y agopinspin_write() arguments must be named; Connect caches removed
- 2y agopinsMessage clarity and Google Drive dribble handling
- 2y agopinsboard_gdrive() added; cache location configurable
Frequently asked questions
What is the difference between Fulcrum and pins?
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 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.
Is Fulcrum better than pins?
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 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.
What are the best alternatives to Fulcrum?
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.
What are the best alternatives to pins?
Top pins alternatives in Analytics are ranked by recent ship velocity. Browse the "pins alternatives" section above for the current picks, or visit /alternatives/pins-r for the full list with editorial commentary on each.