Skip to main content

New App vs. Previous Version


To the engineers and developers who worked on this project, I am sorry, this is a major fail. I imagine you all in a conference room working in your little scrum teams with your white boards littered with notes. But the one note which was missed was the #1 requirement of end users of all music related apps, that is they MUST be user friendly. Quick and easy access to the features. My advice too quickly right the ship, is to focus the majority of your efforts in creating an easy option for users to revert to the previous version within the app. Those who are ok with the new version can stay put. The sooner you accomplish this the sooner this fire goes out! 

Did you find what you were looking for?
This topic has been closed for further comments. You can use the search bar to find a similar topic, or create a new one by clicking Create Topic at the top of the page.

3 replies

buzz
  • 23899 replies
  • June 30, 2024

I doubt that this easy rollback will be offered because it does not support the headphones.

While not publicized heavily, there's also a new ROAM 2. I don't know if previous controller versions will support ROAM 2.


Bumper
  • 1767 replies
  • June 30, 2024

The people who bought Roams could use the new app too if required. 


  • Author
  • Contributor I
  • 2 replies
  • July 1, 2024

I’ll go out on a limb and say that the number of people who would elect to “rollback” would far outweigh those who choose to continue with the new app. And if I’m not mistaken, it would be a quicker and less costly solution. 


Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings