Publishing Your App to the Stores

Once your branded app is built and approved, the final step is getting it into the stores so your users can download it. OTTBuilder prepares the builds and guides you through publishing, but the app is published under your developer accounts so you own the listings. This article explains the process and how to avoid common rejections.

Accounts you need

Publishing requires developer accounts with each platform you target. Set these up early, as approval can take time.

Apple — an Apple Developer Program account for iOS and Apple TV.
Google — a Google Play developer account for Android phones, tablets, and TV.
TV manufacturers — programs such as the one for Samsung TV and other Smart TV ecosystems you choose.

The apps publish under your accounts, so your company name appears as the developer. OTTBuilder supplies the builds and the listing assets; you (or we, with access you grant) submit them.

What we prepare

For each platform, we deliver:

The signed build in the correct package format.
Store assets generated from your branding: icon, screenshots, and graphics.
The technical metadata the store requires.

What you prepare

You provide the listing details that describe your business:

The store listing text: description, keywords, and category.
A privacy policy URL (required by most stores).
Support contact details.
Any age rating information the store requests.

Submission steps

A typical submission looks like this:

Create or confirm your developer account.
Grant OTTBuilder access, or receive the build from us to upload yourself.
Add listing text, screenshots, and the privacy policy.
Submit for review.
Respond to any reviewer questions, then release.

Set up your developer accounts during the build phase, not after. Account approval and identity verification are frequently the slowest part of getting an app live.

Avoiding common rejections

Stores review streaming apps carefully. Reduce the risk of rejection by ensuring:

The app does not imply it provides channels or content; it is a player for your own service.
A working test account is available for reviewers so they can sign in and see the app function.
Your privacy policy is reachable and accurate.
The app name and assets do not infringe on trademarks.

If reviewers cannot log in and reach playable content, they will reject the app. Always provide valid, non-expiring review credentials and confirm your backend is reachable during the review window.

After publishing

Once live, we continue to maintain the app and provide updated builds for new releases and platform requirements. When an update is ready, the same submission process applies. See Managing Your Account & Billing for how ongoing maintenance is handled, or review platform options on /pricing.

Ready to publish? Make sure your developer accounts exist, then reach out via /contact and we will coordinate submission.