Recently, our team went through App Store process, and I want to share what we've learned to help others navigate it more smoothly.
As an organization, building an app for the App Store can be quite a journey, especially with all the steps and waiting times.
Our organization, based in the USA, decided to enroll in the Apple Developer Program.
The process started with some preliminary steps, such as obtaining a D-U-N-S number, which is required for all organizations enrolling in the Apple Developer Program. This number uniquely identifies business entities and is essential for Apple’s verification process.
Initially, our D-U-N-S number was created, but when we tried to set up the Apple Developer account, we found that Apple’s D-U-N-S database hadn't been updated yet. This is a common thing many organizations face.
If the database hasn’t been updated with your D-U-N-S number, you may need to wait a bit before you can proceed. We tried again the next day and finally managed to create the organization developer account.
Even after the account was created, the process wasn’t over. Apple’s verification process can be quite thorough and includes confirming your organization’s legitimacy.
This meant waiting for further updates and occasionally nudging Apple for progress. For example, we had to email Apple because they mentioned a turnaround of two business days for updates, but it was taking longer.
Adding to the delay, there was a holiday in the US, so we could expect a response after that time at the earliest...
Eventually, we made a phone call for verification, which helped move things along. Shortly after that, we received an invitation email, signed the necessary documents, and completed the payment.
Apple then informed us that "Your purchase may take up to 48 hours to process," which meant we were still waiting a bit longer before everything was finalized. After 18 hours we had the credentials.
How Long Does It Take to Set Up an Apple Organization's Developer Account?
In total, from the initial attempt to set up the account to receiving the final invite, the process took about three weeks. This timeframe is something organizations should plan for when setting up their Apple Developer account—there are often delays due to the verification process, database updates, and holidays.
Once we received the credentials, we were ready to log in to App Store Connect. This is where all the magic happens—managing your app’s details, uploading builds, and eventually submitting it to the App Store.
How to Set Up the App
The first thing we did was create a new app. This part is straightforward, but it’s crucial to have all your information ready.
To set up the app properly, it's important to follow a structured roadmap. Here's how we approached it:
Register Your Bundle ID
Before we could create the app in App Store Connect, we had to have a bundle ID. We registered com.something.mobile in the Apple Developer Portal earlier.
This unique identifier is like a passport for your app; it needs to match exactly with what you have in your project configuration to avoid any issues later on.
Create a New App in App Store Connect
The first step was to create a new app. This part is straightforward, but having all your information ready is crucial.
We selected iOS as our platform, and since our organization is named Something, Inc., the company name. Next, we had to choose the app name.
Choose a Unique App Name
It’s important to ensure the name is not already taken in the App Store. This avoids conflicts and ensures your app is easy to find and unique.
I know that everyone's app already has a unique name, but this name may already be taken.
Decide on the SKU
We then needed to decide on the SKU, an internal identifier for the app. We chose "something000"—a simple identifier that our team can easily recognize and manage.
The SKU is used to track your app internally and must be unique within your account.
Configure User Access
One last thing to consider when setting up the app is user access. As an organization, you have the option to give either full or limited access to the app.
We decided on full access for our team to ensure everyone who needs to can manage the app.
However, if you’re in a larger organization, you might want to limit access to specific team members to maintain better control.
And that’s where we are for now! Setting up an app as an organization involves a few more steps than for individual developers, and it can take a bit of time, especially with the verification process.
But with patience and the right information, you’ll get there. Stay tuned for more updates as we continue our journey.
Thanks!
