Clients

Overview

What Fliks runs on, what's shared across every client, and where to find the details for each one.

In short

Pick the client for your screen below: web, iOS, Android, Android TV, Apple TV, Samsung, LG, desktop, or cast to a Chromecast. All of them use the same account and keep your progress in sync.

Pick your client#

Same account everywhere: your library, progress and preferences follow you.

Client Where to get it Minimum version
Web Any browser, at your server's address Any current browser
Mobile (iOS, iPadOS) App Store iOS 16.6
Mobile (Android) Play Store Android 6 (API 23)
Android TV Play Store Android 6
Samsung TV (Tizen) Sideload (not yet on Samsung Apps) Tizen 5.5
LG TV (webOS) LG Content Store webOS 7.0
Desktop GitHub release download Windows, macOS (Apple Silicon only), Linux
Chromecast Built in, cast from any client above Any Chromecast device
Apple TV App Store tvOS 17

Sign in#

Open the app, enter your server's address and sign in with your account. On a TV, choose Quick Connect instead: the TV shows a code, and you type it on your phone under Login requests.

Open your avatar menu, then Login requests, and type the code the TV shows

More in Pairing and remote control.

What every client shares
  • The same account system: resume position, watch history, playlists, likes and requests all live on the server, not on any one device.
  • Pairing: sign a TV into an account without typing a password on the remote, by approving the request from a phone that's already signed in.
  • Remote control: send a title from one signed-in device to play on another.
  • Watch parties: watch together in sync with chat. Every client has it, with a few differences listed on that page.
  • Adaptive playback: each client tells the server what it can decode, and the server picks between sending the file as-is, repackaging it, or converting it, per Streaming and transcoding.
What TV clients cannot do

Android TV, Samsung (Tizen) and LG (webOS) share the same restrictions, because they're built for navigation with a remote control rather than a mouse or touchscreen:

  • No offline downloads: the feature and its settings are hidden entirely. See Offline downloads for which clients do support it.
  • No casting from the TV to a Chromecast: a TV can be a remote control target, but it doesn't act as a Chromecast sender itself.
  • No public profile pages and no server administration screens.
  • Navigation moves with the remote's arrow keys or D-pad instead of a pointer, moving between rows and cards the way a typical TV interface does.

Apple TV is a separate, native app rather than a build of the same interface (see Apple TV for exactly what it does and doesn't cover), but follows the same restrictions: no downloads, no casting out, no server administration.

Note

A beta Nintendo Switch client exists as a separate homebrew project, switchfliks. It is not covered here.

Edit this page on GitHub

Esc