To enhance the user experience and eliminate any confusion, we’ve made a small but significant change. While the app installed on your mobile devices is named “Roon,” our app store listings have previously referred to it as “Roon Remote.” To ensure consistency and clarity, we have updated the name in the all app stores to “Roon". This adjustment is intended to prevent any misconceptions that the app is only for ‘on-the-go’ use due to the term “Remote.”
This name change is already live on Google Play and the Amazon Store. iOS users will see the updated name with the release going live today (build 1457). Rest assured, the app’s functionality remains unchanged and is identical to the current version. You can find more details in our release notes here.
We believe this change will help new users better understand and utilize all the capabilities of our app without any confusion about its purpose.
Thank you for being a valued part of our community and for choosing Roon for your music experiences.
It’s been fairly easy around these parts, when users are supporting other users, to distinguish between Roon, which runs on a computer in your living quarters and points to your music collection, and Roon Remote, which is used as a controller…I could see this being confusing for many people moving forward, as if we were to start calling our TV remotes in a manner like: “Would you please toss me the TV?” and not “Would you please toss me the remote?”
I mean, I know the iOS icon already says “Roon,” but allowing/encouraging users to distinguish “Roon Remote” from “Roon” has been very handy over the years…
Now if you are getting ready to allow an iPad or iPhone to run Roon as a server, then consider this whole response moot
EDIT: FWIW, I never get confused about my ability to only use my TV remote in my house.
EDIT 2: I recommend somebody at Roon go back and contemplate all of the printed explanations/tutorials in Stereophile, Absolute Sound, and other such publications (not to mention countless online sources) that have explained the different Roon components so well over the years. These search results should have meaning to Roon:
SukieInTheGraveyard
(This one time, at Bandcamp... I spent too much money!)
10
Have to agree with the responses so far. The distinction between Server and Remote is well established. Simply labelling everything “Roon” seems somewhat counter-intuitive.
@Jim_F makes a good point though. If there needs to be a change in name so as to remove the confusion surrounding the word “remote”, find a different word to differentiate Server from Remote.
Maybe Roon ARC will eventually become Roon Remote. ARC is just a name, it doesn’t actually mean anything AFAIK but happy to be corrected, calling it Roon Remote would make sense other than the fact the name was taken, until now.
Sounds like a bad boardroom decision or some crappy think tank. This is going to cause more issues than it solves with more of why does Roon not work on my phone support queries. Feels like the same reason the funnel got changed it didn’t need to but someone thought it was a good idea. Now people trying to find radio stations use the wrong search area and wonder why they can’t find them.
Right. While the naming scheme should be split clearly and cleanly three ways to reflect the different responsibilities, the names themselves are subject to tweaking.
Roon Client is an idea, as is Roon Control or Roon Controller. Because if you want to control Roon on a device, you need a controller.
Roon Server is fine, though Roon Core seems more beloved. But it has some potential issues. Roon Core may be perceived as “core” meaning “basic.” And then people may assume that there is another offering with more features, like a Roon Pro.
As for just Roon to reflect a bundled download, installer, and launch package, no, that has been a problem. Too many users fail to know if they have Roon Server running or even installed. Or they have Roon Server running but do not know how to control it. Thus, no more bundling. Separate downloads, installers, and launch icons for everything.
I never liked “Roon Core.” What is a core anyway? Roon Server is more descriptive to me. I also agree that separating the Roon Server and Roon Client software makes the most sense. I’m not sure why Roon combined them in the first place. So, in my mind it would be:
Roon (the brand)
Roon Server Core (for computers)
Roon Controller Client (for computers, phones, and tablets)
Roon Anywhere Player (for phones and tablets)
Roon Endpoint Bridge (for endpoints)
Or something similiar.
EDIT: @danny Maybe Roon should form an “advisory panel” of about 5 highly active customers to run by ideas before implementing them.
The advantage to the Roon Core name is that it emphasizes the central “core” aspect of Roon architecture. Anything and everything runs through the “core.”
Along similar lines, the downside to the Roon Server name is that may be perceived as the “server” of local music files. Some new or potential users mistakenly assume that they do not need a “server” because they do not listen to local music files, only streaming service(s).
I have solved the problem by deciding to call everything Roon now. No more learning discrete names for discrete things for me. Roon? Roon roon. Roon, roon roon!
Roon roon.
Hello, support? My Roon isn’t working.
Is that your Roon-that-serves-music, your Roon-that-controls-music, the Roon-that-feeds-an-endpoint-connected-to-another-computer, or Roon ARC, the Roon-that-plays-when-you’re-away-from-Roon?
