WPML
WPML made machine translation the default, and its point releases keep chasing WordPress and page builders.
A side-by-side editorial comparison of dockViewR and FoRecoML — 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.
The machine-learning arm of a forecast reconciliation toolkit, four months old and already sharing its sibling's plumbing.
FoRecoML brings machine-learning approaches to forecast reconciliation across cross-sectional, temporal, and cross-temporal frameworks through csrml(), terml(), and ctrml(). It reached CRAN in April 2026 and has since spent both releases integrating with FoReco rather than expanding its own method set: results are now FoReco's foreco objects, and print() and summary() report framework, approach, problem dimensions, features, training sample size, combination matrix, and trained models.
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.
FoRecoML brings machine-learning approaches to forecast reconciliation across cross-sectional, temporal, and cross-temporal frameworks through csrml(), terml(), and ctrml(). It reached CRAN in April 2026 and has since spent both releases integrating with FoReco rather than expanding its own method set: results are now FoReco's foreco objects, and print() and summary() report framework, approach, problem dimensions, features, training sample size, combination matrix, and trained models.
This package is being built as a satellite, not a competitor. Adopting FoReco's exported new_foreco_class() constructor within days of that class appearing means FoRecoML results drop straight into the same print, summary, plot, and components methods as analytically reconciled ones — which is what makes machine-learning and classical reconciliation directly comparable in a single workflow. The 1.1.1 argument-validation work landed in the same minute as the equivalent change in FoReco, so the two are being maintained as one release train.
With the integration work done, the next release is more likely to add or expose machine-learning approaches than to keep reshaping output; the structured summary already enumerates features and trained models, which suggests inspection tooling is where attention has been.
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 FoRecoML.
WPML made machine translation the default, and its point releases keep chasing WordPress and page builders.
A forest plot package that keeps handing users control of one more graphical detail.
Interval-valued data plotting, spending 2026 making its function names and examples survive CRAN.
A microbiome network model that got itself un-archived by deleting the dependency that killed it.
Three releases in ten days, every one of them a CRAN reviewer's correction rather than a code change.
Pipeline provenance for tidyverse workflows, recording what changed at each step without keeping the data.
See all dockViewR alternatives → · See all FoRecoML alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
Both compete on the same themes — r-package — within Infra & APIs. dockViewR and FoRecoML 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. dockViewR and FoRecoML 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 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 FoRecoML alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "FoRecoML alternatives" section above for the current picks, or visit /alternatives/forecoml for the full list with editorial commentary on each.