# Apps Management for OTT Platforms | Builds and Versions | Vodlix

**Source:** https://vodlix.com/features/apps-management  
**Summary:** Configure, build and track apps for Android, Android TV, iOS, tvOS and Fire TV from one screen, with versioned builds and branding you change without a rebuild.  
**Publisher:** Vodlix

---

Manage apps quickly and securely with automated updates. Configure, build and distribute every platform from one place.

- **Feature Plan:** 2

- back-end
- core-platform
- mobile-app
- tv-app

## Five Platforms, One Place to Manage Them

Shipping apps is normally where a streaming service discovers it has become a software company. Vodlix keeps configuration, builds and versions for every platform in one screen, so adding a device is an operational step rather than a hiring decision.

### The Cost Nobody Quotes For

An app is not a one time build. Every platform moves underneath you, each store has its own review process, and a change to your branding means a new binary for each one. Do that across phones, televisions and streaming sticks and you have a release cycle that needs an engineering team whose only job is keeping five apps current.

That cost is invisible when a platform is being chosen and painfully visible eighteen months later. Vodlix removes it by making apps configuration rather than code: your branding and behaviour are settings, and the builds are produced from them.

#### Every platform, one screen

Android, Android TV, iOS, tvOS and Fire TV are configured side by side rather than in five separate places, so a change to your identity is made once.

#### Builds you can see

Each platform keeps a list of its builds with a version and a date, so you always know what is current, what shipped when, and what a tester is actually holding.

#### Branding without a rebuild

Icons, splash screens and assets are configured rather than compiled in, so refreshing your identity does not mean commissioning five new apps.

### Configuration, Builds and Versions

The screen separates the three things that usually get muddled. **Configurations** is where your app behaves the way you want it to. **Available builds** is the record of what has actually been produced, each with its version and the date it was cut. **Versions** is what your audience is running.

Keeping them apart matters when something goes wrong. A support question about a viewer on an old build is answerable, because the build list says what existed and when. A rollback is a known quantity rather than an archaeology exercise. And because every platform sits in the same view, nobody has to remember which console holds the Fire TV binary.

- mx-auto

### What This Buys a Small Team

It buys the ability to be on five platforms without five specialists. The [mobile apps](/features/mobile-apps) and the [TV apps](/features/tv-apps) read the same catalogue and the same subscriber accounts as your web storefront, so adding [Android TV](/features/android-tv-app), [Apple TV](/features/tvos-apply-tv-app) or [LG webOS](/features/lg-webos) adds reach rather than another codebase.

It also changes how quickly you can respond. A rebrand, a new splash screen or a behaviour change becomes a configuration update rather than a project with a release date attached, which is the difference between reacting to your market in a week and reacting to it next quarter.

**Q: Which platforms are managed here?**

Android, Android TV, iOS, tvOS and Fire TV, each configured in the same screen rather than in separate tools.

**Q: Can we see which builds exist?**

Yes. Each platform keeps a list of its builds with a version number and the date it was produced, so you know what is current and what a tester or a viewer is running.

**Q: Do we need developers to change our branding in the apps?**

No. Icons, splash screens and assets are configured rather than compiled in, so refreshing your identity does not require five new apps to be commissioned.

**Q: Who builds and publishes the apps?**

Vodlix does, from your configuration, and keeps them current as each platform changes. There is no mobile or television codebase for your team to own.

**Q: Does adding a platform mean maintaining another catalogue?**

No. Every app reads the same catalogue, content lists and subscriber accounts as the web, so a new platform adds audience rather than another system to keep in sync.

**Q: How do we handle an issue on an older build?**

The build list records what was produced and when, so a report from a viewer on an older version can be matched to a specific build rather than guessed at, which makes both support and rollback straightforward.