rtflite
rtflite stopped being an RTF writer and became the conversion layer for clinical table output.
Comparison · Analytics
qualtRics vs xplainfi
A side-by-side editorial comparison of qualtRics and xplainfi — release velocity, themes, recent moves, and the top alternatives to consider.
qualtRics vs xplainfi: 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 xplainfi?
xplainfi treats feature importance as an estimate with error bars, not a number.
xplainfi implements feature importance methods for mlr3 — perturbation-based PFI, CFI and RFI, refit-based LOCO and WVIM, and SAGE. Its defining choice is that importance scores come with inference attached: several confidence-interval methods, including the Nadeau-Bengio correction and a distribution-free option added in 1.1.0. It declared itself released at 1.0.0 in January 2026.
qualtRics vs xplainfi: 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.
xplainfi
2.5ANALYTICS
xplainfi treats feature importance as an estimate with error bars, not a number.
◆ Current state
xplainfi implements feature importance methods for mlr3 — perturbation-based PFI, CFI and RFI, refit-based LOCO and WVIM, and SAGE. Its defining choice is that importance scores come with inference attached: several confidence-interval methods, including the Nadeau-Bengio correction and a distribution-free option added in 1.1.0. It declared itself released at 1.0.0 in January 2026.
◆ Where it's heading
Two lines of work run in parallel. The statistical side keeps adding inference options — variance corrections, conditional predictive impact, and the Lei et al. observation-wise loss-difference test — while the computational side attacks the cost of refit-based methods, most recently with a batch_size argument that parallelises refits and a default of one refit per resampling iteration. Support for pre-trained learners in 1.1.0 removes the refit requirement entirely in some workflows.
◆ Prediction
The stated reasoning that budget is better spent on resampling iterations than repeated refits suggests n_repeats may be removed from WVIM and LOCO outright, as the release notes hint.
Alternatives to qualtRics and xplainfi
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 xplainfi.
git2rdata
git2rdata keeps sharpening one idea: a data frame that produces a readable git diff.
osmextract
osmextract stopped throwing your OpenStreetMap downloads away at the end of every session.
nanoparquet
nanoparquet is chasing byte-level agreement with the Java and Rust Parquet readers, not feature count.
poissonreg
poissonreg gave its models away to parsnip and kept the glue — now it just keeps glmnet honest.
S7
S7 has stopped adding surface and started proving it holds up against R itself.
See all qualtRics alternatives → · See all xplainfi alternatives →
Recent activity from qualtRics and xplainfi
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 20d agoxplainfiRefits parallelise; repeated refits deprioritised in favour of resampling
- 1mo agoqualtRicsMailing list functions migrated to the XM Directory API ⚡
- 5mo agoxplainfiPre-trained learners supported; distribution-free inference added
- 6mo agoxplainfiVersion bumped to mark the package as released
- 9mo agoxplainfiConfidence intervals arrive for feature importance scores
- 11mo agoqualtRicsZip extraction handles more special characters in survey titles
- 1y agoqualtRicsFix for questions with both recoded values and variable naming
- 1y agoqualtRicsBuild and CI housekeeping alongside the 3.2.1 release
- 2y agoqualtRicsSurvey response caching removed from fetch_survey()
- 3y agoqualtRicsArgument checking refactor and include_* NA fix
Frequently asked questions
What is the difference between qualtRics and xplainfi?
They serve adjacent needs but don't currently overlap on shipped themes. xplainfi is currently shipping more aggressively (velocity 2.5 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 qualtRics better than xplainfi?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. xplainfi is currently shipping more aggressively (velocity 2.5 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 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 xplainfi?
Top xplainfi alternatives in Analytics are ranked by recent ship velocity. Browse the "xplainfi alternatives" section above for the current picks, or visit /alternatives/xplainfi for the full list with editorial commentary on each.