bevanc
500+ Head-Fier
I've experienced no bugs, the early access support thread was uneventful. But that is probably due to the simplicity.Let's see…
- No CarPlay or Android Auto support. — And I wouldn't hold my breath, considering that they are a) "investigating support" for those, which is marketing speak for "we really don't want to, so let's wait and see how annoying users get over this before we commit any effort to it," and b) Roon is written for .net (a set of libraries that are not native to the platforms they run on), and at least for CarPlay (but potentially also Android Auto) they would have to re-implement at least the UI and some code in Swift using native libraries — something they completely lack any institutional know-how for right now.
- Offline-listening for local content only (i.e. not for any Tidal or Qobuz content)
In short: A major release (going from 1.8 to 2.0) for a feature that a TON of people asked for for years — which is fair — but that received — in typical Roon fashion — an implementation that is half-assed and unfinished at best. And probably buggy as all hell, too, for the next three to six months, if past experiences are any indication.
More new lipstick on the same old pig. They either can't do better, or they don't have to. Either way, it's really time they get some serious competition in the field.
(The usual disclaimer applies whenever I post something about Roon: I appreciate that some of you love this thing, and I'm glad that you do. More power to you. But as a seasoned software developer with a strong background in quality control and UI/UX design, the standards that I apply to the software I want to use personally are admittedly brutal, but still fair. I know how much better something like Roon could be done, for considerably less money than they ask for. And that just angers me.)
And I doubt that Qobuz and Tidal/ record labels will allow 3rd party downloads.
I've also been able to play over USB whilst using Android Auto.... I'm happy with it so far.
Last edited: