poppr
A population-genetics workhorse in long-term maintenance, shipping only what CRAN demands.
A side-by-side editorial comparison of edibble and rgoogleads — release velocity, themes, recent moves, and the top alternatives to consider.
A grammar for experimental design that learned to compose designs and track its own provenance.
edibble expresses experimental designs declaratively — units, treatments, records and their allotments — rather than calling a canned design function. Since 1.0.0 its internals run on a Provenance object that records the commands used to build a design, and 1.1.0 added conditional treatments, design composition and a separated simulation step. Recent work has focused on designs constructed from existing data rather than from scratch.
A Google Ads API client for R that exists to stay one step ahead of deprecation.
rgoogleads gives R analysts access to the Google Ads API, and its release log is essentially a list of API versions cleared: v10, v11, v13, v14, v16. The last substantive code change was 0.9.2, which rebuilt gads_get_geo_targets() after Google started publishing its region reference as a zip archive instead of a plain CSV, forcing the function to download and unpack before reading.
edibble expresses experimental designs declaratively — units, treatments, records and their allotments — rather than calling a canned design function. Since 1.0.0 its internals run on a Provenance object that records the commands used to build a design, and 1.1.0 added conditional treatments, design composition and a separated simulation step. Recent work has focused on designs constructed from existing data rather than from scratch.
Development has moved from vocabulary to composition. Early releases established the core grammar; 1.0.0 replaced the internal R6 machinery with a Provenance object that tracks both internal and external commands, which is what lets a design carry its own construction history. On that foundation 1.1.0 added the ability to add two designs together, express conditional treatment structures, and split simulation specification from execution. The 2025 release turns toward a different entry point — wiring up level edges and unit attributes when an edibble object is built from data that already exists, rather than from a design declared up front.
Expect continued work on designs derived from existing data, since that is where the last release concentrated and it is the path least covered by the declarative grammar.
rgoogleads gives R analysts access to the Google Ads API, and its release log is essentially a list of API versions cleared: v10, v11, v13, v14, v16. The last substantive code change was 0.9.2, which rebuilt gads_get_geo_targets() after Google started publishing its region reference as a zip archive instead of a plain CSV, forcing the function to download and unpack before reading.
Development is reactive by design — the package changes when Google changes, and the notes rarely describe anything else. The deeper rework happened earlier, in 0.7.0, when request generation was centralised into gads_make_request() and gads_customer() was rewritten onto SearchStream after the old get method was retired. Since then the structure has held and releases have thinned to version bumps, with the most recent gap running over a year.
The next release will be a migration to a newer Google Ads API version, and on this history it will arrive when the current one nears sunset rather than on any schedule of the maintainer's own.
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 edibble or rgoogleads.
A population-genetics workhorse in long-term maintenance, shipping only what CRAN demands.
An urban accessibility toolkit that grew into a distributional-equity toolkit.
The Carpentries' lesson skin, rebuilt on Bootstrap 5 with dark mode and a wider reach.
A project-bound modelling package that shipped its final scenario workflow and stopped.
A Facebook Marketing API client for R whose release schedule belongs to Meta, not its author.
A Japan Meteorological Agency client whose real product is keeping its bundled datasets current.
See all edibble alternatives → · See all rgoogleads alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
Both compete on the same themes — r-package — within Analytics. edibble and rgoogleads 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.
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. edibble and rgoogleads 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.
Top edibble alternatives in Analytics are ranked by recent ship velocity. Browse the "edibble alternatives" section above for the current picks, or visit /alternatives/edibble for the full list with editorial commentary on each.
Top rgoogleads alternatives in Analytics are ranked by recent ship velocity. Browse the "rgoogleads alternatives" section above for the current picks, or visit /alternatives/rgoogleads for the full list with editorial commentary on each.