Whatagraph
Whatagraph keeps fixing what breaks when one account runs a thousand sources.
A side-by-side editorial comparison of animovement and Plotly — release velocity, themes, recent moves, and the top alternatives to consider.
animovement stopped being a package and became a metapackage over seven focused ones.
animovement handles animal movement data — tracking output from pose-estimation and centroid trackers, cleaned into a standard form. Its 0.7.3 release, the first GitHub tag since November 2024, bundles the 0.5 through 0.7 development series and records a structural change: the codebase was split into aniframe, aniread, aniprocess, anicheck, animetric, anivis and anispace, which animovement now bundles and re-exports. The package has done this before at smaller scale, having renamed itself from trackballr in 0.2.0 to match a widened scope.
Plotly is turning its cloud into a metered compute platform with an enterprise on-ramp.
Plotly ships on two tracks. Plotly Studio, the desktop AI app-builder, releases every one to two weeks and has spent v0.0.80 through v0.0.86 on credential handling, reasoning transparency, personalization and now the reliability of the agent session engine itself. Plotly Cloud is the louder track: since late May it has added viewer-seat pricing, domain verification, per-app compute modes with credit-metered billing, and customer-owned domains with managed TLS.
animovement handles animal movement data — tracking output from pose-estimation and centroid trackers, cleaned into a standard form. Its 0.7.3 release, the first GitHub tag since November 2024, bundles the 0.5 through 0.7 development series and records a structural change: the codebase was split into aniframe, aniread, aniprocess, anicheck, animetric, anivis and anispace, which animovement now bundles and re-exports. The package has done this before at smaller scale, having renamed itself from trackballr in 0.2.0 to match a widened scope.
Development has moved to the constituent packages, which release far more often than animovement itself — aniframe, aniread and aniprocess have each shipped multiple times in 2026 while animovement tagged once. That makes animovement a stable install surface rather than where the work happens, and the ani_df data class plus the frame-rate to sampling-rate terminology change are the contracts holding the suite together. Optional dependencies are handled through animovement_install_suggested() against r-universe and Bioconductor mirrors.
With the split done and the constituent packages iterating independently, animovement releases are likely to become periodic roll-ups of the suite rather than carriers of new functionality.
Plotly ships on two tracks. Plotly Studio, the desktop AI app-builder, releases every one to two weeks and has spent v0.0.80 through v0.0.86 on credential handling, reasoning transparency, personalization and now the reliability of the agent session engine itself. Plotly Cloud is the louder track: since late May it has added viewer-seat pricing, domain verification, per-app compute modes with credit-metered billing, and customer-owned domains with managed TLS.
The Cloud releases are assembling the standard pieces of a hosting business in order — identity first (domain verification, explicitly framed as the step before SSO), then billing (viewer seats, then metered compute credits), and now production-grade serving (custom domains, automatic certificate renewal). Studio is being hardened as the authoring front end that feeds it: Universal Deployment pushed beyond Dash apps, credentials saved once and reused, a Winget channel to widen Windows installs, and in v0.0.86 a rebuilt session engine plus automatic retries so agent runs survive expired tokens. The two tracks converge on one funnel — author in Studio, deploy to Cloud, pay by compute consumed.
The Domain Verification entry names SSO as the next step and places it in the Enterprise tier, so single sign-on is the most likely Cloud release next. Studio should hold its one-to-two-week cadence, with the newly added app thumbnails pointing toward more work on browsing and organizing generated apps.
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 animovement or Plotly.
Whatagraph keeps fixing what breaks when one account runs a thousand sources.
Lightdash keeps handing authoring to outside agents and keeping the governed layer for itself.
A 4.4.0 tag appears, but the feed carries only its release plumbing
distributions3 0.3.0 adds sample-based distributions and likelihood derivatives
Basedash keeps pushing its data out of the workspace — now to people without accounts
RStudio ships through release branches, and the notes are commit messages
See all animovement alternatives → · See all Plotly alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. Plotly is currently shipping more aggressively (velocity 6.3 vs 0.0), with 1 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.
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. Plotly is currently shipping more aggressively (velocity 6.3 vs 0.0), with 1 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.
Top animovement alternatives in Analytics are ranked by recent ship velocity. Browse the "animovement alternatives" section above for the current picks, or visit /alternatives/animovement for the full list with editorial commentary on each.
Top Plotly alternatives in Analytics are ranked by recent ship velocity. Browse the "Plotly alternatives" section above for the current picks, or visit /alternatives/plotly for the full list with editorial commentary on each.