Latest Roon Interface Update - Back button position

Hello,

I would like to share some feedback regarding the latest update to the Roon interface. The relocation of the “Back” button (previously at the bottom of the screen and now at the top) makes navigation less intuitive and less practical, especially for quick browsing.

This change disrupts my user experience for the following reasons:

- It breaks a long-standing habit.

- It is not ergonomic for one-handed use on mobile devices.

- In my opinion, it does not provide any functional improvement.

Suggestions:

Could you consider:

1. Reverting the “Back” button to its original position at the bottom of the screen?

2. Adding a setting option to allow users to choose its placement (top/bottom)?

I understand that updates aim to enhance the overall experience, but this small detail has a negative impact on my daily usage. Thank you for considering this feedback for future versions.

Best regards,

Just to add to this feedback. The back chevrons are inconsistent in appearing and/or appear when they shouldn’t.

In order of navigation (steps 3, 4 & 5 are correct. Home Screen to side menu back but goes to previous album view in stead of Home Screen. Step 6 shows me going back to the side menu and the chevron has vanished)
1)

I can honestly not remember when this was the case? Do you have a timeline or screenshot?

Or, are you using a “small screen” portable, i.e. a smart phone?
(I rarely use the phone for navigation, only ARC)

Nor I. I’ve used gestures on mobile for so long. I see images of the buttons in the current location from 3+ years ago.

The return route used to be this way; it was much more convenient than the one up to the left.

That area is the OS, not Roon.

3 Likes

This may be related to an issue that Roon 2.70 (inadvertently) introduced when using some older versions of Android. I have a tablet running Android 14 and the OS back button (bottom of the screen) minimises the app. Only the Roon UI back button (top of the screen) works correctly. My phone (Android 17) doesn’t have the issue.

1 Like

Hello, thanks for your feedback.