← Back to home
Comparison · Infra & APIs

dockViewR vs retroharmonize

A side-by-side editorial comparison of dockViewR and retroharmonize — release velocity, themes, recent moves, and the top alternatives to consider.

Shared themes:r-package

dockViewR vs retroharmonize: at a glance

FeaturedockViewRretroharmonize
SectorInfra & APIsInfra & APIs
Velocity score0.00.0
Sparks · 30d00
Top themesshiny, htmlwidgets, ui-layout, javascript-bindingssurvey-data, data-harmonization, labelled-data, reproducibility
Last editorial update2d ago1h ago
WebsiteVisit →Visit →

What is dockViewR?

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.

Read the full dockViewR trajectory →

What is retroharmonize?

Survey harmonization tooling that spent its last release earning its way back onto CRAN.

retroharmonize handles retrospective harmonization of survey microdata — reconciling value codes, value labels, variable names, and missing-value ranges across waves so separate surveys can be joined or panelled reproducibly. The most recent release was not about any of that: the package had been archived from CRAN when a dependency was archived, and the work went into refactoring the labelled_spss_survey vctrs integration, separating core, print, arithmetic, and vctrs methods, and passing checks across five platforms plus R-devel.

Read the full retroharmonize trajectory →

dockViewR vs retroharmonize: editorial side-by-side

D
dockViewR
INFRA · APIS
0.0

Draggable dock panels for Shiny, learning that layout state belongs on the client

◆ Current state

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.

◆ Where it's heading

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.

◆ Prediction

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.

R
retroharmonize
INFRA · APIS
0.0

Survey harmonization tooling that spent its last release earning its way back onto CRAN.

◆ Current state

retroharmonize handles retrospective harmonization of survey microdata — reconciling value codes, value labels, variable names, and missing-value ranges across waves so separate surveys can be joined or panelled reproducibly. The most recent release was not about any of that: the package had been archived from CRAN when a dependency was archived, and the work went into refactoring the labelled_spss_survey vctrs integration, separating core, print, arithmetic, and vctrs methods, and passing checks across five platforms plus R-devel.

◆ Where it's heading

The design bet has been constant since the first release — comprehensive S3 classes that carry labels and missing-value semantics through every transformation, so the harmonization is documented rather than reconstructed. What has changed is where effort goes. Early releases added harmonization functions and a worked Arab Barometer case study; recent ones are code quality and CRAN survival. Note that the version numbering in this feed is not monotonic: 0.1.13 was released roughly nine months before 0.1.7, so version order here does not indicate release order.

◆ Prediction

Having just restored CRAN availability through a refactor rather than a feature, the near-term work is most likely consolidation of the vctrs integration the notes describe rather than new harmonization functions.

Alternatives to dockViewR and retroharmonize

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 retroharmonize.

See all dockViewR alternatives → · See all retroharmonize alternatives →

Recent activity from dockViewR and retroharmonize

Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.

  1. 3mo agoretroharmonizeCRAN modernisation release
  2. 7mo agoretroharmonizeRelease candidate; notes cite code quality with no detail
  3. 8mo agodockViewRReactive proxy replaces stale input-based panel checks
  4. 1y agodockViewRServer-side panel control and add/remove tracking
  5. 1y agodockViewRFirst CRAN release of the dockview panel widget
  6. 4y agoretroharmonizeImproved documentation
  7. 5y agoretroharmonize0.1.7 With case study on harmonizing Arab Barometer surveys
  8. 5y agoretroharmonizeretroharmonize 0.1.13 is on CRAN
  9. 6y agoretroharmonize0.1.0 Retrospective harmonization of survey data files in R

Frequently asked questions

What is the difference between dockViewR and retroharmonize?

Both compete on the same themes — r-package — within Infra & APIs. dockViewR and retroharmonize 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.

Is dockViewR better than retroharmonize?

Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. dockViewR and retroharmonize 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.

What are the best alternatives to dockViewR?

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.

What are the best alternatives to retroharmonize?

Top retroharmonize alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "retroharmonize alternatives" section above for the current picks, or visit /alternatives/retroharmonize for the full list with editorial commentary on each.