McWanke,
First and foremost, thank you. A staff reply was what I requested, and I genuinely appreciate that you are the one to engage and that you put so much time and effort into your personal response.
While I truly appreciate the gesture and the perspective, the substance of the reply unfortunately doesn’t meet the expectations of my post. I had specific questions about product direction, and they have not yet been answered. I understand you may have to work within company policy and can’t always be completely transparent, but while your post said a lot, it didn’t contain the substantive clarity the community is looking for.
I can certainly appreciate the challenge you described. The idea that Plex can’t be the “magically perfect solution” for millions of different users is something I completely understand, and I don’t envy the difficult decisions your team has to make.
The distinction I’d like to make, however, is that this thread isn’t about asking for a perfect, personalized feature. It’s about understanding the removal of foundational, long-standing functionality that many of us relied on for years.
To use an analogy, it feels as if a car manufacturer issued an update that removed the volume knob from the steering wheel, telling drivers they can still use the main touchscreen. While technically true that the function still exists, it removes a direct, convenient control that drivers had built muscle memory for, making a simple task more cumbersome.
That is what’s happening here. When core behaviours, like managing a queue or a playlist directly on a client device, are changed or moved to a web-only interface, it feels less like an inability to please everyone and more like a fundamental regression of the user experience.
This is where my disappointment in the reply comes from. While I appreciate the sentiment and the well wishes for my media journey, it feels like a gentle pat on the back while the core questions that affect the entire userbase go unanswered.
To that end, could you provide whatever clarity you’re able to on these points?
-
Is making the web app the primary tool for tasks like queue management the official, intended direction for Plex going forward?
-
Is there a plan to restore these management features to the native clients, or should users adapt to the new web-dependent workflow?
Even a concise “Yes, the web app is the intended tool now” or “No, we have no current plans to restore that client functionality” would be incredibly valuable. It gives the community a clear answer to plan around.
Thank you again for your engagement. I hope you can see this is a request for clarity, not conflict, to help the community you’re working to build.