← Back to home
Comparison · Analytics

fect vs r-owidapi

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

Shared themes:r-package

fect vs r-owidapi: at a glance

Featurefectr-owidapi
SectorAnalyticsAnalytics
Velocity score0.02.5
Sparks · 30d00
Top themesr-package, causal-inference, panel-data, api-redesignopen-data, our-world-in-data, r-package, api-wrapper
Last editorial update1h ago2h ago
WebsiteVisit →Visit →

What is fect?

A counterfactual estimator turning itself into a platform for multiple estimands

fect implements counterfactual estimators for panel data with treatment effects — imputation-based fixed effects, interactive fixed effects, matrix completion. The 2026 releases move fast and bundle heavily: 2.1.0 rewrote complex fixed effect handling, 2.2.0 unified cross-validation under a single cv.method parameter and replaced method='gsynth' with an explicit time.component.from switch, 2.4.1 introduced a post-hoc estimand API, and 2.4.5 added group.fe for coarsened fixed effects plus a $sample slot exposing which cells entered estimation.

Read the full fect trajectory →

What is r-owidapi?

The R client for Our World in Data found its search had been reading a tenth of the catalog.

owidapi is a small R client for Our World in Data, covering chart data retrieval, metadata, the full chart catalog, and search over it, with experimental Shiny output helpers. It is three releases old and the most recent one is almost entirely repair: the catalog function was silently truncating at 1000 rows because of a Datasette row cap, which meant search had been operating on a fraction of what exists.

Read the full r-owidapi trajectory →

fect vs r-owidapi: editorial side-by-side

F
fect
ANALYTICS
0.0

A counterfactual estimator turning itself into a platform for multiple estimands

◆ Current state

fect implements counterfactual estimators for panel data with treatment effects — imputation-based fixed effects, interactive fixed effects, matrix completion. The 2026 releases move fast and bundle heavily: 2.1.0 rewrote complex fixed effect handling, 2.2.0 unified cross-validation under a single cv.method parameter and replaced method='gsynth' with an explicit time.component.from switch, 2.4.1 introduced a post-hoc estimand API, and 2.4.5 added group.fe for coarsened fixed effects plus a $sample slot exposing which cells entered estimation.

◆ Where it's heading

The direction is separation of estimation from interpretation. Where the package once returned one effect from one fit, estimand() now dispatches typed estimands — ATT, cumulative ATT, APTT, log ATT — from any imputation fit, with effect() and att.cumu() soft-deprecated but byte-identical pending 3.0.0. Alongside that runs a transparency thread: the $sample matrix, out-of-sample comparison via fect_mspe(), and named component sources instead of opaque method aliases. The release notes are unusually precise about which results change and which do not.

◆ Prediction

The soft-deprecation notice names 3.0.0 as the removal point for effect() and att.cumu(), so a major release consolidating on the estimand() dispatcher is the clearly signposted next step.

R
r-owidapi
ANALYTICS
2.5

The R client for Our World in Data found its search had been reading a tenth of the catalog.

◆ Current state

owidapi is a small R client for Our World in Data, covering chart data retrieval, metadata, the full chart catalog, and search over it, with experimental Shiny output helpers. It is three releases old and the most recent one is almost entirely repair: the catalog function was silently truncating at 1000 rows because of a Datasette row cap, which meant search had been operating on a fraction of what exists.

◆ Where it's heading

Development is about making a thin wrapper trustworthy against an upstream that moves without notice. The truncation fix pages through the catalog properly; a separate fix stops the function breaking when Our World in Data dropped a column, by parsing typed columns only when present. Tests moved to mocked responses, with a small live suite retained purely to detect schema drift and skipped on CRAN — a sensible design for a package whose main risk is that the API changes shape rather than that the code is wrong. The user-facing surface has not grown since the initial release; the work is in defending it.

◆ Prediction

On this pattern the next release is likelier to be another upstream-compatibility fix than new functionality, with the schema-drift tests the mechanism that surfaces it.

Alternatives to fect and r-owidapi

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 fect or r-owidapi.

See all fect alternatives → · See all r-owidapi alternatives →

Recent activity from fect and r-owidapi

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

  1. 20d agor-owidapiCatalog was silently capped at 1000 charts; now paged in full
  2. 2mo agofectAdds group.fe for coarsened fixed effects and a $sample slot
  3. 3mo agofectPost-hoc estimand API decouples estimands from the fit
  4. 4mo agofectUnified cross-validation and explicit control of time components
  5. 7mo agofectRewrites complex fixed effect handling and fixes speed
  6. 11mo agofectAdds heterogeneous treatment effect plots and caps default cores
  7. 1y agor-owidapiRequest logic consolidated, with graceful catalog errors
  8. 1y agor-owidapiFirst release: data, metadata, catalog and search

Frequently asked questions

What is the difference between fect and r-owidapi?

Both compete on the same themes — r-package — within Analytics. r-owidapi 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 fect better than r-owidapi?

Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. r-owidapi 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 Analytics products to evaluate alongside.

What are the best alternatives to fect?

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

What are the best alternatives to r-owidapi?

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