

That’s nice.
That doesn’t work if you are on an airplane (unless you want to spend the entire flight downloading one episode). Or if you just don’t want to deal with hotel wifi. Or if you just don’t want to expose your internal home network at all.
Which is the point and why this is one of those big features of plex that there are so many tickets and requests to get into jellyfin et al. Because yes, you can just copy files from your NAS to your phone’s internal storage (assuming you don’t care about transcoding and the like)… at which point there isn’t much use to a metadata oriented media server/service.
Or you can just set up Plex to always download the next 10 episodes of whatever show you are watching when it has network access. I mean… that probably won’t work (see: 40%) but when it does, it is awesome. Which is the “it just works” functionality.
Which gets back to the issue where, because it is FOSS, it is the greatest thing ever and anyone asking for anything else is wrong and stupid. Which is a shame because if the Jellyfin devs could actually get the “download the next N episodes” functionality to reliably work (even at 80-90%) it would be a killer app. And, for what it is worth, I have liked the devs a lot when I interacted with them in the past. But the users and evangelists are just… what we can see in this thread.
Part of it is that Ubuntu/Canonical so aggressively pushed Snaps which became a huge culture war. So you have people who hate the idea of those style of packages because they hate Snap AND people who hate flatpak because they are Team Ubuntu for some reason.
And the other aspect is that it is incredibly space inefficient (by the very nature of bundling in dependencies) and is prone to “weirdness” when it comes to file system permissions and the like. And many software projects kind of went all in on them because it provides a single(-ish) target to build for rather than having a debian and an arch and a redhad and a…