tidytlg
A tables-listings-graphs package that reached CRAN and then went quiet.
Comparison · Analytics
chattr vs qualtRics
A side-by-side editorial comparison of chattr and qualtRics — release velocity, themes, recent moves, and the top alternatives to consider.
chattr vs qualtRics: at a glance
What is chattr?
chattr deleted every LLM integration it had written and outsourced the lot to ellmer
chattr puts a large language model inside the RStudio IDE, either through a Shiny app or directly at the console. As of 0.3.0 it no longer talks to any model provider itself: all integration goes through ellmer, and the hand-written OpenAI, Databricks and LlamaGPT backends were removed. The package's supported model list is now whatever ellmer supports, and the Shiny app streams responses through ellmer rather than managing a background process.
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.
chattr vs qualtRics: editorial side-by-side
chattr
0.0ANALYTICS
chattr deleted every LLM integration it had written and outsourced the lot to ellmer
◆ Current state
chattr puts a large language model inside the RStudio IDE, either through a Shiny app or directly at the console. As of 0.3.0 it no longer talks to any model provider itself: all integration goes through ellmer, and the hand-written OpenAI, Databricks and LlamaGPT backends were removed. The package's supported model list is now whatever ellmer supports, and the Shiny app streams responses through ellmer rather than managing a background process.
◆ Where it's heading
The first two releases show why that happened. Each provider brought its own error formats, token discovery and response handling, and 0.2.0 is largely a list of per-provider repairs — OpenAI error parsing, Copilot token discovery and model defaults, a new Databricks foundation model backend. Maintaining that surface scales linearly with the number of providers, and the pivot to ellmer trades it for a single dependency. The cost shows up immediately in 0.3.1, which exists solely to absorb a change in ellmer's token object.
◆ Prediction
Expect chattr's releases to now track ellmer's, as 0.3.1 already does, with the package's own work concentrating on the IDE experience rather than model connectivity. New provider support will arrive without a chattr release at all.
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.
Alternatives to chattr and qualtRics
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 chattr or qualtRics.
Tplyr
Tplyr made clinical summary tables explain where every number came from.
rlistings
Clinical listings that keep inheriting their hardest problem — pagination — from the layer below.
hoardr
A cache-directory helper that has shipped nothing but CRAN-triggered patches for seven years.
gigs
gigs redesigned its whole conversion API for rOpenSci, then spent three releases getting the docs to build.
riem
A weather-data client that keeps rewriting its HTTP layer while slowly tightening its API.
See all chattr alternatives → · See all qualtRics alternatives →
Recent activity from chattr and qualtRics
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
- 0y agochattrAdapts to ellmer's token object change
- 1y agochattrAll model integration moves to ellmer, direct backends removed ⚡
- 1y agoqualtRicsFix for questions with both recoded values and variable naming
- 1y agoqualtRicsBuild and CI housekeeping alongside the 3.2.1 release
- 2y agochattrDatabricks foundation models added; per-provider error handling fixed
- 2y agochattrFirst release: LLM chat in the RStudio console and app
- 2y agoqualtRicsSurvey response caching removed from fetch_survey()
- 3y agoqualtRicsArgument checking refactor and include_* NA fix
Frequently asked questions
What is the difference between chattr and qualtRics?
They serve adjacent needs but don't currently overlap on shipped themes. chattr and qualtRics 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 chattr better than qualtRics?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. chattr and qualtRics 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 chattr?
Top chattr alternatives in Analytics are ranked by recent ship velocity. Browse the "chattr alternatives" section above for the current picks, or visit /alternatives/chattr for the full list with editorial commentary on each.
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.