← Back to home
Comparison · Analytics

Fulcrum vs textrecipes

A side-by-side editorial comparison of Fulcrum and textrecipes — release velocity, themes, recent moves, and the top alternatives to consider.

Fulcrum vs textrecipes: at a glance

FeatureFulcrumtextrecipes
SectorAnalyticsAnalytics
Velocity score6.30.0
Sparks · 30d00
Top themesfield-data-collection, esri-arcgis, offline-maps, on-device-inferencetext-processing, tidymodels, recipes, sparse-data
Last editorial update18h ago52m ago
WebsiteVisit →

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.

Read the full Fulcrum trajectory →

What is textrecipes?

Text features finally stay sparse all the way to the model.

textrecipes supplies the recipes steps for turning text into model-ready columns: tokenizing, hashing, term frequency, TF-IDF, and word embeddings. Version 1.1.0 added a sparse argument to step_dummy_hash(), step_texthash(), step_tf() and step_tfidf() so they emit sparse vectors. The releases before it are a long consistency pass — keep_original_cols on every step that creates columns, informative errors on name collisions, tunable arguments documented, integer rather than double output where integers are what is meant.

Read the full textrecipes trajectory →

Fulcrum vs textrecipes: editorial side-by-side

F
Fulcrum
ANALYTICS
6.3

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.

T
textrecipes
ANALYTICS
0.0

Text features finally stay sparse all the way to the model.

◆ Current state

textrecipes supplies the recipes steps for turning text into model-ready columns: tokenizing, hashing, term frequency, TF-IDF, and word embeddings. Version 1.1.0 added a sparse argument to step_dummy_hash(), step_texthash(), step_tf() and step_tfidf() so they emit sparse vectors. The releases before it are a long consistency pass — keep_original_cols on every step that creates columns, informative errors on name collisions, tunable arguments documented, integer rather than double output where integers are what is meant.

◆ Where it's heading

Two forces drive this package. One is memory: text produces wide, mostly-zero matrices, and the sparse work is the direct answer, landing in the same period that workflows learned to fit and predict on dgCMatrix input. The other is upstream churn — the tweets tokenizer was deprecated because tokenizers deprecated it, the politeness feature disappeared when textfeatures left Suggests. The package's own agenda is consistency; its release timing belongs to its dependencies.

◆ Prediction

Expect the sparse argument to spread to the remaining column-producing steps, since only four of them have it, and expect more steps to be reworked as recipes' own sparse-data support matures.

Alternatives to Fulcrum and textrecipes

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 textrecipes.

See all Fulcrum alternatives → · See all textrecipes alternatives →

Recent activity from Fulcrum and textrecipes

Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.

  1. 1d agoFulcrumAndroid: update offline map layers in place, non-blocking Photo FastFill
  2. 2d agoFulcrumiOS fix: slow location resolution blocked record saves
  3. 6d agoFulcrumWeb: SSO email wording and ArcGIS/deck.gl version bumps
  4. 8d agoFulcrumAndroid fixes: ArcGIS stability, signature button, photo markup
  5. 8d agoFulcrumiOS fixes: basemap loading and black map screen
  6. 9d agoFulcrumiOS: ArcGIS SDK 300.0.0 and ONNX replaced by a new INFERENCE format
  7. 1y agotextrecipesHashing and TF-IDF steps can emit sparse vectors
  8. 1y agotextrecipesstep_textfeatures() sped up; clean_levels NA bug fixed
  9. 2y agotextrecipestextfeatures dependency dropped; politeness feature removed
  10. 2y agotextrecipesuntokenize and normalization return factors
  11. 2y agotextrecipeskeep_original_cols everywhere; hashing column order fixed
  12. 3y agotextrecipesTunable arguments documented; name collisions now error

Frequently asked questions

What is the difference between Fulcrum and textrecipes?

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 textrecipes?

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 textrecipes?

Top textrecipes alternatives in Analytics are ranked by recent ship velocity. Browse the "textrecipes alternatives" section above for the current picks, or visit /alternatives/textrecipes for the full list with editorial commentary on each.