Frequently Asked Questions

They do, and that is the whole point of enforcing at the stream. An app cannot decide for itself that somebody is entitled, because it is never asked. It requests a stream and the platform either issues one or does not, which is why an old app version cannot become a way around your rules.

Vodlix supports Google Chromecast and Apple AirPlay, so viewers can send playback from the Vodlix mobile app or web player to a television with a single tap.

Casting lets viewers browse and choose on the phone in their hand, where typing is easy, then watch on the big screen. It avoids remote control typing and matches how many households already behave.

The viewer browses, searches and picks a title on their phone or laptop, then casts playback to the television, leaving the phone free while the title plays on the big screen.

Yes, pause, seek and volume all work from the phone, which is a considerably better remote control than the one that came with most televisions. Being able to scrub with a thumb rather than a directional pad is the clearest example.

It follows them, because the position belongs to the account rather than to the device or the method. Somebody who cast last night and opens the television app tonight finds the same place waiting.

That is one of its main benefits. Casting reaches televisions and streaming sticks you have not built for, which widens your addressable audience without another build or another store review.

Yes. Set a content list's type to Top 10 and the row shows its titles with large rank numbers. It can be curated by hand or filled dynamically from a category or tag, like any other list.

Not with the built in search. It reads your live catalogue, so a title is findable as soon as it is published and unpublished titles never appear. If you connect Algolia, Typesense or Elasticsearch instead, new titles appear once that service has indexed them.

Yes. Each in progress title in the Vodlix Continue Watching rail shows a progress bar, and its More Info panel shows the time remaining beside the Resume button, so the viewer knows what finishing it will take.

Yes. Playback position on Vodlix belongs to the viewer's profile rather than the device, so the Continue Watching rail is identical on a phone, television or the web.

Positions belong to the viewer rather than being pooled across a household, which is the reason profiles exist at all. A family sharing one subscription should not be sharing one place in a series.

Yes. A scheduled Vodlix release goes live on the website, mobile apps and TV apps at the same instant, so no platform receives the title early or late.

No. Vodlix scheduled release removes manual publishing entirely, so nothing goes live before its set time and no one has to watch the clock.

Reversibility removes the risk that makes redesigns get deferred for years. With Vodlix custom templates, refreshing the look becomes an ordinary decision rather than a quarterly project.

Templates govern the web front end, while the apps have their own presentation with the branding shared between them. What travels across all of them is the brand layer rather than the layout, since a television and a browser cannot use the same structure anyway.

Yes. Vodlix player controls are tuned per device, including a scrubber that behaves properly under a directional pad and visible focus for every control on television.

Yes. Casting from the mobile apps to a connected television is built into the player, so a viewer who starts on a phone can move it to the big screen without leaving the app.

The same player and the same catalogue, arranged differently for each. The television build is designed around a remote rather than scaled up from the web, and the mobile build is built for one hand, because a single layout on all three ends up poor on all three.

Vodlix records every playback session against the account that opened it, including the device, the app and the IP address, all searchable by user, device or address from the admin area.