Where Tuneline Fits: Media Players vs Content Services

"Streaming app" gets used as if it's one category. It isn't. There are two genuinely different kinds of software underneath that label, and they work nothing alike.

Content services

Netflix, Spotify, and a cable box are content services. The defining trait is that the service assembles a catalog — it licenses titles, decides what's in the library, and sells access to that specific library. Cancel the subscription and the catalog goes with it, because what you were paying for was access to their content, not a piece of software. The app is a storefront and a player bundled together, but the thing being sold is what's inside.

Media players

VLC, Kodi, Infuse, Plex's client app, and Tuneline are media players. A media player ships with no catalog at all. It's a tool that plays back whatever file or stream it's pointed at — a local video file, a network share, a URL you typed in. The player has no opinion about what that content is and no license to sell it, because it isn't selling content. It's selling (or giving away) the software that plays it.

You can tell the categories apart with one question: if you deleted the app's entire back end tomorrow, would there be anything left to watch? For a content service, no — the app is just a window onto a library that lives on the service's servers. For a media player, the question doesn't even apply, because the player never had a library. It plays what you give it, and what you give it keeps existing independently of the player.

Where Tuneline sits

Tuneline ships with zero content and has no catalog to lose. Every source that plays inside it was added by the person using it, from wherever they already had it. Delete Tuneline's back end entirely and playback for existing sources doesn't change, because playback was never routed through it. (The mechanics.) That puts Tuneline in the media-player column, with VLC and Kodi, not the content service column with Netflix or cable — and it's reflected in how the app describes its own category to app stores and structured data: a MultimediaApplication, not a video-on-demand or broadcast service.

Why the category matters more than it sounds like it should

The two categories carry entirely different obligations. A content service is responsible for what's in its catalog because it built the catalog. A media player is responsible for playing correctly and handling your data properly — not for the contents of a URL someone else operates, because the player never assembled, licensed, or chose what's at that URL.

Conflating the two categories because both can technically end up showing video on a screen misses the part that actually determines who's accountable for what: whether the software built a catalog, or whether it just rendered whatever it was handed.

Related reading

• What Tuneline Actually Is (And Isn't)
• Bring-Your-Own-Playlist vs Bundled Apps
• A closer, feature-by-feature comparison

---

— Shamir