Web App Distribution

The Web platform builds your app as a single-page web application and hosts it on a Vidori-managed URL. You can optionally point your own custom domain at it via DNS.

Before starting, make sure you’ve completed the shared Prerequisites in App Configuration.

1. Upload Web Branding Assets

In the admin panel, go to App Studio → Distribution → Web and upload the following images:

Image	Size	Description
Web App Logo	540 x 100 px	Header logo shown in the web player
Favicon	512 x 512 px	Browser tab icon (PNG, square)

2. Note Your Hosted URL

The Hosted URL field shows the Vidori-managed URL where your web app will be served after the first build. It’s read-only and assigned automatically — you cannot change it.

This URL is what end users will visit if you don’t set up a custom domain.

3. Build and Deploy

1. In App Studio → Distribution → Web, click Build

2. The build typically takes 5–10 minutes. The status updates automatically on the page

3. When the build completes, the app is deployed to the Hosted URL above

Unlike iOS, Android, and Roku, there is no app store review for web — once the build succeeds, your app is live immediately at the Hosted URL.

4. (Optional) Set Up a Custom Domain

If you want users to reach your app at your own domain (e.g. watch.yourcompany.com) instead of the Vidori-hosted URL, configure DNS at your domain registrar.

1. In App Studio → Distribution → Web, locate the DNS Records section. It lists the CNAME record(s) you need to create

2. In your domain registrar (Cloudflare, Namecheap, GoDaddy, Route 53, etc.), open the DNS settings for the domain you want to use

3. Create a CNAME record matching the Name, Type, and Value shown in the admin panel

4. Save the DNS change. Propagation typically completes within 5–60 minutes (occasionally longer for some registrars)

Tip

Once DNS resolves, your custom domain serves the same app as the Hosted URL. SSL certificates are provisioned automatically — you do not need to upload or configure one.

Troubleshooting

Custom domain shows a certificate warning

DNS propagation may still be in progress, or the CNAME record may be incorrect. Verify with dig <your-domain> CNAME (or any online DNS lookup tool) that it points to the Value shown in the DNS Records table. Allow up to an hour after the CNAME starts resolving for the SSL certificate to provision.

Build succeeds but the Hosted URL shows an old version

Browsers and CDN caches may briefly serve the previous build. Hard-refresh (Cmd/Ctrl + Shift + R) or open the URL in a private window to bypass the cache.