SLmetrics
A young ML metrics package rewrote its own backend twice in six months chasing speed.
A side-by-side editorial comparison of dockViewR and GravityKit — release velocity, themes, recent moves, and the top alternatives to consider.
Draggable dock panels for Shiny, learning that layout state belongs on the client
dockViewR wraps the dockview JavaScript library so Shiny apps can offer draggable, splittable, tabbed panel layouts — the IDE arrangement, driven from R. Three releases since May 2025 have taken it from a working widget to one with a proper server-side control surface: panels can be added, removed, selected and moved from the server, and the dock exposes a reactive proxy.
GravityKit ships a weekly Launch Log, and the interesting work is buried inside it
GravityKit publishes a consolidated weekly Launch Log across its whole add-on suite rather than per-product release notes, so a single entry can carry a genuine new capability and a batch of compatibility fixes side by side. The recent run covers Google Sheets export in GravityExport, adaptive DataTables columns, calendar sync fixes, unions in Multiple Forms 0.7.0, rich text inline editing in GravityEdit, and a long tail of Gravity Forms 3.0 and WordPress 7.0 compatibility work. GravityView 3.0 in June, with the Vantage theme and AI-assisted View creation, remains the anchor release the suite is building on.
dockViewR wraps the dockview JavaScript library so Shiny apps can offer draggable, splittable, tabbed panel layouts — the IDE arrangement, driven from R. Three releases since May 2025 have taken it from a working widget to one with a proper server-side control surface: panels can be added, removed, selected and moved from the server, and the dock exposes a reactive proxy.
The design has been converging on the standard htmlwidgets pattern, and 0.3.0 is where it commits. Earlier releases routed panel-id checks through Shiny inputs, which meant the state was stale until the next reactive flush and forced awkward workarounds when manipulating the dock inside observeEvent(). Moving those checks to the browser and adding dock_view_proxy() drops that class of bug entirely, at the cost of a breaking API change and a dev-mode option for surfacing the warnings.
Having taken one breaking change to reach the proxy idiom, the natural follow-on is filling out the proxy surface so every panel operation is reachable through it.
GravityKit publishes a consolidated weekly Launch Log across its whole add-on suite rather than per-product release notes, so a single entry can carry a genuine new capability and a batch of compatibility fixes side by side. The recent run covers Google Sheets export in GravityExport, adaptive DataTables columns, calendar sync fixes, unions in Multiple Forms 0.7.0, rich text inline editing in GravityEdit, and a long tail of Gravity Forms 3.0 and WordPress 7.0 compatibility work. GravityView 3.0 in June, with the Vantage theme and AI-assisted View creation, remains the anchor release the suite is building on.
Two threads persist. One is making Views handle data they previously could not — unions stacking entries from many forms without a shared field or custom code, field-to-field filtering, distance sorting, 3D map viewport loading. The other is compatibility maintenance against a moving platform, with Gravity Forms 3.0 fixes appearing in four consecutive Launch Logs. The MCP work on Block MCP and GravityKit MCP has gone quiet since June, which makes the AI thread the least predictable part of the suite.
Expect the export and data-source work to keep widening now that Google Sheets is wired in, and the Gravity Forms 3.0 fix stream to taper as the compatibility surface is worked through. Whether the MCP add-ons get further investment is not readable from these entries.
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 dockViewR or GravityKit.
A young ML metrics package rewrote its own backend twice in six months chasing speed.
The AusTraits engine, generalised for anyone's trait database, now links measurements to real specimens.
The toolchain that gets R packages into the browser is optimising for payload size, not features.
Fail2Ban finally ships 1.1.1 after 14 months in beta, with a botched deb package on the way out the door
A logging header for Rcpp packages that sat untouched for nine years, then changed how it switches on
The C++ layer under R's neuroimaging stack, closing the gaps where images stopped acting like arrays
See all dockViewR alternatives → · See all GravityKit alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. GravityKit is currently shipping more aggressively (velocity 5.0 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.
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. GravityKit is currently shipping more aggressively (velocity 5.0 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 Infra & APIs products to evaluate alongside.
Top dockViewR alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "dockViewR alternatives" section above for the current picks, or visit /alternatives/dockviewr for the full list with editorial commentary on each.
Top GravityKit alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "GravityKit alternatives" section above for the current picks, or visit /alternatives/gravitykit for the full list with editorial commentary on each.