← Back to home
Comparison · Infra & APIs

dialr vs TrendLSW

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

dialr vs TrendLSW: at a glance

FeaturedialrTrendLSW
SectorInfra & APIsInfra & APIs
Velocity score0.00.0
Sparks · 30d00
Top themesphone-numbers, libphonenumber, rjava, r-packagetime-series, wavelets, defaults, plotting
Last editorial update2h ago4h ago
WebsiteVisit →Visit →

What is dialr?

The R phone-number package stopped only parsing numbers and started asking them where they are.

dialr wraps Google's libphonenumber through rJava, giving R a phone vector class that parses, validates and formats international numbers. It has been quiet since August 2022, when the last release removed a pathology where Java would freeze after enough invalid inputs. The package covers parsing, validation, formatting, and the metadata lookups added in 0.3.0.

Read the full dialr trajectory →

What is TrendLSW?

Wavelet trend estimation tightens the defaults it shipped with.

TrendLSW estimates trend and evolutionary wavelet spectrum for locally stationary time series through a single TLSW() entry point. Its history since the first CRAN appearance is short and centres on defaults and plotting around that function, plus one dataset addition. The latest entry carries both the 1.0.4 and 1.0.3 notes in one body.

Read the full TrendLSW trajectory →

dialr vs TrendLSW: editorial side-by-side

D
dialr
INFRA · APIS
0.0

The R phone-number package stopped only parsing numbers and started asking them where they are.

◆ Current state

dialr wraps Google's libphonenumber through rJava, giving R a phone vector class that parses, validates and formats international numbers. It has been quiet since August 2022, when the last release removed a pathology where Java would freeze after enough invalid inputs. The package covers parsing, validation, formatting, and the metadata lookups added in 0.3.0.

◆ Where it's heading

Two forces shape the history. One is expansion into what libphonenumber knows beyond the number itself — carrier, geocode, timezone — which happened once, in 2019, and has not been extended since. The other is the ongoing cost of being a Java wrapper inside an R tidyverse: rJava initialisation moved so the :: form works, phone vectors reclassified when tibble 3.0.0 changed how it treats list-based classes, and repeated performance work to make crossing the Java boundary tolerable. The maintainer has floated moving the phone class onto vctrs but has not.

◆ Prediction

The vctrs migration is the one change the maintainer has explicitly signalled, and the hard-deprecated one-shot functions were slated for removal in the next major release; three years of silence make neither imminent.

T
TrendLSW
INFRA · APIS
0.0

Wavelet trend estimation tightens the defaults it shipped with.

◆ Current state

TrendLSW estimates trend and evolutionary wavelet spectrum for locally stationary time series through a single TLSW() entry point. Its history since the first CRAN appearance is short and centres on defaults and plotting around that function, plus one dataset addition. The latest entry carries both the 1.0.4 and 1.0.3 notes in one body.

◆ Where it's heading

The package has moved from getting onto CRAN to correcting the choices it launched with: the spectrum filter defaults were swapped to their trend counterparts, the plot.CI switch was removed in favour of inferring it from what was actually computed, and an example was shrunk to fit check timings. This is consolidation around a stable API rather than expansion.

◆ Prediction

Further releases most likely continue tuning TLSW() defaults and plot behaviour; the entries show no work toward new estimators.

Alternatives to dialr and TrendLSW

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 dialr or TrendLSW.

See all dialr alternatives → · See all TrendLSW alternatives →

Recent activity from dialr and TrendLSW

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

  1. 8mo agoTrendLSWTrend filter defaults replace spectrum defaults; plot.CI dropped
  2. 2y agoTrendLSWNew z.acc and z.labels datasets shipped with the package
  3. 2y agoTrendLSWDescription field and plot.TLSW documentation fixes
  4. 3y agodialrInvalid values short-circuit the Java parser, fixing a freeze
  5. 5y agodialrJava initialises on load, so :: calls work without library()
  6. 6y agodialrR 4.0 bump and tests decoupled from libphonenumber data
  7. 6y agodialrPhone vectors work in tibbles again after the 3.0.0 change
  8. 7y agodialrCarrier, geocode, and timezone lookups added
  9. 7y agodialrTenfold rJava speedup and proper phone equality

Frequently asked questions

What is the difference between dialr and TrendLSW?

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

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

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

What are the best alternatives to TrendLSW?

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