I just want to throw in my two cents to stan for the desktop apps, even if it makes no difference. I came here while going down the rabbithole investigating the deprecated runtime used in the latest Linux Flatpak.
There’s a valid argument to be made that the desktop apps could, in an ideal world, be retired thanks to the growing popularity of Progressive Web Apps. Instead of maintaining an entire app, the web interface could simply be installed as a Chrome or Firefox PWA and run through the browser’s engine. The problem is that there’s seemingly no progress in STABLE codec support from actual web browser devs. Someone in this thread touched on that, but just adding codecs to the browser isn’t the only problem.
I have a dual boot setup with both Windows 11 and Linux Mint. On both systems it’s now possible to add native HEVC support to Firefox in different ways. I’ve been using it this way for around a year now. If I skip through several videos on Plex in a row (particularly my music video library), playback in Firefox will break completely until I restart the browser. When this happens I’ve noticed my swap space fills up completely. This is a big headache if I have multiple browser tabs or windows open to work in at the same time. Even though Windows and Linux have their own way of using swap, the same behavior happens on both. The consistent swap behavior leads me to believe there’s some kind of memory leak issue. It could be related to the HEVC/H265 codec itself (used by my entire library), but this problem doesn’t happen in the Plex desktop apps.
One would expect you might fix this by switching browsers, but Chrome seems to have exactly the same problem. It also doesn’t seem to be specific to Plex either, as my Jellyfin instance seems to do exactly the same thing in browsers. It’s really telling that this happens on two completely separate operating systems consistently, so it would seem strange to be tied to my specific computer.
Here’s where we have a triage problem. Self-hosted media servers are probably the primary way anyone will ever need direct codec support in their browsers. Most public-facing websites have robust server-side handling for video playback to flexibly transcode for any client. Very little attention seems to be paid to fixing direct codec implementation in web browsers for this reason. Firefox update after update, I never see this problem fixed or improved. Plex transcoding is an awesome option when it works, but it’s resource-intensive. Ideally the most stable way for a client to play should be direct if you have the bandwidth to support it. The majority of web browser users don’t have an urgent need for that browser feature to be stringently maintained, so it’s anyone’s guess if we’ll ever see the browser side improve.
These codec and memory problems don’t exist in the Plex desktop apps in my experience. Until web browsers fix whatever it is that causes these direct play stability issues, the desktop apps are a load-bearing structure for a stable experience on desktop. If Chrome/Firefox and their downstream variants ever fix these problems, by all means fall back to encouraging users to use PWAs. Chrome has good PWA implementation, and Firefox recently added it natively as well. Until then, I hope Plex devs see this and my appreciation for the reliability of the desktop apps. Please don’t consider retiring them before desktop users have a 1:1 stable alternative. My PC is still how I watch Plex 99% of the time.
I know the app continues to function even if development stops, but that doesn’t mean it won’t stop working eventually as PMS evolves.