Roon Roadmap?

[Menzies (I’m a Roon user)]

A discussion point based on

How do people typically mark artists/albums for future exploration?

The most recent release was a step in that direction, with bans now supported outside of the library. Ultimately, covering all of the cases in one go is a big lift that would require basically stopping release cycles for 5-7 months while we rework some pretty fundamental aspects of how the library works. From past experience, the community tends to punish us when we don’t release often enough, so we don’t really have a choice but to approach something like this incrementally, which obviously t…

How do people typically mark artists/albums for future exploration?

I’m all for a slower development cycle. Since you switched it up things have not been as smooth from my experience.

How do people typically mark artists/albums for future exploration?

I’m all for a slower release cycle to. If it gives Roon more time to dot the i’s and cross the t’s and conduct thorough QC in house, then I’m all for that. Find and fix known long standing issues. Make Roon new user proof. I also think early access should be a closed program to a select number on an invitation basis. While new features are wanted by some, they’re not for everyone. I think introducing features with an opt in or means to disable features unwanted is a must.

How do people typically mark artists/albums for future exploration?

Roon use to have a longer release cycle and people complained. Some years ago they started releasing updates much more frequently and people complained. Roon simply can’t win. I’ve not noticed a difference in stability/introduced bugs between the longer release cycle and the shorter release cycle.

How do people typically mark artists/albums for future exploration?

Please can the @moderators break these posts out into another thread. FWIW, I blame @brian for going off topic I think it’s a valid discussion point. An option maybe for users to select update cycle periods. @Saturn94 it’s an odd beast this Roon. For a good while I was issue free, then a few minor niggles crept in. I just feel that if Roon’s dev team is small, are they best working on bigger things rather than smaller things. A Roon roadmap would be good.

Would fellow Roon users prefer regular updates and longer release cycles?

Would longer release cycles help, for some, fix long term issues?

A Roon (live) roadmap would be good.

[Saturn94]

@Menzies

A Roon (live) roadmap would be good.

I seriously doubt this will happen. Roon has been burned in the past talking about future plans, hence why they stopped doing it. Then again, a folder browser feature was one of those things that would never happen.

This is pure speculation on my part, but I think Roon’s main issue regarding development/bug fixes/customer support is lack of staff.

[Menzies (I’m a Roon user)]

@Saturn94

This is pure speculation on my part, but I think Roon’s main issue regarding development/bug fixes/customer support is lack of staff.

From 2021, would be more I hope by now

@mike

Over the last year, we’ve doubled the Roon team to over 50 people across five continents, which allows us to be more ambitious in the scope and number of engineering projects running in parallel. One great example is search, which is now being improved on an ongoing basis by our data team. This release features the first of many planned search developments: an improved user interface with predictive auto-complete.

[Einar_Torshaug (// Evolving "MixTape" on Shuffle with Roon //)]

Having worked with software developement and product portfolio management, though in a different market than Roon, my experience is that the Roadmap is classified as company confidential information not to be shared with customers and competitors.

One of the reasons for this is that most software related product today uses agile development methodologies which includes frequently re-prioritizing of the product work-backlog(s) due to changes in market/technology/resources/budgets/strategy/partners/Maintenance vs “New”… etc. Prio’s is often done from pain(effort) vs gain (customer value) and not necessary how many votes or attention one specific new features gets.

[Abrahams_Bogere (Abe)]

As someone that works on product. I can tell you roadmaps change based on requirements and such. I suggest we be patient and enjoy. Many times new things don’t work out as well and compromise the software (see the Sonos situation). I think Roon should keep it private until ready to release. I’m ok with that. Trust me I would have said different if I wasn’t in this field.

[Jim_F (Minimalist)]

Under promise, over deliver.