Developers Account Guide: Apple, Google, Roku Setup for OTT

Here is the scenario: The app is ready. The transcoding pipeline is stable. The marketing team has the press release queued for Tuesday. Then, on Monday morning, you realize you can’t upload the build because the developers account is still pending identity verification.

I have seen this happen more times than I care to count.

The reason most OTT launches slip is rarely the code—it is the infrastructure and the access rights. When you are building a streaming service, the "developers account" isn't just a login. It is the legal and technical root of your entire distribution network.

If you don't own it, you don't own your audience.

This guide covers exactly what you need to know to set up, secure, and manage developer accounts for a multi-device OTT rollout.

What is a Developers Account?

In the context of OTT and streaming, a developers account is the gateway between your backend (like Vodlix) and the end-user's device. It is the subscription you pay to Apple, Google, Roku, or Samsung to allow you to publish apps, manage in-app purchases (IAP), and access analytics.

Technically, it provides three critical things:

1. Code Signing Certificates: You cannot install an app on a non-debug device without a certificate issued by the platform holder.
2. API Access: For things like push notifications (APNs, FCM) and DRM licensing.
3. Merchant Capabilities: The ability to process credit cards through the store's billing system.

The "Organization" vs. "Individual" Trap

Here is the first mistake founders make: signing up as an "Individual."

Do not do this.

If you sign up as an individual, the developer name on the App Store will be "John Smith" instead of "StreamFlix Inc." changing this later is a nightmare of support tickets and migration scripts. Always register as an Organization. This requires a D-U-N-S number (more on that below), but it is non-negotiable for a professional OTT service.

Why Developers Account Ownership Matters

I often see non-technical founders ask agencies to "just handle it." The agency creates the account, publishes the app, and holds the keys.

This is a critical infrastructure risk.

If you ever switch vendors or if that agency goes out of business, you lose the ability to push updates. You cannot rotate your signing keys. You cannot access your subscriber data.

Rule #1: You must own the root account. You grant the dev team (or platform provider like Vodlix) access via "User Permissions," but you never hand over the root login.

How to Implement Developers Accounts (The Big Three)

Setting these up takes time. Apple can take 2-4 weeks for organization verification. Google is getting stricter with identity checks. Start this process the day you sign your contract for the OTT platform.

1. Apple Developer Program

This is the strictest process. You need a D-U-N-S number from Dun & Bradstreet. If your business is new, this number might not be synced with Apple's database yet.

• Cost: $99/year.
• Requirement: Legal Entity Status (LLC, Inc, Ltd).
• The Gotcha: Two-Factor Authentication (2FA) is mandatory for the account holder. Do not use a burner phone number.

For a deep dive on the specific steps for Apple, check out my guide on How to Setup an Apple Developer Account for OTT Apps.

2. Google Play Console

Google used to be instant. Now, they require valid government ID and sometimes proof of address. For new personal accounts, they even require 20 testers for 14 days before production access. Fortunately, Organization accounts usually skip the 20-tester rule but face stricter business verification.

• Cost: $25 one-time fee.
• Requirement: D-U-N-S number (recently added as a requirement for orgs).
• The Gotcha: If Google links your account to a previously banned account (via IP, credit card, or recovery email), they will ban you too. Use a clean browser and a corporate credit card.

For more on navigating Google's requirements, see Google Play Developer Account setup.

3. Roku & Amazon Fire TV

These are often easier but have their own quirks.

• Roku: Free to join. You need to set up a "Developer" account, not just a user account. They pay out via PayPal or Wire, but tax forms must be perfect.
• Amazon: Free. The "Amazon Appstore" is what runs on Fire TV. It is separate from AWS, though you can link them.

Best Practices for Managing Access

Once you have the accounts, you need to manage them. Do not share the password in a Slack channel.

Use Role-Based Access Control (RBAC)

Every platform allows you to invite users with specific roles.

• Admin: Can do everything except delete the account. Give this to your CTO.
• Developer: Can upload builds and view crashes. Give this to your engineering team.
• Finance: Can view payments and tax forms. Give this to your CFO.
• Marketing: Can edit store descriptions and screenshots.

Service Accounts for CI/CD

If you are automating your pipeline (and you should be), you don't want your CI server logging in as a human.

• Google: Use a Service Account (JSON key file) linked to the Google Play API.
• Apple: Use an App Store Connect API Key. This bypasses 2FA for automated uploads via tools like Fastlane.

Centralize Your Keys

When you generate upload keystores (Android) or distribution certificates (iOS), store them in a secure vault (like 1Password or HashiCorp Vault). If you lose the Android upload key, you have to contact Google support to reset it, which takes days. If you lose the keystore password, you are stuck.

Common Challenges and Solutions

Here are the actual support tickets I deal with every month.

Challenge 1: The "Entity Name Mismatch"

Problem: Your legal entity is "Stream Co. LLC" but your D-U-N-S record says "Stream Company Limited Liability Company." Apple will reject this.
Solution: You must contact D&B to update the record to match your legal documents exactly, or wait for Apple to sync. This can take 7 business days.

Challenge 2: The 2FA Bottleneck

Problem: The root account is tied to the CEO's phone number. The CEO is on vacation. The team cannot login to accept the new license agreement.
Solution: Set the root account phone number to a virtual corporate line or a dedicated device kept in the office (if you are physical). Better yet, ensure Admins have full access so the root account is rarely needed.

Challenge 3: Smart TV Verification (Samsung/LG)

Problem: Unlike Apple/Google, Samsung and LG often require a partnership request or a specific seller portal registration that isn't open to everyone automatically.
Solution: These are manual processes. You often need to submit a "Seller Office" application. Do this months in advance.

Integrating with Your OTT Platform

When you use a white-label solution like Vodlix, we need access to these accounts to publish on your behalf.

We typically ask for:

1. Apple: Invite us as an Admin or App Manager.
2. Google: Invite us with Release Manager permissions.
3. Service Keys: The API keys mentioned above for automated builds.

This setup allows us to push updates automatically whenever you change a configuration in the dashboard, without us needing your root password.

Summary Checklist

Before you write a single line of code or upload a single video:

1. Register your business and get a D-U-N-S number.
2. Create a dedicated email address (e.g., [email protected]) for these accounts.
3. Sign up for Apple (Organization) and Google (Organization).
4. Set up 2FA and save backup codes in a secure vault.
5. Invite your team and your OTT vendor (like Vodlix) as users.

If you get this right, your launch will be boring. And in engineering, boring is good.