6. Creating Your App IDs (a.k.a. The Identifier Nonsense)
Alright, you've paid the tolls, you've got your shiny developer accounts - now comes the next delightful step: actually creating the app in the stores.
And here's where Apple and Google show their true personalities. Apple, once again, makes you jump through flaming hoops blindfolded. Google, bless its corporate soul, just hands you a checklist and pats you on the back.
Apple: Bundle ID, AKA "Why Is This So Complicated?"
So here's the deal: you can't just create an app in Apple's system. No, no. First, you need an App ID (Identifier).
👉 https://developer.apple.com/account/resources/identifiers/list
Easiest way to get here is by clicking "Create a new app" on App Store Connect, which will then tell you: "Hey, you need a Bundle ID."
This is where the madness begins.
You need to register a new Bundle ID.
You need to tick every box for the capabilities your app will use (push notifications, payments, NFC, etc).
You need to pick a name that looks like a URL but isn't actually a URL. Example: for CutCompass we used
io.cutcompass.
Why? Because Apple. Don't ask.
Once you've finally registered it, congrats! You can now… go back to where you started and finish creating your app.
Bob's your auntie Patt.
Google: "Just Fill In the Form, Mate"
Google, by comparison, feels like being babysat by a friendly robot.
👉 https://play.google.com/console
Click Create App. Fill in the name, language, and some declarations at the bottom. Boom. App created.
No Bundle IDs. No capabilities screen. No double-backs. You've technically got a slot ready to accept builds within five minutes.
See, Apple? It's not that hard.
Store Listings: The Marketing Bit (That Actually Matters)
Once the app shells exist in both platforms, you now need to fill in what I call the marketing tax.
This means:
App description
Screenshots
Preview videos
Keywords
Promotional text
Privacy policy URLs
Apple forces you to fill in absolutely everything before you can even think about launching. Google at least lets you skip some stuff and come back later.
But here's the real talk: this is the part users will actually see. So put effort in. Don't just treat it as a formality - your app store listing is your landing page for millions of people.
Rant Break: Why Can't They Just Agree on Anything?
I have to say it: why are these systems so different?
Apple makes you go off on side quests for every tiny thing, then come back three tabs later to finish the process. Google hands you a checklist.
They could have agreed on a single standard. They could have made it easier. But no, each one insists on reinventing the wheel in their own special way. And you, dear founder, get to deal with the fallout.
Survival Tips
For Apple, plan your capabilities in advance. Know what services you'll need (push notifications, Apple Pay, NFC, etc). Saves you a second round of headaches later.
For Google, don't half-arse your privacy policy. They're stricter than they used to be.
Don't rush your screenshots. Good ones make the difference between "ignored" and "downloaded."
Coming Up Next
Now that our apps exist in both stores, it's time to fill out the really boring but super important stuff: app information, privacy declarations, and the joy of age ratings.
Oh, and monetisation - the part where Apple and Google hold you hostage if you don't use their payment systems.
That's next. Grab more coffee.