This is a bit of an open letter to Roon principals, who we don’t see around here much.
I adore Roon. I love its premise, its interfaces, its vendor-spanning architecture. In spite of that, I find it frustrating and often quite depressing. Years ago, I recommended Roon to friends. I don’t now. My audio setups are fun to play with and sound pretty good. When we entertain, people like to play with my Roon installation and the custom volume controls I’ve got everywhere. When they’re curious about setting it up themselves, I discourage them. I live with its flaws and issues, as do many of us, but I don’t consider it a good product. I consider it a finicky product that’s hard to set up and has inconsistent quality over time.
I’ve worked in the software industry for decades. Many of us have worked in tech in one form or another. I didn’t start running mega services, there was no such thing when I was coming up in the industry, but I did end up there. Big services.
We evolved a fundamental way of thinking about quality and features. It’s simple. You work in the following order.
- Reliability. If data goes into the system, it always comes out. No corruption, no data loss.
- Availability. The system always works. When a user wants to do something, they can.
- Performance. The system works quickly. The user never has cause to notice or complain about performance issues.
- Features. You earn the right, as engineers and product owners, to build features when your product meets reliability, availability, and performance targets. It’s a privilege. You earn it.
Here’s a well known anecdote. In the early days of facebook, Zuckerberg’s mantra was “Go fast and break things.” It was posted on the walls. It was smart. It got them moving quickly and the laddered into owning the market. Then an intern pushed a change and took the site down hard. Users were really upset. It was a defining moment. Zuckerberg read the room and understood that they had evolve. The mantra became, “Go fast on stable infrastructure.”
This is so important. You need stability in the foundation to build a building. You need it in software, too. Users love features. But they love reliability, availability, and performance even more, even if they don’t know how to articulate it. If your mobile carrier can’t deliver reliable dial tone and high quality audio calls, than no amount of T-Mobile Tuesdays (where you get free stuff at least here in the US) will help you acquire and retain customers.
I know the people on this forum who will show up here and be dismissive of this. I get it - they feel protective and have the time and energy to form what some folks call the “Roon Defense Force” or, colloquially, the RDF. That’s fine - this forum is generally pretty good at allowing civil discourse and defending Roon is a valid for of that. But there’s a pretty good size population of people here that will agree my basic premise, which is that Roon does not have a stable foundation. This upcoming “announcement” will delight some and be dismissed or ignored by others, but it is a tough story to swallow when it feels like Roon needs real attention at the foundational level to be the truly phenomenal, easy to love, and easy to recommend product that it should, by all rights, be.
The list of fundamental issues is sort of long. Just a taste:
-
Database corruption. It happens insidiously. It happened to me. The database goes silently corrupt but continues to get backed up without issue and at some point, the corruption surfaces, the user is notified, and finds that their backups are corrupt, too
-
Search. Sort of works. A couple of years back there was a guy hired to address it, there were some big blog posts, a commitment to making it great. It got a little better, and then nothing.
-
Network discovery and reliability. I can’t say enough about this. We’ve grown accustomed to accepting that Roon can be flaky about finding devices and has issues with wireless and various networks, etc. This doesn’t have to be. Even just investing in user-facing diagnostic tools in the product would be a major step forward - put the capability into Roon to show a user what the bandwidth, latency, whatever is to a specific Roon Ready device. Be willing to open up RAAT and make some investments in working better in more diverse network environments.
-
Box sets, metadata, etc. We hear about these problems from people regularly. We know they’re lurking in there. We know they’re probably really hard to fix. Fix them anyhow.
-
Memory leaks, crashes, serious issues that break usability. These show up and can take weeks to fix. A recent version introduced a crash in the iOS apps that causes the apps to quit when clicking on certain objects in the UI. I’m hitting it. Others are reporting it. This should be an emergency fix within 48 hours at the most. It should be accompanied by a humble apology and the community should feel heard and taken care of. It’s not like that at all.
I’m a reasonably influential person in my little circle of peers and friends. This isn’t unique to me. I’m an enthusiast in a variety of areas. If I loved Roon - I mean loved the company, the product, felt like it was really great - I’m pretty confident that this would result in me bringing on at least a couple of new users. Maybe more. Instead, I tell people to stay away from it.
This is truly intended as an open letter. If Roon principals actually are around and have the interest in engaging here with me or others in the community, I expect we would welcome that. Don’t just give us a new feature - come and talk to the community. Win us over again. Make Roon the absolutely delightful product it can and should be without the caveats and concerns. I hope you take me - maybe us - up on this.
Thanks for reading.