comtradr
comtradr's 1.0 line is a long tail of patches against a brittle UN trade API.
A side-by-side editorial comparison of flexdashboard and pins — release velocity, themes, recent moves, and the top alternatives to consider.
flexdashboard has slowed to a fix-only trickle since the bslib theming rework
flexdashboard turns R Markdown into dashboard layouts, and its last structural release was 0.6.0's integration with bslib, which handed theming to shared tidyverse infrastructure and opened the Bootstrap 4 path. Everything after that is Bootstrap 5 compatibility, navigation polish, and rendering fixes — with a two-and-a-half-year gap between 0.6.2 and 0.6.3.
pins keeps adding a storage backend per release while retiring its original API
pins publishes and versions R objects to a board, where a board is whatever storage you have. The recent releases read as a steady list of new boards - Google Cloud Storage, Google Drive, Databricks Volumes, Connect vanity URLs - alongside serialization changes that track which formats R users actually want: parquet via nanoparquet, and qs replaced by qs2.
flexdashboard turns R Markdown into dashboard layouts, and its last structural release was 0.6.0's integration with bslib, which handed theming to shared tidyverse infrastructure and opened the Bootstrap 4 path. Everything after that is Bootstrap 5 compatibility, navigation polish, and rendering fixes — with a two-and-a-half-year gap between 0.6.2 and 0.6.3.
The package has reached the stage where its releases exist to keep it working against newer Bootstrap, knitr and Quarto behavior rather than to add anything. Theming was outsourced to bslib, icons to Font Awesome, and the remaining surface is the layout syntax itself, which has not changed. The long release gaps are the clearest signal here.
The entries do not support a confident prediction of new capability; the realistic read is continued Bootstrap 5 compatibility fixes as bslib moves, at whatever cadence maintenance allows.
pins publishes and versions R objects to a board, where a board is whatever storage you have. The recent releases read as a steady list of new boards - Google Cloud Storage, Google Drive, Databricks Volumes, Connect vanity URLs - alongside serialization changes that track which formats R users actually want: parquet via nanoparquet, and qs replaced by qs2.
Two long-running processes, neither dramatic. Backend coverage expands toward wherever teams already store artifacts, which increasingly means Databricks and cloud object storage rather than a shared drive. Meanwhile the legacy pin() API from before the board model has been in a staged deprecation across at least three releases, escalated each time rather than removed.
Expect another board or two as storage platforms are requested, and the legacy pin() functions to finally become errors; the format list will keep tracking whichever serializer the R community settles on.
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 flexdashboard or pins.
comtradr's 1.0 line is a long tail of patches against a brittle UN trade API.
An htmlwidget whose release notes are mostly billboard.js version bumps, quiet since 2021.
bbotk is generalizing from an optimizer toolkit into an evaluation framework.
bayesplot keeps widening its posterior-check catalogue while absorbing each ggplot2 break.
Contribution-driven maintenance on a package whose last structural change was magick support.
tsibble shipped one release in five and a half years - the data structure is finished
See all flexdashboard alternatives → · See all pins alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. flexdashboard and pins 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. flexdashboard and pins 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 flexdashboard alternatives in Analytics are ranked by recent ship velocity. Browse the "flexdashboard alternatives" section above for the current picks, or visit /alternatives/flexdashboard for the full list with editorial commentary on each.
Top pins alternatives in Analytics are ranked by recent ship velocity. Browse the "pins alternatives" section above for the current picks, or visit /alternatives/pins-r for the full list with editorial commentary on each.