pins
pins keeps adding a storage backend per release while retiring its original API
A side-by-side editorial comparison of Fulcrum and ggpubr — release velocity, themes, recent moves, and the top alternatives to consider.
| Feature | Fulcrum | ggpubr |
|---|---|---|
| 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 | visualization, statistics, publication, ggplot2 |
| Last editorial update | 15h ago | 48m 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.
ggpubr reached 1.0.0 with p-value formatting presets for specific journals
ggpubr adds publication-ready statistics and annotation to ggplot2. Two releases define its capability: 0.5.0 introduced the stat_*_test family and geom_pwc() for pairwise comparison brackets, and 1.0.0 added p-value formatting presets matching named journal house styles. In between, most releases are ggplot2 and dplyr deprecation chasing.
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.
ggpubr adds publication-ready statistics and annotation to ggplot2. Two releases define its capability: 0.5.0 introduced the stat_*_test family and geom_pwc() for pairwise comparison brackets, and 1.0.0 added p-value formatting presets matching named journal house styles. In between, most releases are ggplot2 and dplyr deprecation chasing.
The package is moving from drawing statistics to matching the conventions of where they get published - style presets are a different kind of feature from a new test. That sits on a persistent maintenance load: after_stat migrations, linewidth parameters, R-devel changing how the Wilcoxon test handles ties. ggpubr absorbs upstream deprecations so that figure code written years ago keeps rendering.
Expect the preset list to grow as users request their own journals' conventions, and the deprecation-chasing to continue with each ggplot2 release; the statistical test coverage looks complete enough that additions there would be surprising.
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 ggpubr.
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
bigrquery went MIT, then handed its slowest path to the BigQuery Storage API
See all Fulcrum alternatives → · See all ggpubr 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 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 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.
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 ggpubr alternatives in Analytics are ranked by recent ship velocity. Browse the "ggpubr alternatives" section above for the current picks, or visit /alternatives/ggpubr for the full list with editorial commentary on each.