2025-02-28, 03:17 PM
I use Jellyfin and have an LG TV as my main client, and it works fine for shows and movies, although DV support is terrible (as a result of LG's poor implementation of it on most of their TVs) and I just strip it out completely in favor of HDR10. As mentioned, the official app for WebOS is just a web wrapper since it's simply the intended way in general for running apps on that OS, hence the name.
That said, I prefer it because native clients are often missing some features that are present on the web client, and you do benefit directly from the web development of Jellyfin; the tradeoff, however, is that performance is going to be more dependent on network stuff instead of the hardware side of things. It can be rather slow even if you have an efficient setup for things like DNS (such as pihole + unbound correctly configured) and there can be issues with a reverse proxy setup of Jellyfin for some LG TVs.
Alternatively, if you're deadset on a native client, you could try the WebOS homebrew route (you don't even need to root the TV, just get dev mode in it) and install Kodi from the homebrew repositories, and use that to setup Jellyfin.
That said, I prefer it because native clients are often missing some features that are present on the web client, and you do benefit directly from the web development of Jellyfin; the tradeoff, however, is that performance is going to be more dependent on network stuff instead of the hardware side of things. It can be rather slow even if you have an efficient setup for things like DNS (such as pihole + unbound correctly configured) and there can be issues with a reverse proxy setup of Jellyfin for some LG TVs.
Alternatively, if you're deadset on a native client, you could try the WebOS homebrew route (you don't even need to root the TV, just get dev mode in it) and install Kodi from the homebrew repositories, and use that to setup Jellyfin.
Server specs => OS: Debian 12 | GPU: Arc A380 | CPU: Ryzen 5 5600X | 64GB RAM | 56TB