tidytext
Finished, widely taught, and shipping roxygen fixes.
Comparison · Analytics
Displayr vs probably
A side-by-side editorial comparison of Displayr and probably — release velocity, themes, recent moves, and the top alternatives to consider.
Displayr vs probably: at a glance
What is Displayr?
Chat is being made legible while the survey-analysis core picks up the fundamentals it lacked.
Displayr is shipping on two fronts at a steady, unhurried cadence. The AI assistant is being made auditable rather than more capable — a context pill showing exactly what a prompt will send, a change summary listing every item Chat added, edited or deleted, and an Explain This button that routes errors and warnings into Chat with context attached. Separately the document core is filling in fundamentals: controls that stay synced across pages and page masters, rolling averages computed on date-keyed tables, browser-style back and forward navigation, and templates that can be saved as folder-scoped defaults.
What is probably?
The package that made calibration a step instead of an afterthought.
probably started as a small utility for class predictions and equivocal zones, and version 1.0.0 turned it into tidymodels' calibration and uncertainty package: cal_plot_*, cal_estimate_*, cal_validate_* and cal_apply across binary, multiclass and regression problems, plus conformal prediction intervals. Since then the work has been consolidation — a large internal refactor with no API change, split conformal and conformal quantile regression, bound_prediction(), and required_pkgs() and butcher methods so conformal objects can be deployed and stripped.
Displayr vs probably: editorial side-by-side
Displayr
5.0ANALYTICS
Chat is being made legible while the survey-analysis core picks up the fundamentals it lacked.
◆ Current state
Displayr is shipping on two fronts at a steady, unhurried cadence. The AI assistant is being made auditable rather than more capable — a context pill showing exactly what a prompt will send, a change summary listing every item Chat added, edited or deleted, and an Explain This button that routes errors and warnings into Chat with context attached. Separately the document core is filling in fundamentals: controls that stay synced across pages and page masters, rolling averages computed on date-keyed tables, browser-style back and forward navigation, and templates that can be saved as folder-scoped defaults.
◆ Where it's heading
The Chat work reads as a deliberate answer to the trust problem with AI in analyst tools — every release makes what the assistant touched inspectable rather than expanding what it can do unprompted. The other track is closing gaps a long-standing survey analysis platform accumulates, with the default-template mechanic notable for scoping defaults by Cloud Drive folder, which turns a personal preference into an organizational standard. Neither track has produced a directional move in this window.
◆ Prediction
Expect the transparency pattern to extend to Chat actions that modify data rather than layout, since the change summary establishes the mechanism. Folder-scoped defaults look like the start of broader template governance.
probably
0.0ANALYTICS
The package that made calibration a step instead of an afterthought.
◆ Current state
probably started as a small utility for class predictions and equivocal zones, and version 1.0.0 turned it into tidymodels' calibration and uncertainty package: cal_plot_*, cal_estimate_*, cal_validate_* and cal_apply across binary, multiclass and regression problems, plus conformal prediction intervals. Since then the work has been consolidation — a large internal refactor with no API change, split conformal and conformal quantile regression, bound_prediction(), and required_pkgs() and butcher methods so conformal objects can be deployed and stripped.
◆ Where it's heading
The recent releases are about making these objects survive leaving the session. butcher and required_pkgs() methods are what a model needs to be pinned, containerised and served, and their arrival alongside workflows adding a tailor postprocessing stage and vetiver adding probably support points the same way: calibration is being moved out of analysis scripts and into the deployed pipeline. The cal_*_none() reference implementations are the tell that calibration is now something people tune rather than apply once.
◆ Prediction
Expect the calibration functions to be reachable directly from a tuned workflow's postprocessing stage rather than applied to predictions afterwards, following the tailor integration that workflows just shipped.
Alternatives to Displayr and probably
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 Displayr or probably.
textrecipes
Text features finally stay sparse all the way to the model.
workflowsets
workflowsets keeps widening what counts as a model worth comparing.
workflows
The tidymodels pipeline grew a third stage, and it happens after the model runs.
vetiver
Posit's MLOps package went quiet for two years, then came back to keep up with recipes.
patchwork
patchwork stopped being a ggplot composer and became a page composer.
See all Displayr alternatives → · See all probably alternatives →
Recent activity from Displayr and probably
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 22h agoDisplayrUse the Same Control Across Multiple Pages and Page Masters
- 22h agoDisplayrRolling Averages Computed Automatically on Tables
- 16d agoDisplayrExplain This — AI help for errors & warnings
- 16d agoDisplayrBack and Forward Buttons for Navigation
- 16d agoDisplayrSave Templates as Default Visualizations
- 1mo agoDisplayrMore transparency when working with Chat
- 10mo agoprobablyConformal objects gain required_pkgs() and butcher methods
- 1y agoprobablyggplot2 test updates and a clearer validation-set error
- 1y agoprobablyCalibration internals refactored; isotonic bootstrap bug fixed
- 2y agoprobablyFix grouping sensitivity to variable type
- 3y agoprobablySplit conformal and conformal quantile regression added
- 3y agoprobablyCalibration and conformal inference arrive in tidymodels ⚡
Frequently asked questions
What is the difference between Displayr and probably?
They serve adjacent needs but don't currently overlap on shipped themes. Displayr is currently shipping more aggressively (velocity 5.0 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 Displayr better than probably?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. Displayr is currently shipping more aggressively (velocity 5.0 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 Displayr?
Top Displayr alternatives in Analytics are ranked by recent ship velocity. Browse the "Displayr alternatives" section above for the current picks, or visit /alternatives/displayr for the full list with editorial commentary on each.
What are the best alternatives to probably?
Top probably alternatives in Analytics are ranked by recent ship velocity. Browse the "probably alternatives" section above for the current picks, or visit /alternatives/probably for the full list with editorial commentary on each.