Apple Developer & Google Play setup: a clean checklist for brands

Every Appolar launch starts with the same boring conversation: do you have Apple Developer and Google Play accounts ready? Half of brands say yes and are right. A quarter say yes and discover later that the account is a personal one, in the founder's name, not the company. A quarter say no and need to start the enrollment, adding days to the timeline. This piece is for all three cohorts; even if you "have" the accounts, the checklist is worth reading.

Why organization accounts, not personal

For any brand that intends to be a real business, both Apple Developer and Google Play accounts should be Organization accounts, not personal Individual accounts. The difference matters more than it sounds. An Organization account allows multiple team members to manage builds, listings, and certificates. It also displays your company name as the app publisher, not the founder's name.

Migrating from Individual to Organization later is possible but painful — it involves transferring apps, certificates, and signing keys, and usually adds friction to release workflows for weeks. Doing it right the first time saves you the migration tax. The cost is the same; the setup work is similar.

Apple Developer enrollment

Apple's enrollment process for an Organization account requires three pieces of information: a D-U-N-S number, a legal entity name that matches your business registration, and a senior team member as the contact. The D-U-N-S number is free and takes 1–5 business days to issue via Dun & Bradstreet. Most brands have one already; check before applying for a new one.

The legal entity name has to match your business documents exactly. "Acme Co" on your Apple application and "Acme Company, Inc." on your articles of incorporation will trigger a verification call. Match them character for character — capitalization included.

The $99 annual fee is paid at the end of the enrollment flow. Renewal is automatic from a credit card; the most common preventable account suspension is a renewal failure because the card on file expired. Set a calendar reminder for the renewal date and audit the card every 11 months.

Google Play Console enrollment

Google Play Console enrollment is faster and cheaper — $25 one-time fee, paid at the end of the flow. The account creation itself is immediate; you have a Play Console in minutes. What is not immediate is the payments profile, which lets you publish paid apps or apps with in-app purchases.

For most Shopify brands, in-app purchases are not used (Shopify Checkout handles payments via web), but the payments profile is still required for some app types and most certainly required if you ever plan to add in-app subscriptions or promo content. Setting it up takes 1–3 days and requires a business tax ID. Do it during initial enrollment, not later.

The Google Play Console also has a "verified developer" requirement that involves submitting business documents and waiting for review. As of 2024–2025, this verification is mandatory for any new account distributing apps to consumer audiences. Plan for an extra day of review time on the first app you upload.

Access and roles

Once both accounts are active, add the right team members with the right roles. The platform vendor (us, in the Appolar case) needs upload and build access but not full account ownership. The brand should keep account ownership in-house, on the founder or operations lead's email.

On Apple, the relevant roles are App Manager (can submit) and Developer (can build). On Google Play, the relevant role is Admin scoped to the specific app, not the whole console. Avoid giving the platform vendor full Admin rights to the entire developer account; it is a security risk and unnecessary.

“The fastest app launch we ever ran had the developer accounts active before the contract was even signed. That brand cut three weeks off the timeline by starting day-zero work on day-negative-fourteen.”— Appolar launch notes

Certificates and signing keys: your ownership

Apple uses certificates and provisioning profiles to sign the apps you submit. Google uses a single upload key plus the Play App Signing service. Both are tied to your account and effectively non-transferable. If you ever switch platform vendors, the new vendor needs access to these signing materials to ship updates that App Store and Play Store recognize as continuing your existing app.

Lose the signing keys and you lose the ability to update the app. Apple has recovery paths but they are slow and involve customer support. Google's Play App Signing service holds the canonical key for you, which is one reason it is the recommended default. Either way, document the recovery paths the day the accounts are set up; you will not want to be discovering them in a release crisis a year later.

Common failure modes

Failure 1: name mismatch. The legal entity name on Apple does not match D-U-N-S exactly. Apple flags the application for verification. 1–3 day delay.

Failure 2: missing tax info on Google. The Play Console exists but the payments profile is not complete. The app uploads fine but cannot go live. 1–2 day delay.

Failure 3: wrong account holder. The Apple account is in a contractor or former employee's name. Transferring ownership takes weeks. Plan for the senior in-house owner from day one.

Failure 4: expired payment method. Apple's $99/yr renewal fails because the card on file expired. Account goes into a grace period, but if it lapses, app updates stop. Audit annually.

None of these failures are exotic. All of them are preventable. The brands that ship apps fast are the brands that resolve these upfront, before the platform vendor is in the room. The brands that miss launch windows are the ones who treated the developer accounts as someone else's problem.