Frequently Asked Questions

It depends on the apps you run. The website needs a favicon and logos, the mobile apps need app icons, notification icons and splash screens, and each TV platform has its own icon or tile. Vodlix lists every slot per app and marks the ones required before that app can be published.

Each upload slot shows its dimensions, format and maximum file size, for example 192×192 PNG up to 25KB for the favicon and 1024×1024 PNG for the iOS app icon. Store specific slots link to the store guidelines, and the iOS icon slot offers a template.

Yes. Every app has a live preview of its device, such as an iPhone or Android home screen, an Apple TV home row or the Roku home screen, with home and splash views and, on mobile, light and dark mode.

No. The brand kit holds your shared logo, colours and default splash, and every app reuses it until you override an asset for that app. Copy from app starts one app from another app's set.

The website and PWA, the iOS and Android apps, and the Android TV, Fire TV, Apple TV, Roku, Samsung Tizen and LG webOS apps, each with its own page of assets.

Each app shows a readiness percentage and a Before you can publish panel naming the required assets that are still missing. When they are all in place it changes to Ready to publish and shows how many optional assets are still empty.

Yes. You set the minimum time it stays on screen, from 500 to 15,000 milliseconds, whether the centre logo shows, whether an animation plays over the background, bottom text with its colour and size, and native bottom branding on Android 12 and later. Apple TV and Android TV can also play an MP4 splash video of up to 10 MB.

White label is the proposition that the service is yours rather than ours. Branding assets is the practical work of it: the specific files that have to exist, at the right sizes, for that to be true on every screen a viewer might see.

Tickets raised inside a Vodlix service arrive attached to the subscriber's account, with device, plan and history already visible, so your team skips the identity questions and addresses the actual problem first.

A Vodlix support ticket includes the account, the device and app in use, the subscription status and the relevant viewing history the platform already holds, without the subscriber having to explain it.

The whole conversation lives in one place inside Vodlix, tied to the subscriber's account, so nothing is scattered across inboxes and the full history is at hand when they write in again.

Problems are solved faster without wasted replies, at exactly the moment a frustrated subscriber is deciding how they feel about your service, which makes support a retention tool.

Vodlix brings support inside the product where the platform can see the account, which removes most identity questions. You can still run email support alongside it if you choose.

Billing questions, playback on one particular device, and sign in problems. All three have factual answers already recorded in the platform, which is why keeping support close to those records shortens them so much.

The session and order records show what reached the platform and what was charged, which is usually the difference between a fault and a misunderstanding. Signing in as the viewer to reproduce something is available separately for the cases that need it.

When you have a rota, service level commitments or multiple channels to manage. Deciding that before you commit is worth the thought, because moving support tooling later is more disruptive than choosing correctly at the outset.

Vodlix conditional access (CAS) is a system where each title carries rules on who can watch, in which countries, at what age rating and between which dates, and every play request is checked against them before a stream is issued.

A hidden or greyed out button still leaves the stream reachable to anyone who inspects the network. Vodlix conditional access checks entitlement at the moment of play, so content is actually locked, not just visually locked.

Vodlix access rules live on the content and the account and are enforced server side when a stream is requested, so they hold on the website, in every app version and on any device.

Yes. Because Vodlix enforces access on the server rather than in the client, the same rules hold even in apps shipped long ago, and a rule cannot be bypassed by using an old app.