Thanks @cayars - you also bring up another point that I believes warrants dissection: dominance in UI design of single-point of entry mechanics.
Who were the clever people that decided only having one option to initiate any action in UI was best practice? They should be chastised. Severely.
There’s been a massive trend in UI design in the past 6? years of whittling down the way users interact to only offering them the single most ‘popular’ way of performing a function. I understand the original intent, to avoid ‘confusing’ users by giving them too many ways to learn to do something. It sounds in principle like a good idea, however in reality humans thrive on diversity.
Sure, double the UI elements to maintain (eg: having to maintain working top and side menu systems) adds to the burden on the development team, however failing to provide an interface that allows people to do things the way they want to do them places a burden on your support and creates a poor public image.
It grates on me when UI is designed with this single-rail mentality, as it’s often based on what are ultimately flawed statistical analysis (flawed due to the sample size, the sample participants and then flawed by the analysis itself) and packaged as “Customer metrics show most people access things through this button, whilst this other button was rarely used.” Sometimes such analysis is beneficial, most often though that analysis should focus on why the underutilised element was underutilised. Sadly though it is almost universally used as ammunition to justify the removal of the element. That kind of cut-throat pursuit of single design might be appropriate for some hand held device interactions, but it cannot (and no designer should endorse it) be applied universally across varied platforms.
I’ve not had much issue with the UI on Android and iOS, which are the other two platforms outside Xbox that we use, and I’ve used the web front-end from time to time obviously, so I may have missed some “advances” in this common-UI being pushed out.
It’s a terrible decision to have the same UI everywhere. Personally I don’t care if the UI is different between platforms, so long as it works on every platform. Designers know this (or they should). An architect doesn’t produce one efficient house design and then just sell that to every client.
Which can all be summarised to: devolving the Plex client UI to a common design was never going to, and will never, work across all platforms.