osmapiR
osmapiR is the rare API client that tracks its server's wiki revision numbers in the changelog.
A side-by-side editorial comparison of Athlytics and S7 — release velocity, themes, recent moves, and the top alternatives to consider.
A Strava analytics package spent its 1.0 cycle surviving rOpenSci review, not adding features.
Athlytics computes endurance-training metrics — ACWR, EWMA load, efficiency factor, decoupling, personal bests — from Strava exports. Every release in view is review-driven: test-suite consolidation, dataset renames, styler passes, and a substantial robustness pass over the metric calculations and stream parsers. 1.0.6 explicitly changes nothing but packaging metadata.
S7 has stopped adding surface and started proving it holds up against R itself.
S7 is R's third-generation object system, built to unify the S3 and S4 lineages rather than add a fourth. The design work landed in 0.2.0, which reworked the default constructor, extended base-class coverage, and added a backward-compatibility shim so `@` property access works on R older than 4.3. Everything since has been maintenance: property setters gained a `check` escape hatch, and two consecutive releases exist mainly to keep the package compiling against R-devel 4.6.
Athlytics computes endurance-training metrics — ACWR, EWMA load, efficiency factor, decoupling, personal bests — from Strava exports. Every release in view is review-driven: test-suite consolidation, dataset renames, styler passes, and a substantial robustness pass over the metric calculations and stream parsers. 1.0.6 explicitly changes nothing but packaging metadata.
The package is optimising for credibility rather than surface area. It completed rOpenSci peer review, moved to an offline ZIP export workflow with hardened TCX/GPX parsing, corrected the EWMA half-life mapping, and deliberately softened its ACWR language away from injury-risk claims. Version numbers are also being published out of order, which makes the feed a poor guide to what shipped when.
With review complete and packaging metadata frozen for archival, the next substantive release is more likely to extend metric coverage or data sources than to continue polishing; nothing in these entries points to a specific new metric.
S7 is R's third-generation object system, built to unify the S3 and S4 lineages rather than add a fourth. The design work landed in 0.2.0, which reworked the default constructor, extended base-class coverage, and added a backward-compatibility shim so `@` property access works on R older than 4.3. Everything since has been maintenance: property setters gained a `check` escape hatch, and two consecutive releases exist mainly to keep the package compiling against R-devel 4.6.
The changelog is thinning by design — 0.1.0 was a months-long feature dump, 0.2.0 a coordinated architectural revision, 0.2.2 a single line about internal R-devel support. That shape usually means an API the maintainers consider settled, where the remaining work is tracking the host language rather than extending the system. The one recurring theme is validation cost: repeated releases have made validation less frequent, more targeted, or skippable outright.
Expect continued small releases pinned to R-devel changes rather than new class-system features, with any further movement most likely in the validation and property-setter path that the last two feature changes both touched.
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 Athlytics or S7.
osmapiR is the rare API client that tracks its server's wiki revision numbers in the changelog.
ymlthis retired itself, naming Quarto as the reason it no longer needs to exist.
forestly built an interactive safety review tool, then taught it to produce submission-ready RTF.
pharmaverseadam is the pharmaverse's test-data mirror, and it now covers neurology.
pkglite's whole job is knowing which files in an R package are text — and it keeps getting better at guessing.
gMCPLite exists to be gMCP without Java, and its releases guard that boundary rather than extend it.
See all Athlytics alternatives → · See all S7 alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. Athlytics and S7 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. Athlytics and S7 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 Athlytics alternatives in Analytics are ranked by recent ship velocity. Browse the "Athlytics alternatives" section above for the current picks, or visit /alternatives/athlytics for the full list with editorial commentary on each.
Top S7 alternatives in Analytics are ranked by recent ship velocity. Browse the "S7 alternatives" section above for the current picks, or visit /alternatives/s7 for the full list with editorial commentary on each.