← Back to home
Comparison · Analytics

qualtRics vs ymlthis

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

qualtRics vs ymlthis: at a glance

FeaturequaltRicsymlthis
SectorAnalyticsAnalytics
Velocity score0.00.0
Sparks · 30d00
Top themessurvey-data, api-client, qualtrics, ropenscir-markdown, yaml, retirement, quarto
Last editorial update1h ago48m ago
WebsiteVisit →Visit →

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.

Read the full qualtRics trajectory →

What is ymlthis?

ymlthis retired itself, naming Quarto as the reason it no longer needs to exist.

ymlthis built R Markdown YAML front matter programmatically — a fluent `yml_*()` interface plus RStudio add-ins, so users did not have to hand-write metadata blocks whose valid fields were scattered across output-format documentation. Version 1.0.0 declares the package retired, with only CRAN-preserving changes to follow, and states the reason plainly: Quarto now provides good YAML support.

Read the full ymlthis trajectory →

qualtRics vs ymlthis: editorial side-by-side

Q
qualtRics
ANALYTICS
0.0

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.

Y
ymlthis
ANALYTICS
0.0

ymlthis retired itself, naming Quarto as the reason it no longer needs to exist.

◆ Current state

ymlthis built R Markdown YAML front matter programmatically — a fluent `yml_*()` interface plus RStudio add-ins, so users did not have to hand-write metadata blocks whose valid fields were scattered across output-format documentation. Version 1.0.0 declares the package retired, with only CRAN-preserving changes to follow, and states the reason plainly: Quarto now provides good YAML support.

◆ Where it's heading

The retirement is the endpoint of a long drift. Between 2020 and 2022 every release was reactive — patching around a crayon update that mangled rendered YAML, tracking shiny 1.6, following roxygen2 7.0.0, fixing a typo in an add-in. No new capability has landed in six years, and the four-year gap before 1.0.0 had already answered the question the release note finally makes explicit.

◆ Prediction

Nothing further of substance is expected — the stated policy is changes only where CRAN requires them, so the next release, if any, will be a compatibility patch.

Alternatives to qualtRics and ymlthis

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

See all qualtRics alternatives → · See all ymlthis alternatives →

Recent activity from qualtRics and ymlthis

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

  1. 1mo agoqualtRicsMailing list functions migrated to the XM Directory API
  2. 5mo agoymlthisymlthis retired; Quarto covers the need
  3. 11mo agoqualtRicsZip extraction handles more special characters in survey titles
  4. 1y agoqualtRicsFix for questions with both recoded values and variable naming
  5. 1y agoqualtRicsBuild and CI housekeeping alongside the 3.2.1 release
  6. 2y agoqualtRicsSurvey response caching removed from fetch_survey()
  7. 3y agoqualtRicsArgument checking refactor and include_* NA fix
  8. 4y agoymlthisTypo fixed in the miniUI add-in check
  9. 4y agoymlthisyml_author() accepts yml_blank(); shiny fixes
  10. 4y agoymlthisciteproc handling moved to newer rmarkdown functions
  11. 5y agoymlthisPatched a crayon update that mangled rendered YAML
  12. 5y agoymlthisAdjustments for shiny 1.6

Frequently asked questions

What is the difference between qualtRics and ymlthis?

They serve adjacent needs but don't currently overlap on shipped themes. qualtRics and ymlthis 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 ymlthis?

Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. qualtRics and ymlthis 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 ymlthis?

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