rollupTree
The recursive-computation engine under massProps grows the accessors its consumer needed
Comparison · Infra & APIs
formr vs surveytidy
A side-by-side editorial comparison of formr and surveytidy — release velocity, themes, recent moves, and the top alternatives to consider.
Shared themes:r-packages
formr vs surveytidy: at a glance
What is formr?
formr's R client reached CRAN and moved its recommended path to the v1 REST API.
formr is the R-side client for formr.org, the open study framework used to run longitudinal and experience-sampling questionnaires. In May it reached CRAN for the first time, released in step with formr.org server v1.0.0, and the formr_api_* family built on the server's RESTful surface became the supported entry point. The three releases since have been repair work on the paths that move rendered output and API results.
What is surveytidy?
surveytidy taught every dplyr verb to operate on a whole collection of surveys at once.
surveytidy is the tidyverse-facing half of a two-package survey stack, wrapping survey design objects from surveycore so filter, mutate, select and the rest work on them while carrying variable labels, value labels and a transformation log alongside the data. The May release extended that verb surface to survey_collection, the abstraction surveycore uses to hold several surveys as one object, so a pipeline written once dispatches across every member.
formr vs surveytidy: editorial side-by-side
formr
0.0INFRA · APIS
formr's R client reached CRAN and moved its recommended path to the v1 REST API.
◆ Current state
formr is the R-side client for formr.org, the open study framework used to run longitudinal and experience-sampling questionnaires. In May it reached CRAN for the first time, released in step with formr.org server v1.0.0, and the formr_api_* family built on the server's RESTful surface became the supported entry point. The three releases since have been repair work on the paths that move rendered output and API results.
◆ Where it's heading
The direction is consolidation around the v1 API while the legacy Classic path is left running but demoted in the vignette. The complication is that CRAN's requirements and the OpenCPU server's requirements pull against each other: CRAN review pushed rendering into tempdir() with random filenames, which broke rforms.org because the server fetches a fixed knit.html, and 1.1.2 had to put it back. The 1.2.0 note describes the same write-directory problem being solved in an OpenCPU-aware way rather than reverted, alongside making dependencies installable under WASM.
◆ Prediction
Two of the last three releases were regressions in the render path, so the OpenCPU-aware write directory in 1.2.0 is the change most likely to need follow-up. The Classic formr_results() path remains in the package with no removal date announced, and nothing in these entries indicates when that ends.
surveytidy
0.0INFRA · APIS
surveytidy taught every dplyr verb to operate on a whole collection of surveys at once.
◆ Current state
surveytidy is the tidyverse-facing half of a two-package survey stack, wrapping survey design objects from surveycore so filter, mutate, select and the rest work on them while carrying variable labels, value labels and a transformation log alongside the data. The May release extended that verb surface to survey_collection, the abstraction surveycore uses to hold several surveys as one object, so a pipeline written once dispatches across every member.
◆ Where it's heading
The package is being built in two layers that arrive in order: vector-level transformations first, structural dispatch second. The make_* family in 0.4.0 handles the recoding that survey work actually consists of — labelled to factor, multi-level to dichotomous, scale reversal, valence flipping — with value labels propagating automatically. Collection support then applies data-masking, tidyselect, grouping, slicing and collapsing verbs per survey, with joins explicitly refused and a typed message reporting which surveys were skipped. Metadata fidelity is the recurring bug source: labels surviving across(), stale labels left behind by recoding, the transformation log keeping up with what the verbs did.
◆ Prediction
Joins are the one verb family that errors on collections, with users directed to join before constructing the collection, so that restriction is the clearest outstanding gap. The re-export of surveycore's collection constructors suggests the package is positioning itself as the single import users need, which points toward more re-exports as surveycore's stable API settles.
Alternatives to formr and surveytidy
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 formr or surveytidy.
massProps
A mass-properties rollup spends a year on documentation and follows its sibling's API
writeAlizer
Six months of releases and not one of them touched the scoring models
samplr
A cognitive-science sampling package ships once, then goes quiet for eighteen months
stochvol
A Bayesian volatility sampler in its maintenance decade, paying for its own speed
midr
A black-box interpreter reaches CRAN, then learns multi-class and survival responses
See all formr alternatives → · See all surveytidy alternatives →
Recent activity from formr and surveytidy
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 1mo agoformrOpenCPU-aware render directory and WASM-installable dependencies
- 2mo agoformrHotfix: rendered output returns to knit.html
- 2mo agoformrcalculate items no longer coerced to NA by as.numeric()
- 2mo agosurveytidymutate() syncs metadata for across() recodes
- 2mo agoformrv1.0.0 — first CRAN release ⚡
- 3mo agosurveytidydplyr and tidyr verbs dispatch across survey collections
- 5mo agosurveytidyFive label-aware recoding functions for use inside mutate()
Frequently asked questions
What is the difference between formr and surveytidy?
Both compete on the same themes — r-packages — within Infra & APIs. formr and surveytidy 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 formr better than surveytidy?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. formr and surveytidy 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 Infra & APIs products to evaluate alongside.
What are the best alternatives to formr?
Top formr alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "formr alternatives" section above for the current picks, or visit /alternatives/formr for the full list with editorial commentary on each.
What are the best alternatives to surveytidy?
Top surveytidy alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "surveytidy alternatives" section above for the current picks, or visit /alternatives/surveytidy for the full list with editorial commentary on each.