typst-gather
Extracted from Quarto's CLI, typst-gather learned to explain a dependency tree before fetching it.
Comparison · Analytics
qualtRics vs waywiser
A side-by-side editorial comparison of qualtRics and waywiser — release velocity, themes, recent moves, and the top alternatives to consider.
Shared themes:r-package
qualtRics vs waywiser: at a glance
What is qualtRics?
qualtRics moved its contact functions onto XM Directory days before the old endpoints died.
qualtRics is the R client for the Qualtrics v3 API — fetching survey responses, definitions, distributions, and contact lists into tidy data frames. Version 3.3.0 migrated all_mailinglists() and fetch_mailinglist() from the deprecated Research Core Contacts endpoints to XM Directory, ahead of Qualtrics retiring the old ones on June 30, 2026. Authentication and directory discovery are handled automatically, but the new endpoints return a different data shape, so column names changed. Before that, releases had been steady maintenance for two years, mostly around how survey response archives are unpacked.
What is waywiser?
Spatial model assessment that spent the last year on cross-platform arithmetic and CRAN rules.
waywiser provides spatial model assessment metrics in a tidymodels idiom — spatial autocorrelation measures, area of applicability, and multi-scale assessment of predictions. The substantive work landed in 0.3.0 through 0.5.0, and the recent releases are consolidation: 0.6.0 made metric functions return NA everywhere they previously returned NaN, because macOS disagreed with every other platform, and taught ww_multi_scale() to handle classification and class probability metrics correctly when given rasters. The three releases since are entirely CRAN policy compliance — no internet downloads during checks, no writing to directories, no syntax that would raise the R version floor.
qualtRics vs waywiser: editorial side-by-side
qualtRics
0.0ANALYTICS
qualtRics moved its contact functions onto XM Directory days before the old endpoints died.
◆ Current state
qualtRics is the R client for the Qualtrics v3 API — fetching survey responses, definitions, distributions, and contact lists into tidy data frames. Version 3.3.0 migrated all_mailinglists() and fetch_mailinglist() from the deprecated Research Core Contacts endpoints to XM Directory, ahead of Qualtrics retiring the old ones on June 30, 2026. Authentication and directory discovery are handled automatically, but the new endpoints return a different data shape, so column names changed. Before that, releases had been steady maintenance for two years, mostly around how survey response archives are unpacked.
◆ Where it's heading
This package's roadmap is set by Qualtrics, not by its maintainers, and the release history reads as a sequence of accommodations — endpoint changes, retired APIs, and edge cases in exported files. The team's own recurring theme is reducing surprise: caching was removed from fetch_survey() in 3.2.0 so results are never stale, error handling was standardized on retry semantics, and column mappings were made inspectable via extract_colmap(). Feature additions, when they come, are new endpoints wrapped rather than new abstractions.
◆ Prediction
With the Contacts migration complete, the next likely work is bringing the remaining Research Core-era functions onto XM Directory equivalents before Qualtrics retires more of the old surface.
waywiser
0.0ANALYTICS
Spatial model assessment that spent the last year on cross-platform arithmetic and CRAN rules.
◆ Current state
waywiser provides spatial model assessment metrics in a tidymodels idiom — spatial autocorrelation measures, area of applicability, and multi-scale assessment of predictions. The substantive work landed in 0.3.0 through 0.5.0, and the recent releases are consolidation: 0.6.0 made metric functions return NA everywhere they previously returned NaN, because macOS disagreed with every other platform, and taught ww_multi_scale() to handle classification and class probability metrics correctly when given rasters. The three releases since are entirely CRAN policy compliance — no internet downloads during checks, no writing to directories, no syntax that would raise the R version floor.
◆ Where it's heading
The package has reached the point where the interesting bugs are cross-platform and cross-package rather than statistical. Its main function, ww_multi_scale(), has been the focus of nearly every release since 0.4.0, working through units handling, aggregation ordering, raster inputs and metric-type dispatch. The dependency on vip and the tidymodels metric machinery means a share of releases exist only to track breaking changes elsewhere.
◆ Prediction
Expect the next substantive release to continue on ww_multi_scale() edge cases, given that it has absorbed most of the fixes in this window. The recent run of CRAN-compliance patches suggests no feature work is currently in flight.
Alternatives to qualtRics and waywiser
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 qualtRics or waywiser.
naijR
naijR is assembling the Nigerian reference data R analysts otherwise hand-code every time.
RBesT
RBesT is teaching its Bayesian decision rules to answer two-sided questions.
graphicalMCP
graphicalMCP is a narrow statistical tool being hardened rather than grown.
rtflite
rtflite stopped being an RTF writer and became the conversion layer for clinical table output.
git2rdata
git2rdata keeps sharpening one idea: a data frame that produces a readable git diff.
See all qualtRics alternatives → · See all waywiser alternatives →
Recent activity from qualtRics and waywiser
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 1mo agoqualtRicsMailing list functions migrated to the XM Directory API ⚡
- 11mo agoqualtRicsZip extraction handles more special characters in survey titles
- 1y agowaywiserStops downloading data during CRAN checks
- 1y agowaywiserVignettes no longer write to CRAN directories
- 1y agowaywiserKeeps the R version floor below 4.1
- 1y agoqualtRicsFix for questions with both recoded values and variable naming
- 1y agoqualtRicsBuild and CI housekeeping alongside the 3.2.1 release
- 2y agowaywiserNaN results become NA; raster metrics dispatch correctly
- 2y agoqualtRicsSurvey response caching removed from fetch_survey()
- 2y agowaywiserGuards against ignored grid arguments; faster on sf data
- 2y agowaywiserFixes wrong observation counts and ignored grid units
- 3y agoqualtRicsArgument checking refactor and include_* NA fix
Frequently asked questions
What is the difference between qualtRics and waywiser?
Both compete on the same themes — r-package — within Analytics. qualtRics and waywiser are shipping at a similar cadence (velocity 0.0 vs 0.0, both within Sparkpulse's "active" band). See the at-a-glance table above for a side-by-side breakdown of velocity, recent sparks, and editorial themes.
Is qualtRics better than waywiser?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. qualtRics and waywiser are shipping at a similar cadence (velocity 0.0 vs 0.0, both within Sparkpulse's "active" band). For your specific use case, the alternatives sections above list other Analytics products to evaluate alongside.
What are the best alternatives to qualtRics?
Top qualtRics alternatives in Analytics are ranked by recent ship velocity. Browse the "qualtRics alternatives" section above for the current picks, or visit /alternatives/qualtrics for the full list with editorial commentary on each.
What are the best alternatives to waywiser?
Top waywiser alternatives in Analytics are ranked by recent ship velocity. Browse the "waywiser alternatives" section above for the current picks, or visit /alternatives/waywiser for the full list with editorial commentary on each.