Dev.to WebDev 🛠 Dev 👁 0 📖 3 min read

Modeling per-OS app store availability: why "Samsung" and "Tizen" are two different claims in our data

We run Best IPTV Player, a catalog that tells people which IPTV player apps their device can run (players only; no channels, no subscriptions). On 19 November 2026 we rebuilt our Samsung Smart TV page, and the data work

We run Best IPTV Player, a catalog that tells people which IPTV player apps their device can run (players only; no channels, no subscriptions). On 19 November 2026 we rebuilt our Samsung Smart TV page, and the data work behind it raised a modeling question worth writing up: how do you store "this app is available on Samsung TVs" when publishers phrase it in at least three different ways?

The problem: brand, OS and store are not the same field

A Samsung TV is a brand (Samsung), an operating system (Tizen, or Orsay on older models), and a distribution channel (Samsung Apps TV inside Smart Hub). LG has the same three layers: LG, webOS (or Netcast on older sets), and the LG app store. Publishers rarely name all three. In the copy we checked:

  • HotPlayer's FAQ says Samsung (Tizen), LG (webOS) ... your TV's app store. That's brand + OS + channel.
  • SmartOne IPTV says Samsung TVs (Orsay and Tizen). Brand + two OS generations, no store wording.
  • IBO Player's site has a platform strip with Samsung and LG Web OS. Brand only for Samsung, brand + OS for LG.

If you collapse all of that into samsung: true, you lose detail that users care about. For example, a Samsung owner with a 2014 Orsay set and one with a 2024 Tizen set are not asking the same question.

A claim-level schema

Instead of one boolean per device, we store claims, one per publisher statement:

type Status = "verified_yes" | "unknown";      // no "verified_no" unless the publisher says so

interface PlatformClaim {
  player: string;            // "smartone"
  device: string;            // "samsung-tv"
  brandNamed: boolean;       // the text says "Samsung"
  osNamed: string[];         // ["tizen", "orsay"]; empty if not written
  channelNamed?: string;     // "tv-app-store" | "apk" | ...
  quote: string;             // the exact words we relied on
  sourceUrl: string;
  checkedOn: string;         // "2026-11-19"
  status: Status;
}

Display rules come from the claims and are never typed in by hand:

  • Verified if brandNamed || osNamed.includes(deviceOs). The page then prints the quote and shows whether the OS word was actually present ("Tizen: not written" for IBO Player).
  • Unknown if no claim exists. Unknown is a first-class value. It never renders as "No", and it never counts toward a "supported" total.

Store channel is per OS, not per player

The second lesson: install instructions belong to the OS, not the app. Samsung's own support page states "Only apps available in the App store can be installed on the Smart TV", and Samsung's developer docs say TV apps are released on Samsung Apps TV after review, per model group. So the Samsung install path (Home > Apps > Search > Install) is one shared record. A player-level apk channel that a publisher lists for Android (HotPlayer lists a Downloader code for Android devices) must never leak onto a Tizen page. We enforce this with a simple check: if device.os is tizen or webos, then any channel of type apk or downloader fails the build.

Re-verification as a diff

Each round we fetch the publisher pages again (curl first, plain-text extraction, then grep -i 'samsung\|tizen') and compare the new quotes with the stored ones. On 19 November SmartOne's home page contained "Samsung TVs (Orsay and Tizen)", which our 9 November extract had missed, so SmartOne moved from Unknown to Verified. Some sites ship an empty HTML shell and render the platform list in JavaScript (IBO Player does). For those we search the built JS bundle for the string literal (alt:"Samsung") instead of giving up.

Avoiding near-duplicate device pages

Search Console had flagged our Samsung and LG pages as duplicates. The template was the same and only the brand name changed. Claim-level data fixed that on its own: the Samsung page now has its own players, quotes, install path and FAQ, and the shared text dropped to about 11% of 5-word shingles.

If you build any compatibility matrix (browsers, TVs, cars), model publisher statements as quoted, dated claims rather than booleans. Your "Unknown" column will be honest, and your pages will differ because the facts differ.

Data and sources: bestiptvplayer.tv/devices/samsung-tv/. Try the device-based player selector.

📰 Read the original article on Dev.to WebDev

Originally published by Dev.to WebDev. Aggregated on AIWithGhost for educational purposes — full credit and traffic to the original publisher.