← Back to home
Comparison · Infra & APIs

formr vs writeAlizer

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

formr vs writeAlizer: at a glance

FeatureformrwriteAlizer
SectorInfra & APIsInfra & APIs
Velocity score0.00.0
Sparks · 30d00
Top themessurvey-research, rest-api, cran-release, opencpuwriting-assessment, nlp-features, model-artifacts, cran-compliance
Last editorial update2h ago1h ago
WebsiteVisit →Visit →

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.

Read the full formr trajectory →

What is writeAlizer?

Six months of releases and not one of them touched the scoring models

writeAlizer generates predicted writing-quality scores from features produced by Coh-Metrix, ReaderBench and GAMET, downloading its trained scoring models on demand. Every release in this window — nine of them between September 2025 and February 2026 — is about that download path rather than the scoring: classed error conditions, checksum verification, an offline mode, a mockable artifact directory, and dependency reporting for the model families a user actually invokes.

Read the full writeAlizer trajectory →

formr vs writeAlizer: editorial side-by-side

F
formr
INFRA · APIS
0.0

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.

W
writeAlizer
INFRA · APIS
0.0

Six months of releases and not one of them touched the scoring models

◆ Current state

writeAlizer generates predicted writing-quality scores from features produced by Coh-Metrix, ReaderBench and GAMET, downloading its trained scoring models on demand. Every release in this window — nine of them between September 2025 and February 2026 — is about that download path rather than the scoring: classed error conditions, checksum verification, an offline mode, a mockable artifact directory, and dependency reporting for the model families a user actually invokes.

◆ Where it's heading

The package is being made safe to distribute. CRAN's policy on packages that reach the internet drove the first wave — graceful failure, tests that preflight their URLs and skip, examples seeded from a local mock model — and 1.7.0 turned the accumulated fixes into structure with named error classes for each failure mode. Only 1.7.2 adds anything a user would ask for: filename handling for Coh-Metrix and GAMET outputs that arrive as paths.

◆ Prediction

With the artifact registry hardened and documented, the pressure that produced nine releases in six months should ease, and attention can return to the models themselves — the vignette on scoring-model development added in 1.7.2 hints at that. Nothing here promises new models.

Alternatives to formr and writeAlizer

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

See all formr alternatives → · See all writeAlizer alternatives →

Recent activity from formr and writeAlizer

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

  1. 1mo agoformrOpenCPU-aware render directory and WASM-installable dependencies
  2. 2mo agoformrHotfix: rendered output returns to knit.html
  3. 2mo agoformrcalculate items no longer coerced to NA by as.numeric()
  4. 2mo agoformrv1.0.0 — first CRAN release
  5. 6mo agowriteAlizerOne example rewrapped to silence a CRAN check note
  6. 8mo agowriteAlizerFilename stems recovered from Coh-Metrix and GAMET paths
  7. 10mo agowriteAlizerOffline example guard, declared as no API change
  8. 10mo agowriteAlizerNamed error classes for every model-download failure mode
  9. 10mo agowriteAlizerNetwork failures degrade gracefully under CRAN policy
  10. 11mo agowriteAlizerwa_seed_example_models() exported and documented

Frequently asked questions

What is the difference between formr and writeAlizer?

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

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

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