This has been a very interesting thread, and a very long one at that. Roon essentially morphed into a quite different product as from its conception. Roon, at the beginning, was like the ultimate LAN player; a far superior version of JRiver and Foobar2000. Linn and Sonos had their systems developed in a similar vein. Prior to working as a data architect, I used to work in the high-end audio industry and built up a substantial system of components, the central piece being PS Audio’s DirectStream DAC, which connects to my LAN through an Ethernet cable. For those not in high-end audio, we’re a little ‘old-school’ in some ways. Wires in preference to wireless, for example. We value resilience in the architecture of the system.
Roon has moved into a very different world along with the likes of Tidal, Spotify and PlexAmp with the introduction of its ARC app. Roon may become very successful and grow but with a new audience and customer base who never approached Roon as a product for what it originally started out with. Perhaps they will become more profitable with the new user type, but naturally, those who grew attached to Roon feel abandoned as if we were sold a juicy steak at a restaurant and end up getting fish, to quote a crude analogy.
Saying that, this thread resonates strongly with me as in my current role, I am working on a data project for a business to ensure that Internet resilience is part of the scope. For those in the data field, you may have come across ‘the Cloud’ and On-Prem (‘prem’). Essentially, this serves as a hybrid solution if the Internet fails. For example, I used to work in the South Australian courts data team and we had to ensure that resilience to the failure of the Internet.
I am also about to host a keynote speech on systems resilient to the Internet, and this piece will be cited. Not naming Roon of course, but will give a current example in this particular industry. What can be learned? How should the software developers engage with their userbase? Are thorough SDLC systems in place and if so, what are the contingencies and fallbacks.
The owners of this forum are obviously being given a bit of a deluge of feedback, but this is a perfect example of what not to do. I did mention it earlier, but such principal changes to a product’s mission and philosophy is bound to rile up a stir, but it’s not all doom and gloom. The market as a whole continues to improve and there are always opportunities for others to ‘fill in the missing holes’. I, for one, have done quite a lot of extensive research into similar systems I’ve not heard of before, simply because I didn’t bother to do any research because Roon was the solution to my music problems.
Roon 2.0 will attract a different person, but it’s too risky for me to rely on Roon alone with my system, a system that connects to a vast collection of own music files, most ripped from my extensive CD collection.
Perhaps I’m a dinosaur…