Roku Client updates?

[rookies 12]

Any major UI Experience or quality of life updates planed for this app?

[Luke 42077]

Hi, what would you like to see?

[rookies 12]

I was simply trying to understand the level of development currently going on with the client.

To answer your question, My initial impression of the client after 15 minutes of messing with it. Overall the app seems to be functional which is a good thing.

I would like to see an overall less frustrating more polished client. One example, it took 3 tries to get library display setting done right because there are no limiters on button actions that kick you out of that menu.  But really that is just an example for a task that I may never perform again, but still it detracts from the experience.  The app doesn't feel intuitive, and doesn't seem follow recognized formulas for where things typically exist. 

After my initial look at the app, the impression is that it is a clunky and non-intuitive design, but it looks good and seems to function. 

What I would like to see is a beautiful, intuitive, and efficient UI that works and is fun to use. I know my limitations.  So if you're looking for a list of things to change, I don't have that.   Just an impression and an opinion. A good UI Architect could tell you what changes would help. 

[Lazarus_Long 80]

3 hours ago, rookies said:

I was simply trying to understand the level of development currently going on with the client.

To answer your question, My initial impression of the client after 15 minutes of messing with it. Overall the app seems to be functional which is a good thing.

I would like to see an overall less frustrating more polished client. One example, it took 3 tries to get library display setting done right because there are no limiters on button actions that kick you out of that menu.  But really that is just an example for a task that I may never perform again, but still it detracts from the experience.  The app doesn't feel intuitive, and doesn't seem follow recognized formulas for where things typically exist. 

After my initial look at the app, the impression is that it is a clunky and non-intuitive design, but it looks good and seems to function. 

What I would like to see is a beautiful, intuitive, and efficient UI that works and is fun to use. I know my limitations.  So if you're looking for a list of things to change, I don't have that.   Just an impression and an opinion. A good UI Architect could tell you what changes would help. 

