← Back to home
Comparison · Analytics

qualtRics vs rtflite

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

qualtRics vs rtflite: at a glance

FeaturequaltRicsrtflite
SectorAnalyticsAnalytics
Velocity score0.00.0
Sparks · 30d00
Top themessurvey-data, api-client, qualtrics, ropensciclinical-reporting, python, document-conversion, rtf
Last editorial update1h ago41m 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 rtflite?

rtflite stopped being an RTF writer and became the conversion layer for clinical table output.

rtflite generates the RTF tables clinical study reports are built from, a Python answer to the R tooling that has owned this niche. Over one dense month it grew a full export path: DOCX in 2.2.0, DOCX concatenation in 2.3.0, a configurable LibreOffice converter in 2.4.0, and HTML plus PDF in 2.5.0. The three releases since have been documentation, test infrastructure, and typing work — the feature push has stopped and consolidation has started.

Read the full rtflite trajectory →

qualtRics vs rtflite: 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.

R
rtflite
ANALYTICS
0.0

rtflite stopped being an RTF writer and became the conversion layer for clinical table output.

◆ Current state

rtflite generates the RTF tables clinical study reports are built from, a Python answer to the R tooling that has owned this niche. Over one dense month it grew a full export path: DOCX in 2.2.0, DOCX concatenation in 2.3.0, a configurable LibreOffice converter in 2.4.0, and HTML plus PDF in 2.5.0. The three releases since have been documentation, test infrastructure, and typing work — the feature push has stopped and consolidation has started.

◆ Where it's heading

Every format addition routes through the same LibreOffice converter rather than a per-format implementation, and 2.4.0's breaking change made that converter an injectable object you can configure and reuse. That is the shape of a package expecting to run inside a pipeline that produces hundreds of tables, not one that converts a document at a time. The recent quiet — snapshot tests moved onto `pytest-r-snapshot`, docs migrated, pandas and pyarrow dropped from dev dependencies — reads as work to stay dependency-light while the surface stabilizes.

◆ Prediction

With the export matrix filled in and three consecutive infrastructure-only releases, the next substantive change is most likely on the input side — table construction and pagination — since `page_by` and `subline_by` are the only feature area still generating bug reports in these notes.

Alternatives to qualtRics and rtflite

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

See all qualtRics alternatives → · See all rtflite alternatives →

Recent activity from qualtRics and rtflite

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

  1. 1mo agoqualtRicsMailing list functions migrated to the XM Directory API
  2. 4mo agortfliteMulti-section body typing tightened; pandas dropped from dev deps
  3. 7mo agortfliteAPI reference renders Pydantic field metadata
  4. 7mo agortfliteDocumentation site migrated to Zensical
  5. 7mo agortfliteSnapshot tests moved to pytest-r-snapshot
  6. 7mo agortfliteHTML and PDF export complete the output matrix
  7. 7mo agortfliteLibreOffice conversion becomes an injectable converter object
  8. 11mo agoqualtRicsZip extraction handles more special characters in survey titles
  9. 1y agoqualtRicsFix for questions with both recoded values and variable naming
  10. 1y agoqualtRicsBuild and CI housekeeping alongside the 3.2.1 release
  11. 2y agoqualtRicsSurvey response caching removed from fetch_survey()
  12. 3y agoqualtRicsArgument checking refactor and include_* NA fix

Frequently asked questions

What is the difference between qualtRics and rtflite?

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

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

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