All bases
MediaPubflow

Video streaming

A customer watches with household profiles. Those profiles are not extra logins. An administrator publishes titles.

These are example architectures. They are not affiliated with any company or trademark.

Try the flow here. It is a local sketch of the base, not a live account.

Who's watching

POST/api/v1/profiles/switch

200 · profile switch is ready for this household.

Try as

Functions

Lists the household profiles on this customer. A locked profile asks for a PIN. The profile is not a new user.

Apps

A full pack is not available to clone.

  • backend

    Catalog and playback API

    Checks the Flowless session, the maturity gate, and how many screens are playing.

    Default node-backend

    Can swap node-backend, go-backend, python-backend, rust-backend, elixir-backend

  • web

    Web and TV portal

    Profile faces, the home row, and the player.

    Default nextjs

    Can swap nextjs, react

  • mobile

    Mobile player

    The same catalog and player on a phone.

    Default react-native

    Can swap react-native

Who signs in

  • Customer

    customer

    Pays for the household and picks who is watching. Profiles hang off this account.

  • Administrator

    admin

    Publishes titles into the catalog. Signs in with a second factor.

Policies

  • Profiles stay on the customer

    A household profile is not a new login. It hangs off the customer who pays.

  • Kids stay inside the rank

    A kids profile cannot open a title above its maturity rank.

  • One household, limited screens

    A second screen in the same household can be refused.

  • Only the administrator publishes

    Putting a title on the home row is the administrator account.

API

  • Choose who is watching

    Lists the household profiles on this customer. A locked profile asks for a PIN. The profile is not a new user.

    POST /api/v1/profiles/switch

    requireAuth · Hosted by Catalog and playback API

    Customer

  • Show the home row

    The chosen profile sees a feature and what they already started.

    GET /api/v1/catalog/home

    requireAuth · Hosted by Catalog and playback API

    Customer

  • Start playback

    Opens one stream. A second screen in the same household can be refused.

    POST /api/v1/playback/sessions

    requireAuth · Hosted by Catalog and playback API

    Customer

  • Publish a title

    The administrator puts the next title on the home row.

    POST /api/v1/studio/titles

    requireUserType · Hosted by Catalog and playback API

    Administrator

What you see

  • Who's watching

    • Up to a few profile faces
    • A kids mark
    • A PIN when the profile is locked

    POST /api/v1/profiles/switch

  • Home

    • A feature with its maturity mark
    • Play
    • A continue row with progress

    GET /api/v1/catalog/home

  • Player

    • The title
    • Play and pause
    • A warning when the household stream limit is hit

    POST /api/v1/playback/sessions

  • Studio

    • The title to publish
    • A publish action for the administrator
    • A refusal for the customer

    POST /api/v1/studio/titles

What is stored