← Back to home
Comparison · Analytics

patentsview vs rlistings

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

Shared themes:r-package

patentsview vs rlistings: at a glance

Featurepatentsviewrlistings
SectorAnalyticsAnalytics
Velocity score0.00.0
Sparks · 30d00
Top themesapi-client, breaking-change, patent-data, r-packageclinical-trials, listings, pagination, r-package
Last editorial update5h ago1h ago
WebsiteVisit →Visit →

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 →

What is rlistings?

Clinical listings that keep inheriting their hardest problem — pagination — from the layer below.

rlistings renders clinical-trial subject listings and paginates them for regulatory output, sitting alongside rtables on the shared formatters engine. The releases in this window are dominated by pagination correctness: repeated key columns across pages, splitting by a variable, ordered-factor handling, column gaps, and font metrics. Development is a large rotating contributor set inside the insightsengineering organisation.

Read the full rlistings trajectory →

patentsview vs rlistings: editorial side-by-side

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.

R
rlistings
ANALYTICS
0.0

Clinical listings that keep inheriting their hardest problem — pagination — from the layer below.

◆ Current state

rlistings renders clinical-trial subject listings and paginates them for regulatory output, sitting alongside rtables on the shared formatters engine. The releases in this window are dominated by pagination correctness: repeated key columns across pages, splitting by a variable, ordered-factor handling, column gaps, and font metrics. Development is a large rotating contributor set inside the insightsengineering organisation.

◆ Where it's heading

The package is progressively delegating pagination to formatters rather than implementing it — paginate_listing() was refactored to call formatters' paginate_to_mpfs() directly, and truetype font support arrived through a new formatters API. That reduces duplicated logic but ties the package's page-break behaviour to a dependency it shares with rtables. Feature work beyond pagination is thin: better error messages for unsupported column classes, a cheatsheet.

◆ Prediction

Expect pagination fidelity to remain the focus, with changes arriving as formatters exposes more of its layout machinery rather than as rlistings-native features.

Alternatives to patentsview and rlistings

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

See all patentsview alternatives → · See all rlistings alternatives →

Recent activity from patentsview and rlistings

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

  1. 6mo agopatentsviewRebuilt for PatentsView's new API: keys, nested endpoints
  2. 1y agorlistingsError and message handling for difftime and zero-row listings
  3. 1y agorlistingsTrueType font support and col_gap in pagination
  4. 2y agorlistingssplit_into_pages_by_var() and pagination moved onto formatters
  5. 4y agopatentsviewMoves to HTTPS endpoints and handles API throttling
  6. 7y agopatentsviewVignettes dropped so CRAN builds survive API outages
  7. 8y agopatentsviewAPI examples wrapped in dontrun for CRAN stability
  8. 8y agopatentsviewcast_pv_data() converts returned columns to real types
  9. 9y agopatentsviewFirst release: query DSL for the PatentsView API

Frequently asked questions

What is the difference between patentsview and rlistings?

Both compete on the same themes — r-package — within Analytics. patentsview and rlistings 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 patentsview better than rlistings?

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

What are the best alternatives to rlistings?

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