Vixeo

Connecting to a server

On first launch the app asks for a server URL. Any scheme Jellyfin accepts works, including a reverse-proxied subdomain. The client stores the resolved base URL and an access token; the password is never written to disk.

Library browsing

Libraries are read from the server's own view definitions, so whatever you configured in Jellyfin is what appears. Sorting and filtering happen client-side against a cached index, which is why the grid stays responsive while a slow server is still answering.

Playback

Direct play is attempted first. If the container or codec is not supported on the device, the client asks the server to transcode and reports which of the two it ended up doing in the player's detail sheet.

Player → long-press the quality chip
  Direct play   H.264 / AAC   no server load
  Transcoding   HEVC → H.264  server is re-encoding

Offline behaviour

The last-seen library index, artwork and watch positions are cached. With no connection the app opens to that cache in a read-only state rather than to an error screen.