Skip to content

FAQ

Jump to bottom
Ferris edited this page Jun 24, 2026 · 5 revisions

Frequently Asked Questions (FAQ)

Welcome to the OcenFin FAQ! Here you will find answers to the most common questions regarding the background, development, and technical choices of this project.

The most important question: Is this project AI-generated?

Yes, to a very large extent by Claude.

I have foundational knowledge in HTML, CSS, and some PHP/JavaScript. Choosing Svelte and Tailwind was a conscious decision on my part, and AI—when used correctly—is a great tool to support me in this endeavor. I intend to keep the project alive and maintain important dependencies for as long as I use my WebOS TV (which should be for a long time).

Why Svelte and Tailwind instead of other existing frameworks?

I could have used something else, but I didn't want to. My goal was to create the smallest possible app with a strict focus on TV performance.

With Svelte, there is no heavy runtime framework shipped to the TV. During the build process, Svelte compiles the code into pure JavaScript, which makes the app not only incredibly lightweight but also extremely fast.

Why is the versioning just a date?

Right now, traditional versioning (like v1.0, v2.0) wouldn't make much sense for me. I am constantly implementing new features or trying to improve existing ones under the hood.

I don't want to rush to version 10.0 in a short time and set false expectations. With the current YYYYMMDD format, you can immediately tell when a release was built and easily see if you are on the latest version.

What is the difference between the Legacy and Modern versions?

It's actually quite simple. The source code you see on GitHub is exactly the same for both. The Svelte base is identical. The difference happens during the build process:

  • Legacy: I specify an older Chromium target version. The compiler then translates the code into older JavaScript syntax that older WebOS TVs can understand.
  • Modern: This version has no specific target restrictions and uses the latest, most optimized JavaScript available.

Why don't you add features that other WebOS Jellyfin apps already have?

If I did that, I would basically just be building a clone of an existing app, which is not my goal.

I try to design OcenFin exactly the way I need it for my own daily use. My goal was never to offer hundreds of toggles and options, but to focus on the core experience. The features that are there should just work intuitively, without the user having to dig through 10 settings first.

Clone this wiki locally