Viewer apps on web, mobile, and TV

Understand how web, mobile, and TV apps share the same catalog, accounts, and playback rules.

Mobile Handling Flow

Mobile apps use the same backend truth as the rest of the platform: profile context, home rows, content detail, playback, downloads, watchlist, comments, notifications, and progress sync.

Mobile handling

Mobile stays connected to catalog, access, and operations.

OfflinePlay or castMobile app opensiOS or Android sessionAuth and profileHousehold contextHome and feed APIRows, search, libraryContent detailEpisodes, list, commentsViewer actionPlay, download, cast?Offline packageDownload, local playbackSync backProgress, list, comments
Mobile is not a separate product silo
Downloads still respect platform rules
Engagement syncs with the shared service
Profiles and subscriptions stay consistent

Frontend

Use the web app for landing data, discovery pages, search, content detail, account flows, profile selection, subscription gates, and browser playback entry.

Mobile

Deliver home rows, search, library, offline downloads, casting, notifications, comments, support, profiles, device management, and a native player with tracks and quality controls in the mobile app.

TV

Optimize the TV app for remote navigation, TV login, profile management, large-screen discovery, search, subscription gates, and focused playback controls.

Playback

Playback respects account, profile, device, access, progress, language, subtitle, and reporting signals so every app honors entitlement and viewing continuity.

  1. 1Resolve viewer contextBefore playback starts, send account, profile, device, and title context from the app to the backend.
  2. 2Check access rulesLet the backend evaluate Free, SVOD, PPV, subscription, rental, or purchase access for the requested title.
  3. 3Return playback stateWhen access is allowed, receive a secure stream path from the API and save watch progress during viewing.
Talk to BitByte3 about implementation