openair
Air quality analysis rebuilt on ggplot2, twenty years of lattice plotting dropped in one release.
Comparison · Infra & APIs
estimatr vs projoint
A side-by-side editorial comparison of estimatr and projoint — release velocity, themes, recent moves, and the top alternatives to consider.
Shared themes:r-package
estimatr vs projoint: at a glance
What is estimatr?
Fast design-based estimators for experiments, coasting on CRAN patches.
estimatr provides the design-based regression estimators the DeclareDesign ecosystem is built on — robust and cluster-robust standard errors, blocked and clustered randomization inference — implemented for speed rather than generality. The last three releases carry no substantive notes: each is a merge commit for a CRAN patch, one of them accompanied by a typo fix.
What is projoint?
projoint spent a year on CRAN paperwork, then shipped a correctness fix it flagged itself.
projoint is an R package for analysing conjoint survey experiments, covering Qualtrics import, reshaping, and quantity-of-interest estimation with inter-rater reliability correction. Most of its release history is CRAN admission work — citation formats, DESCRIPTION fields, \value{} tags, vignette cleanups — with four tags backfilled within ninety seconds of each other on 15 July in non-monotonic version order, so neither tag order nor timestamps in this feed track the real sequence. The substantive releases are the ones fixing data-preparation bugs that silently corrupt estimates.
estimatr vs projoint: editorial side-by-side
estimatr
0.0INFRA · APIS
Fast design-based estimators for experiments, coasting on CRAN patches.
◆ Current state
estimatr provides the design-based regression estimators the DeclareDesign ecosystem is built on — robust and cluster-robust standard errors, blocked and clustered randomization inference — implemented for speed rather than generality. The last three releases carry no substantive notes: each is a merge commit for a CRAN patch, one of them accompanied by a typo fix.
◆ Where it's heading
Direction cannot be read from this feed. The release notes are unedited merge-commit messages, so the only signal is cadence — roughly annual, each release framed as a CRAN patch rather than as feature work. That pattern is consistent with a package whose estimators are considered finished and which now moves only when CRAN policy requires it.
◆ Prediction
On the evidence here the next release is another CRAN compliance patch, but the notes are too thin to support a confident read of what the maintainers are actually working on.
projoint
2.5INFRA · APIS
projoint spent a year on CRAN paperwork, then shipped a correctness fix it flagged itself.
◆ Current state
projoint is an R package for analysing conjoint survey experiments, covering Qualtrics import, reshaping, and quantity-of-interest estimation with inter-rater reliability correction. Most of its release history is CRAN admission work — citation formats, DESCRIPTION fields, \value{} tags, vignette cleanups — with four tags backfilled within ninety seconds of each other on 15 July in non-monotonic version order, so neither tag order nor timestamps in this feed track the real sequence. The substantive releases are the ones fixing data-preparation bugs that silently corrupt estimates.
◆ Where it's heading
The maintainer is hardening the path from raw Qualtrics export to estimate, which is where conjoint analysis quietly goes wrong. Three separate releases fix that path: dropped respondent-level weights in organize_data(), repeated-task reshaping in reshape_projoint(), and choice-to-profile mapping in 1.1.3. Each fix now arrives with regression tests and stricter validation rather than just a patch, and 1.1.3 adds an explicit .choice_map so the mapping is auditable instead of inferred.
◆ Prediction
Expect the validation-and-regression-test pattern to keep extending across the import path, with releases continuing to arrive in bursts around CRAN submission rather than on a cadence.
Alternatives to estimatr and projoint
Other Infra & APIs 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 estimatr or projoint.
retroharmonize
Survey harmonization tooling that spent its last release earning its way back onto CRAN.
asar
A NOAA report-template generator being debugged by the workshops that teach it.
CBTF
A fuzzer for R packages that grew from one argument at a time to parallel runs across whole namespaces.
phyloatlas
An atlas of the tree of life that keeps publishing what it got wrong, and stopped shipping the trees it does not own.
OpenLand
Land-change analysis in R that has spent six years defending one download link.
See all estimatr alternatives → · See all projoint alternatives →
Recent activity from estimatr and projoint
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 17d agoprojointExplicit .choice_map guards choice-to-profile mapping
- 1mo agoprojointCRAN submission housekeeping for DESCRIPTION and examples
- 1mo agoprojointCRAN formatting pass; minor make_projoint_data() fix
- 1mo agoprojointreshape_projoint() repeated-task bug fixed; validation tightened
- 1mo agoprojointCitation metadata updated with the CRAN DOI
- 5mo agoprojointorganize_data() no longer drops respondent-level weights
- 1y agoestimatrCRAN version 1.0.4
- 2y agoestimatrCRAN version 1.0.2
- 3y agoestimatrCRAN version 1.0.0
Frequently asked questions
What is the difference between estimatr and projoint?
Both compete on the same themes — r-package — within Infra & APIs. projoint 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 estimatr better than projoint?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. projoint 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 Infra & APIs products to evaluate alongside.
What are the best alternatives to estimatr?
Top estimatr alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "estimatr alternatives" section above for the current picks, or visit /alternatives/estimatr for the full list with editorial commentary on each.
What are the best alternatives to projoint?
Top projoint alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "projoint alternatives" section above for the current picks, or visit /alternatives/projoint for the full list with editorial commentary on each.