Just wondering (since you're coming from Plex), how does the Emby Roku app compare to the latest crappy release of the Plex Roku app?

I'm also a Plex user and working on switching over.  I don't use Roku devices (use Apple TV w/Infuse currently), but I do have other users with Roku devices so interested in what their experience will be like when I switch them over.

[speechles 2055]

On 9/21/2025 at 3:45 PM, rookies said:

I was simply trying to understand the level of development currently going on with the client.

To answer your question, My initial impression of the client after 15 minutes of messing with it. Overall the app seems to be functional which is a good thing.

I would like to see an overall less frustrating more polished client. One example, it took 3 tries to get library display setting done right because there are no limiters on button actions that kick you out of that menu.  But really that is just an example for a task that I may never perform again, but still it detracts from the experience.  The app doesn't feel intuitive, and doesn't seem follow recognized formulas for where things typically exist.

Which screen do you mean where the library display settings kick you out? You mean the "grid" and the display settings there? Or do you mean the main display settings area of the app?

 

On 9/21/2025 at 3:45 PM, rookies said:

What I would like to see is a beautiful, intuitive, and efficient UI that works and is fun to use. I know my limitations.  So if you're looking for a list of things to change, I don't have that.   Just an impression and an opinion. A good UI Architect could tell you what changes would help. 

Not really a list of things to change. A list of things you want. Then some things you find that you dont want. That would help us understand the end user. We have some things coming that will address the beautiful aspect. They should be coming in the next few weeks or so. We also have other things planned and in the works. I am part of the Roku development team at Emby.

I feel like we shouldn't need a UI architect to tell us what changes would help if they never use the app. Unless it was an app for UI architects to watch media with their friends. We want real users with real normal lives to give us their unbiased opinion of the app. What exactly they find annoying, and how much so, and why we aren't on the ball fixing it. Why isn't it fixed already? And just hammer us. Then as other users pile on believe me it causes valuable traction here that will move your issue higher and you will find it much better here as far as how we react to public opinion. When the tide turns you need to move with it. We will move with it.

What do you think in the app could be done more efficiently? I mean honestly. If you could directly communicate with the very people who help maintain and code the app and could tell them something what would it be. That is why we are asking seriously what would you like to see?

On the other side, I am also very curious what users do not like to see in the app and do not want to see in our app. Otherwise we usually do not get users vocal enough to really tell us like it is. You do not have to be afraid to pull punches or try to hide the bad news. Give it to us straight. It doesn't suck. Okay. We can start there. It is good. It does the job. Okay those are also good things to hear. But they don't really tell you the user is impressed or loving what you are doing. What would you love to see in the app? If you had like 3 wishes we can start there.

That is the difference between the other guys and us. Here we actually read and will respond to your posts. We feel the vibe. Understand you. Possibly. But at least we are here to get to the bottom of what you wanted to achieve by making this post. I feel the post is constructive and can lead to good things. You just have to let us know how you really feel. Thanks.

Note: We also won't remove your posts and try to act like everything is okay when it really isn't. We will actually tell you like it really is. In my mind, the app could be better. There are things we could do better. It is quite black alot of the time. There are no themes yet. There are some areas where there is a learning curve. I agree. This is why we need real users to give us the unbiased opinions to really know.

On the show "Silicon Valley" Richard tests his Pied Piper chat app with other developers and they don't find many flaws. They say it is really good. But he is Beta testing it with other developers. Those people will never really give you valuable input. Then they push the app out and everyone immediately hates it because they forgot to include a pool of real users in their testing. You need real users who find real issues/bugs and have real features they miss to improve the product.

Edited September 26, 2025 by speechles

[rookies 12]

10 hours ago, swallman said:

Just wondering (since you're coming from Plex), how does the Emby Roku app compare to the latest crappy release of the Plex Roku app?

I'm also a Plex user and working on switching over.  I don't use Roku devices (use Apple TV w/Infuse currently), but I do have other users with Roku devices so interested in what their experience will be like when I switch them over.

Well, funny you should mention that!  The new Plex experience for Roku is somewhat of a train wreck.  My environment is only used by my immediate family, so I don't have a very big dataset to go on.  The reviews are not great, but I suspect some of that is just resistance to change that all humans exhibit.   My wife was in the room when I was navigating around Emby for the first time.  She provided unsolicited feedback that she would rather stick with the new Plex interface over moving to Emby.  Part of that was she was witness to the behavior of Emby when you go to like favorites or something and the navigation highlight just disappears because there is nothing to show.   If I forced the switch, she would figure it out and likely be ok with it.  it is a functional and usable interface.

[rookies 12]

10 hours ago, speechles said:

Which screen do you mean where the library display settings kick you out? You mean the "grid" and the display settings there? Or do you mean the main display settings area of the app?

The screen where you can add and remove information to be displayed in the main grid,  like rating and release dates etc etc.

10 hours ago, speechles said:

Not really a list of things to change. A list of things you want. Then some things you find that you dont want. That would help us understand the end user. We have some things coming that will address the beautiful aspect. They should be coming in the next few weeks or so. We also have other things planned and in the works. I am part of the Roku development team at Emby.

hmm,  maybe I misunderstood the ask then. I am glad to hear there is active development on the app.  That is exactly what I was ineffectively trying to ask about.

10 hours ago, speechles said:

I feel like we shouldn't need a UI architect to tell us what changes would help if they never use the app. Unless it was an app for UI architects to watch media with their friends. We want real users with real normal lives to give us their unbiased opinion of the app. What exactly they find annoying, and how much so, and why we aren't on the ball fixing it. Why isn't it fixed already? And just hammer us. Then as other users pile on believe me it causes valuable traction here that will move your issue higher and you will find it much better here as far as how we react to public opinion. When the tide turns you need to move with it. We will move with it.

My comment wasn't to say that you needed a good UI Architect, but that I would need one to effectively communicate and understand what aspects of the interface are producing the initial impressions I got.   I appreciate that you took my post to heart as a developer,  it shows ownership!  Something that is both priceless hard to find in this day and age!  

10 hours ago, speechles said:

On the other side, I am also very curious what users do not like to see in the app and do not want to see in our app. Otherwise we usually do not get users vocal enough to really tell us like it is. You do not have to be afraid to pull punches or try to hide the bad news. Give it to us straight? It doesn't suck. Okay. We can start there. It is good. It does the job. Okay those are also good things to hear. But they don't really tell you the user is impressed or loving what you are doing. What would you love to see in the app? If you had like 3 wishes we can start there.

That is the difference between the other guys and us. Here we actually read and will respond to your posts. We feel the vibe. Understand you. Possibly. But at least we are here to get to the bottom of what you wanted to achieve by making this post. I feel the post is constructive and can lead to good things. You just have to let us know how you really feel. Thanks.

Note: We also won't remove your posts and try to act like everything is okay when it really isn't. We will actually tell you like it really is. In my mind, the app could be better. There are things we could do better. It is quite black alot of the time. There are no themes yet. There are some areas where there is a learning curve. I agree. This is why we need real users to give us the unbiased opinions to really know.

So far I have spent a sum total of half an hour looking at the app.  I did not intend my post as a slam against the product or the people behind it.  I was simply trying to communicate my initial experience with the product. Something I don't do exceptionally well.  Overall I think that it was mostly little quarks in the interface, what I call Quality of Life items. It was also likely also due to the layout, and menu systems.  Where things exist and how to or if you could accomplish something wasn't real intuitive to someone that doesn't already know the product.

11 hours ago, speechles said:

On the show "Silicon Valley" Richard tests his Pied Piper chat app with other developers and they don't find many flaws. They say it is really good. But he is Beta testing it with other developers. Those people will never really give you valuable input. Then they push the app out and everyone immediately hates it because they forgot to include a pool of real users in their testing. You need real users who find real issues/bugs and have real features they miss to improve the product.

Having done some development in my career. I understand this statement very well.  There definitely is a reason that developers should not test their own code. To quote the most interesting may in the world: "I don't often test my code, but when I do. It's in production!"  (You may be too young to remember the ads  if so take my word for it, this is funny!)

- Rookie

[ebr 16169]

1 hour ago, rookies said:

Overall I think that it was mostly little quarks in the interface, what I call Quality of Life items. It was also likely also due to the layout, and menu systems.  Where things exist and how to or if you could accomplish something wasn't real intuitive to someone that doesn't already know the product.

Hi.  Were these things demonstrably different from either the other Emby apps or other apps on the Roku device?

[rookies 12]

Don't really have a lot of experience with other Emby apps, other than the web interface app.  The Roku app seems to try and mirror the UI of the web app,  however the user interaction for a web app should (in my option) potentially be different than a TV app controlled by a remote. For example: compare it to the experience playing a built for PC game vs the interface of a game that was built for consoles and ported.  From a pc user experience the interface is almost always a pain with the latter.

Which I think may relate to what I am sensing. But in both cases I would expect most configuration options IE default behaviors to exist within a settings menu, and on the fly sorting and filtering to be accessible from the related screen.  That kind of stuff.  

Now Emby is absolutely not the only app that exhibits this kind of behavior, so comparing it to other apps that also are not very intuitive is not fair to either app.

I know I am being vague,  not really trying to.  Just can't put my finger on exactly what it is.   Hope this is at lease making sense.

[ebr 16169]

1 hour ago, rookies said:

however the user interaction for a web app should (in my option) potentially be different than a TV app controlled by a remote

Very true and the Roku app interface has actually been designed for remote control use on a TV exclusively.  That's why I'm struggling to understand your complaints without some sort of specific examples - but I would really like to...

[rookies 12]

Remember, I have spent 30 minutes looking at the Emby Roku app.

I am not really complaining about any specific thing per say, I don't know enough about the app to actually complain. I am simply stating what my initial personal feeling and impressions of the application are.  I have just gone back through this thread and I have identified at least 3 examples in this thread of what could possibly be detracting from a highly favorable first impression of the application.  It's not about these 3 things specifically though,  it's about the patterns and events experienced from the perspective of someone with no knowledge of the application, opening it up and trying to figure out how it works and what it can do.

Initially for this thread I was simply trying to figure out the level of development going on with the app. That was it, and it has turned into a round of 20 question!  

"One example, it took 3 tries to get library display setting done right because there are no limiters on button actions that kick you out of that menu."

"Part of that was she was witness to the behavior of Emby when you go to like favorites or something and the navigation highlight just disappears because there is nothing to show."

"But in both cases I would expect most configuration options IE default behaviors to exist within a settings menu, and on the fly sorting and filtering to be accessible from the related screens.  That kind of stuff. "

Also as a side note, I just remembered noticing settings for some options are controlled by the setting either on the server or in a location not accessible via the app,  how does that help the user who's only interaction will be via the Roku app? (I have several members of my household in this category)  Not sure of the specific options or what they did because I can't remember what they were. May be something they would never try to change. 

If we are going to keep going back and forth on this conversation, I am going to have to learn more about the app.  Which of course will change this conversation from "my first impression was"  to something entirely different. 
 

[rookies 12]

10 hours ago, ebr said:

Very true and the Roku app interface has actually been designed for remote control use on a TV exclusively.  That's why I'm struggling to understand your complaints without some sort of specific examples - but I would really like to...

So I got curious and I went back into the Roku app a few minutes ago,  I think I may have figure out one of the major things that set me off.   When your navigating in the app, the app changes the focus of where your navigation marker is on it's own.  It should not do that, it breaks the navigation experience when you have to hunt to figure out where you currently are.  This is most noticeable with the top bar navigation.  if you stop on anything it immediately moves the navigation focus to the main content of what you stopped on.  So if your going between say movies, suggestions etc etc. if you stop on any one of them the screen should paint, but the navigation should remain on the top bar unless a user action states to go into the content.  It is a special problem when there is no content and the navigation completely disappears leaving you with an unclear picture of what you would need to do to continue your navigation. Not sure if the app is doing this in other places as well, but it might be.

[ebr 16169]

17 hours ago, rookies said:

One example, it took 3 tries to get library display setting done right because there are no limiters on button actions that kick you out of that menu.

I'm afraid I don't really understand what you mean by "limiters on button actions"...

17 hours ago, rookies said:

Part of that was she was witness to the behavior of Emby when you go to like favorites or something and the navigation highlight just disappears because there is nothing to show.

So you brought up the favorites section (from the home screen I guess) and the focus went away?  We can definitely look at that.

8 hours ago, rookies said:

if you stop on anything it immediately moves the navigation focus to the main content of what you stopped on.  So if your going between say movies, suggestions etc etc. if you stop on any one of them the screen should paint, but the navigation should remain on the top bar unless a user action states to go into the content. 

Interesting.  This is the first time we've heard this feedback (that I can recall).  The thinking is that you want to interact with that section when you stop on it.

17 hours ago, rookies said:

That was it, and it has turned into a round of 20 question!

Because we'd like to understand and address your concerns.

Thanks.

[rookies 12]

19 minutes ago, ebr said:

I'm afraid I don't really understand what you mean by "limiters on button actions"...

if you move up it exits the menu, if you move right it exists the menu if you move left it exits the menu. if you move down beyond the last entry it exits the menu.

a nicer experience would be to limit this to say the back button on the remote and/or the left button on the remote.  So if you scroll right nothing happens, if you scroll up beyond the top item nothing happens, or if you scroll down beyond the bottom option nothing happens. This would prevent unintended closure of the menu.

25 minutes ago, ebr said:

Interesting.  This is the first time we've heard this feedback (that I can recall).  The thinking is that you want to interact with that section when you stop on it.

The assumption that just because you stopped you want the navigation focus to change is unique to this app as far as I can remember.  What if the user is just wanting to peek at that view before moving on. To change navigation focus typically it take an action, either an arrow key the back button or an ok button.  

[ebr 16169]

2 hours ago, rookies said:

if you move up it exits the menu, if you move right it exists the menu if you move left it exits the menu. if you move down beyond the last entry it exits the menu.

Which specific menu?  We should address this.

2 hours ago, rookies said:

What if the user is just wanting to peek at that view before moving on.

In the situation of someone  just learning to use the app, yes, I can see that.  However, as you stop discovering the app and start using it to discover and access your media, I think requiring the extra click would be more of an annoyance - and possibly why we haven't heard this feedback before.

So, yes, I see your point at a first blush but I think the behavior is advantageous once you are actually using the app for purpose.  I guess I'll be interested if you agree after a while...

I feel that, if we changed that behavior at this point, we'd have a lot of people complaining about having to have the extra click.

[speechles 2055]

2 hours ago, rookies said:

if you move up it exits the menu, if you move right it exists the menu if you move left it exits the menu. if you move down beyond the last entry it exits the menu.

a nicer experience would be to limit this to say the back button on the remote and/or the left button on the remote.  So if you scroll right nothing happens, if you scroll up beyond the top item nothing happens, or if you scroll down beyond the bottom option nothing happens. This would prevent unintended closure of the menu.

We discussed this. Our thinking was the user might instead believe they are trapped inside the panel. Pressing back can act like cancel the user may think. They may think that by using back their already applied changes will get dismissed. Then we thought.. hmm..perhaps if the focus moves off the panel we should close the panel? That was our thinking. We might need to rethink this if people are finding it clumsy and always closing on them. It was supposed to be a feature that moving off the panel would act as a back keypress. You consider this a misfeature?

Edited September 23, 2025 by speechles

[Gilgamesh_48 1240]

1 hour ago, speechles said:

Then we thought... 

You do realize that thinking is one of the most dangerous things that a developer can do, don't you?

"The mind is a terrible thing to use."  

[rookies 12]

2 hours ago, speechles said:

We discussed this. Our thinking was the user might instead believe they are trapped inside the panel. Pressing back can act like cancel the user may think. They may think that by using back their already applied changes will get dismissed. Then we thought.. hmm..perhaps if the focus moves off the panel we should close the panel? That was our thinking. We might need to rethink this if people are finding it clumsy and always closing on them. It was supposed to be a feature that moving off the panel would act as a back keypress. You consider this a misfeature?

my experience with other roku apps which is what creates the intuitiveness of the pattern is this,

a back button is either an exit or a cancel, (but either way should take you out of the menu)

an ok button should exit you out of the menu.

if the menu is on the right, a left arrow should take you out

if the menu is on the left a right arrow should take you out.

Typically you don't see a menu with an up or down arrow exit at all,  unless it is some strange case.  but I can' think of an instance of that I can remember. 

[rookies 12]

2 hours ago, ebr said:

Which specific menu?  We should address this.

  On 9/21/2025 at 9:52 PM, speechles said:

Which screen do you mean where the library display settings kick you out? You mean the "grid" and the display settings there? Or do you mean the main display settings area of the app?

The screen where you can add and remove information to be displayed in the main grid,  like rating and release dates etc etc.

 

2 hours ago, ebr said:

In the situation of someone  just learning to use the app, yes, I can see that.  However, as you stop discovering the app and start using it to discover and access your media, I think requiring the extra click would be more of an annoyance - and possibly why we haven't heard this feedback before.

So, yes, I see your point at a first blush but I think the behavior is advantageous once you are actually using the app for purpose.  I guess I'll be interested if you agree after a while...

Of course your right,  if second gear is broken in my car and I learn to go from first to third.  Eventually it's not going to bother me that second gear is broken because the workaround has become the norm. 

I can see where your navigating along and you have to stop and answer your wife or kid and now your navigation focus has changed.  Creating an extra click to get back up to the navigation bar.   I mean the extra click works both ways to some degree. but the extra click would also bring the behavior into line with what a majority of apps most people are familiar with encounter.  (creating intuitive navigational feel)

2 hours ago, ebr said:

I feel that, if we changed that behavior at this point, we'd have a lot of people complaining about having to have the extra click.

You may be right on the complaints from people who have learned the clicks.  Only way to find out would be to do it and see.  But at a minimum you should fix it so that if there is nothing for the navigation to land on, the focus doesn't just disappear altogether. that is really annoying, and just feels broken!  

[ebr 16169]

16 hours ago, rookies said:

Of course your right,  if second gear is broken in my car and I learn to go from first to third.  Eventually it's not going to bother me that second gear is broken because the workaround has become the norm. 

That wasn't really what I was saying.  My point was that, when using the app normally, you aren't likely to just be "peeking" under each of those headings.  You are much more likely to be going straight to the heading you want.

Behaving differently that we do now may actually be a bit of a technical challenge, but I'll look into it.  I can see both sides of this coin.

16 hours ago, rookies said:

But at a minimum you should fix it so that if there is nothing for the navigation to land on, the focus doesn't just disappear altogether

Yes, that's clearly a bug.  Of course, it would be solved by changing the behavior...

[rookies 12]

1 hour ago, ebr said:

That wasn't really what I was saying.  My point was that, when using the app normally, you aren't likely to just be "peeking" under each of those headings.  You are much more likely to be going straight to the heading you want.

Agreed, it wasn't what you were saying, yet it would in fact be the net result.  Which was my point.   "using the app normally" means I learn the new pattern set forth by the current behavior and it becomes the norm.  Even if it is not the norm for other apps on the same or similar platform.  What makes you resist is that you have "trained" your user base and developers that the app is used X way based on decisions that have already been made and they complied in order to use the app.  Now weather or not they realized that second gear in their car was broken in the first place.  They now understand and expect to go from first gear to third gear.  All I am doing is pointing out that second gear is actually broke.  If I use the platform, I too will comply in order to use the app, and at some point will stop noticing that second gear doesn't work right.  Each new user to your platform will go through this transformation weather they actually notice it or not.

On 9/21/2025 at 9:52 PM, speechles said:

On the show "Silicon Valley" Richard tests his Pied Piper chat app with other developers and they don't find many flaws. They say it is really good. But he is Beta testing it with other developers. Those people will never really give you valuable input. Then they push the app out and everyone immediately hates it because they forgot to include a pool of real users in their testing. You need real users who find real issues/bugs and have real features they miss to improve the product.

This trap also applies to long term users of an application.  and it is because of the bias towards continuing known patterns.  right or wrong.  At least this is my observation based on experience.   What I am pointing out is the patterns of design more so than this one single observation you have latched onto.  There may or may not be other examples where the application deviates.  This is why I initially did not want to go down this road.  Who am I as a user of your app for about an hour to tell you what design patterns you should use.  Nobody. 

As a new user though, I don't have pre-conceived or trained behaviors established yet, and therefore notice perceived pattern deviations for what others view as normal app behavior.

[rookies 12]

This is what creates the initial impression of an application. Which can effect both adoption and retention of users.

[ebr 16169]

Regardless, I think you have a good point with the tab focus behavior so we'll look into it.

Thanks.

[rookies 12]

I hope this conversation was helpful,  and I cannot stress how much this isn't about the navigation element alone. 

It's about where you go to find things, how thing are accomplished. It's about how many new pattern are introduced that have to be learned.

For instance:  Settings seem to be strung out all over the place with very little actually being included in your setting menu.  Oh and the setting menu layout is like nothing I have ever encountered before making it initially disorienting to navigate.  Both of these things and more, mean I have to learn new patterns for interacting with the app, before I can go about the business of actually learning the cool stuff it can do.  

[speechles 2055]

1 hour ago, rookies said:

I hope this conversation was helpful,  and I cannot stress how much this isn't about the navigation element alone.

There are some differences in the navigation. There are nuances to how things are done. Some of them good. Some of them bad.

1 hour ago, rookies said:

It's about where you go to find things, how thing are accomplished. It's about how many new pattern are introduced that have to be learned.

For instance:  Settings seem to be strung out all over the place with very little actually being included in your setting menu.  Oh and the setting menu layout is like nothing I have ever encountered before making it initially disorienting to navigate.  Both of these things and more, mean I have to learn new patterns for interacting with the app, before I can go about the business of actually learning the cool stuff it can do.  

Agree. The settings menu is from the very early days and not much has been done to give it a makeover. That area is something that all users must get through so spiffing it up and making it more intuitive and pretty isn't a bad idea. I do agree the format it is using to present some information gives it a cluttered and redundant look. We can look at fixing that.

The General settings can be accessed through the "cog" at the top of the homescreen or using the "star" button on the remote.

The "grid" settings can be accessed from the toolbar of the grid.

The landing tab setting for each library section can be set by entering that library and pressing "star" and choosing "set default tab"

----

Issue #1731: Need Sidebar (left-side vertical menu) just like web app
Issue #1730: *** top secret ***
Fix #1729: [DetailsView] load backdrop immediately do not wait for tasks to load
Issue #1728: Backdrops do not show/rotate when the "Video Themes" plugin is used just a black screen is shown

----

The above are the real issues and fixes we have planned for the future. You can see #1731 is on there. Cannot say when we will start and when that will be complete but I can say it is on there. For #1730 it is something held close to the vest and I cannot show. It is best to be surprised with that one.

If you can give us some screenshots of where you are having issues and how it interrupts your workflow of enjoying the app we will be more than happy to listen to those concerns and perhaps solve them. We are a team at Emby and actually use the software ourselves. I personally use the Roku app more than any other app. I am very interested in hearing what can be improved. I already know what personally I find aggravating and I cannot push my agenda higher than users. So if users find the same issues I am already having personally we can have a win win situation. You get the fix in the app and so do I. And even faster. That is why we need input from people to give us nudges in those directions they want us to move.

I added the issue you mentioned to our tracker, see below. Thanks for being part of Emby and helping us help you.

Reference: Issue #1733: [Settings] Update the panels to a more modern look

Edited September 27, 2025 by speechles