Getting started
Getting Started: How Onboarding Works
A step-by-step overview of how OTTBuilder onboards your branded streaming player apps, from kickoff to published builds.
Welcome to OTTBuilder. We build and maintain fully branded, white-label streaming player applications for IPTV providers, resellers, and content operators. You bring your brand and your service backend; we deliver polished apps your customers download and use. This article walks you through what onboarding looks like from start to finish.
What OTTBuilder provides
OTTBuilder delivers the player application across the platforms you choose. We do not provide channels, playlists, EPG data, or subscriptions. Those come from your own service backend (for example, your Xtream Codes panel or hosted M3U/M3U8 playlists). Our job is to wrap your streaming experience in a stable, branded app and keep it updated.
The onboarding stages
Onboarding generally moves through five stages:
- Kickoff — You confirm which platforms you want (for example, Apple TV, Samsung TV, Android, iOS). See /pricing for current platform options.
- Brand intake — You submit your brand assets: app name, logo, color palette, app icon, and splash screen. The Brand Assets Checklist covers exactly what to prepare.
- Login configuration — You tell us which login method your app should use, such as Xtream Codes login or M3U / M3U8 playlists.
- Build & review — We assemble your branded build and share it for testing. You review playback, branding, and login behavior, then send feedback.
- Publishing — Once approved, we help you get the app into the relevant stores. See Publishing Your App to the Stores.
Timelines vary by platform and how quickly assets and store accounts are provided. The fastest projects are the ones where brand assets and store credentials are ready at kickoff.
What you need before you start
To keep things moving, gather these in advance:
- A finalized app name and brand colors.
- A high-resolution logo, app icon, and splash screen (see App Icon & Splash Screen Requirements).
- Working backend credentials so your login method can be tested against a live service.
- Store developer accounts if you plan to publish (for example, Apple Developer and the relevant TV manufacturer programs).
Your role versus our role
| You provide | OTTBuilder provides | | --- | --- | | Brand assets and app name | The branded player application | | Streaming backend and content | App build, packaging, and updates | | Store developer accounts | Publishing guidance and support | | End-user subscriptions | Ongoing maintenance |
Decide on your full platform lineup early. Adding platforms later is straightforward, but planning them up front keeps your branding consistent across every device.
Next steps
When you are ready, head to /get-started to begin intake, or reach out through /contact if you want to talk through platforms first. Once your assets are in, you are usually only a few review cycles away from a publishable, fully branded app.
Still need help? Open a ticket in the client portal.
Open a ticket