← Back to home
Comparison · Analytics

forestly vs patentsview

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

forestly vs patentsview: at a glance

Featureforestlypatentsview
SectorAnalyticsAnalytics
Velocity score0.00.0
Sparks · 30d00
Top themesclinical-safety, adverse-events, data-visualization, r-languageapi-client, breaking-change, patent-data, r-package
Last editorial update1h ago3h ago
WebsiteVisit →Visit →

What is forestly?

forestly built an interactive safety review tool, then taught it to produce submission-ready RTF.

forestly renders adverse-event forest plots as interactive reactable widgets — filterable by AE category, with sliders for incidence thresholds and a toggle for the risk-difference column. Version 0.1.3 added `rtf_static_forestly()` for static RTF output, and 0.1.4 has been about giving the display owner control over what reviewers see: the CSV download button, the AE filter label, and the diff toggle can each be switched off.

Read the full forestly trajectory →

What is patentsview?

Dormant for years, then rewritten wholesale when the API underneath it broke.

patentsview is an R client for the USPTO PatentsView API, and version 1.0.0 is less a feature release than a forced reconstruction: the upstream API introduced mandatory keys, renamed and re-nested its endpoints, and the package had to follow. Between 2017 and 2021 the release cadence was roughly annual and almost entirely defensive — wrapping examples so CRAN would not fail during API outages, patching URL encoding, adding throttling retries. The 1.0.0 work restores the package to parity with an API that no longer resembles the one it was written against.

Read the full patentsview trajectory →

forestly vs patentsview: editorial side-by-side

F
forestly
ANALYTICS
0.0

forestly built an interactive safety review tool, then taught it to produce submission-ready RTF.

◆ Current state

forestly renders adverse-event forest plots as interactive reactable widgets — filterable by AE category, with sliders for incidence thresholds and a toggle for the risk-difference column. Version 0.1.3 added `rtf_static_forestly()` for static RTF output, and 0.1.4 has been about giving the display owner control over what reviewers see: the CSV download button, the AE filter label, and the diff toggle can each be switched off.

◆ Where it's heading

The arc runs from a fixed interactive widget toward a configurable one with two output modes. Nearly every new argument in the last two releases exists to remove something from the display or relabel it, which suggests the users driving development are producing outputs for others to review under conventions they do not control. The x-axis range, column header, figure header and slider range arguments point the same way — this is a tool being fitted into standardised reporting rather than used ad hoc.

◆ Prediction

Given that the last two releases have consisted almost entirely of display-control arguments, the next is likely more of the same, applied to whichever parts of the interactive layout are still fixed.

P
patentsview
ANALYTICS
0.0

Dormant for years, then rewritten wholesale when the API underneath it broke.

◆ Current state

patentsview is an R client for the USPTO PatentsView API, and version 1.0.0 is less a feature release than a forced reconstruction: the upstream API introduced mandatory keys, renamed and re-nested its endpoints, and the package had to follow. Between 2017 and 2021 the release cadence was roughly annual and almost entirely defensive — wrapping examples so CRAN would not fail during API outages, patching URL encoding, adding throttling retries. The 1.0.0 work restores the package to parity with an API that no longer resembles the one it was written against.

◆ Where it's heading

The arc here is a client package whose roadmap is entirely dictated by an upstream service it does not control. Every release since 0.2.0 has been reactive — HTTPS migration, throttling, encoding fixes, and now a full breaking rewrite. The one forward-looking piece is retrieve_linked_data(), which follows HATEOAS links the API now returns, meaning the package is starting to navigate the API rather than just query fixed endpoints.

◆ Prediction

Expect the next releases to be small follow-ups against the reworked API — field list refreshes and error handling for endpoints that behave differently in practice than in the documentation. The entries do not show any independent roadmap, so anything beyond that would depend on further upstream API changes.

Alternatives to forestly and patentsview

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 forestly or patentsview.

See all forestly alternatives → · See all patentsview alternatives →

Recent activity from forestly and patentsview

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

  1. 5mo agoforestlyDownload button, AE filter label and diff toggle become optional
  2. 6mo agopatentsviewRebuilt for PatentsView's new API: keys, nested endpoints
  3. 11mo agoforestlyStatic RTF forest plots join the interactive output
  4. 1y agoforestlyreactR 0.6.0 rendering fix and slider label control
  5. 2y agoforestlyTreatment group selection and rough-edge fixes
  6. 3y agoforestlyFirst release on GitHub and CRAN
  7. 4y agopatentsviewMoves to HTTPS endpoints and handles API throttling
  8. 7y agopatentsviewVignettes dropped so CRAN builds survive API outages
  9. 8y agopatentsviewAPI examples wrapped in dontrun for CRAN stability
  10. 8y agopatentsviewcast_pv_data() converts returned columns to real types
  11. 9y agopatentsviewFirst release: query DSL for the PatentsView API

Frequently asked questions

What is the difference between forestly and patentsview?

They serve adjacent needs but don't currently overlap on shipped themes. forestly and patentsview 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 forestly better than patentsview?

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

What are the best alternatives to forestly?

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

What are the best alternatives to patentsview?

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