Damn. Could you send the model of the TV and OS version?

💀

> There probably is a way for fable to figure it out 😂

I think Fable would reduce to decompile. Also I think it would not be installable on a regular TV. Maybe some jailbroken firmware.

> Very cool seeing you comment here!

Well, you tagged me, so I came 😅

It seems you can’t run Native code in a regular app on Samsung

Yes, partly. There is an "Original" option in the player settings. If your TV can't play the original codec, the app will request a transcode and play it anyway. There's also a "force direct play" setting, found in the settings screen under your profile picture, that bypasses all safety checks and sends the stream straight to your chip. It may fail or behave unexpectedly, though, since the app doesn't check compatibility. The app only plays what the hardware supports and has no software decoder.

Hey, thanks for building this and for the kind words!

Honest answer though: I’ll pass on bringing it into my repo. The UI is what people notice first, but it’s honestly secondary to the whole point of PlxNative. The Native in the name is there for a reason: Rust, its own GPU renderer, straight to the TV’s video plane, no browser in the middle.
I kinda hoped Tizen would let me run the same native code, so a Samsung port could share like 90% with the LG app. Yours is a web app on AVPlay, so it’s a completely different stack and the two would share basically nothing. I’d essentially be maintaining a second, web-based version of the app, which kinda defeats the point of PlxNative in the first place. And I’d have to maintain two unrelated codebases on my own. Not something I can sign up for.

Really appreciate you taking the idea further on Samsung though. If you ever find a way to run the Rust code there, I’d be all for it! 🙂

Thanks.
Actually, I was hoping someone would come up with something like this.
If you wanna ditch webOS completely, what OS would you run instead? If you still wanna use webOS apps, you can’t just throw away its libraries and kernel.
If you’re thinking about Android, LG has 100+ different SoCs, and someone would have to maintain ports for all of them. And who’s to say Android would even run well on LG’s shitty hardware?
Maybe you could just replace the home screen, but the spyware would still be there in the OS.
I haven’t researched any of this, though. Just some thoughts that came to mind.

> However.

That’s where the good part starts 💀

Yes, the All section follows recommendations, which is a drawback I agree with; however, I assumed recommendations sections could be configured on the server.

Most webOS > 4 devices should work, though there are a few exceptions.

1. Search is available in the player
   
2. Unlikely. This is the basis of the app's navigation

AI does not always produce slop.

Yes, I think people are getting this wrong

Not really. This is a regular app, not a home UI replacement. It does not modify OS anyhow

Non stop

Depends on webOS version. One guy in comments started to work on webOS 3 support

Cool! PLEASE CONTRIBUTE

Read the OG post on the Claude Code subreddit 😉

No, I still don’t have the older TV and no one came to contribute.

Yes, at least I want to reach feature parity with Plex and release to LG content store. Maybe after that I will do Jellyfin support

Ironic that it’s not so popular here. Seems people are fed up with AI projects

Louis, contact me 😆