RMVMR
RMVMR is being tidied in lockstep with MVMR, the package it wraps
A side-by-side editorial comparison of Fulcrum and shapviz — release velocity, themes, recent moves, and the top alternatives to consider.
| Feature | Fulcrum | shapviz |
|---|---|---|
| Sector | Analytics | Analytics |
| Velocity score | 6.3 | 0.0 |
| Sparks · 30d | 0 | 0 |
| Top themes | gis, esri-migration, offline-maps, field-data-capture | shap, visualization, model explainability, ggplot2 |
| Last editorial update | 7h ago | 1h ago |
| Website | — | Visit → |
Fulcrum is betting its whole map stack on Esri, with a hard Google Maps cutoff on September 1.
Fulcrum is a field data collection platform, and nearly every entry in the last month touches mapping. The web app ships weekly fix batches for layer rendering (KML/KMZ, MBTiles, ArcGIS Feature Services), while iOS and Android push near-weekly builds against the ArcGIS SDK. Feature work is thin right now; the visible surface is stabilization around a mapping engine migration already in flight.
shapviz refines its SHAP plots release by release while chasing ggplot2's moving target.
shapviz turns SHAP values from XGBoost, LightGBM, H2O, kernelshap and other sources into standard diagnostic plots — importance, dependence, waterfall, force and interaction. Recent work is plot ergonomics: shared y-axis control across dependence plots, a bar view for interaction values, and axis collection via patchwork. The two most recent releases are pure compatibility and bug fixes.
Fulcrum is a field data collection platform, and nearly every entry in the last month touches mapping. The web app ships weekly fix batches for layer rendering (KML/KMZ, MBTiles, ArcGIS Feature Services), while iOS and Android push near-weekly builds against the ArcGIS SDK. Feature work is thin right now; the visible surface is stabilization around a mapping engine migration already in flight.
The direction is a full consolidation onto Esri. The legacy Google Maps engine is being retired on September 1 with automatic migration for anyone who hasn't switched, and Esri now carries Google's satellite and street basemaps so the imagery argument is neutralized. Underneath, the mobile SDK moved to ArcGIS 300.0.0 and ONNX on-device inference was dropped for a new INFERENCE format with labels.txt support. Offline is the second thread: downloadable layers can now be updated in place rather than deleted and recreated.
Expect the weeks before September 1 to stay dominated by migration-shaped fixes and Esri feature parity work, with the MMPK layer and Photo FastFill early-access programs the most likely to graduate to general availability next.
shapviz turns SHAP values from XGBoost, LightGBM, H2O, kernelshap and other sources into standard diagnostic plots — importance, dependence, waterfall, force and interaction. Recent work is plot ergonomics: shared y-axis control across dependence plots, a bar view for interaction values, and axis collection via patchwork. The two most recent releases are pure compatibility and bug fixes.
Two threads run in parallel here. One is visual refinement converging on conventions from Python's shap — the 0.10.0 notes openly float switching share_y to TRUE to match it. The other is connector maintenance, keeping pace with H2O, XGBoost 1.x and 2.x, shapr and permshap as each changes. Neither thread adds new explanation methods; shapviz's job is presentation, and it is being polished rather than extended.
Expect share_y = TRUE to become the default and further ggplot2 4.x fallout, with connector updates arriving as the upstream SHAP packages release.
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 shapviz.
RMVMR is being tidied in lockstep with MVMR, the package it wraps
geoarrow tracks the GeoArrow spec and otherwise just keeps compiling
n2khab keeps retracting interpretations of habitat data it can't actually support
tidypolars is grinding toward complete dplyr coverage, one supported function at a time
OneSampleMR found that argument order in a formula was silently changing its estimates
bpbounds found the same swapped-cell bug twice and clamped its bounds back into range
See all Fulcrum alternatives → · See all shapviz 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 shapviz alternatives in Analytics are ranked by recent ship velocity. Browse the "shapviz alternatives" section above for the current picks, or visit /alternatives/shapviz for the full list with editorial commentary on each.