tidytext
Finished, widely taught, and shipping roxygen fixes.
A side-by-side editorial comparison of Fulcrum and mlr3mbo — release velocity, themes, recent moves, and the top alternatives to consider.
| Feature | Fulcrum | mlr3mbo |
|---|---|---|
| Sector | Analytics | Analytics |
| Velocity score | 6.3 | 2.5 |
| Sparks · 30d | 0 | 0 |
| Top themes | field-data-collection, esri-arcgis, offline-maps, on-device-inference | bayesian-optimization, mlr3, hyperparameter-tuning, r-stats |
| Last editorial update | 18h ago | 1h 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.
mlr3mbo picked its defaults from a benchmark study, not from taste
mlr3mbo does model-based and Bayesian optimisation for mlr3. Its 1.0.0 release added a dictionary of pre-built acquisition-function optimisers and, more consequentially, replaced the default surrogate, acquisition function and optimiser settings with values derived from a large-scale benchmark study. The releases since are corrections to the acquisition-optimiser path exposed by that new default configuration.
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.
mlr3mbo does model-based and Bayesian optimisation for mlr3. Its 1.0.0 release added a dictionary of pre-built acquisition-function optimisers and, more consequentially, replaced the default surrogate, acquisition function and optimiser settings with values derived from a large-scale benchmark study. The releases since are corrections to the acquisition-optimiser path exposed by that new default configuration.
The package has moved from a toolkit that expected users to assemble a Bayesian optimisation loop into one with a defensible default loop, and the recent fixes — warm-start sizing on multi-objective archives, silently discarded terminators, stale x_domain values — are the consequences of more people running the default path.
Expect continued hardening of the acquisition-optimiser classes rather than new acquisition functions.
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 mlr3mbo.
Finished, widely taught, and shipping roxygen fixes.
Text features finally stay sparse all the way to the model.
The package that made calibration a step instead of an afterthought.
workflowsets keeps widening what counts as a model worth comparing.
The tidymodels pipeline grew a third stage, and it happens after the model runs.
Posit's MLOps package went quiet for two years, then came back to keep up with recipes.
See all Fulcrum alternatives → · See all mlr3mbo 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 2.5), 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 2.5), 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 mlr3mbo alternatives in Analytics are ranked by recent ship velocity. Browse the "mlr3mbo alternatives" section above for the current picks, or visit /alternatives/mlr3mbo for the full list with editorial commentary on each.