To publish an app on the App Store and Google Play from Saudi Arabia (or anywhere in the GCC) under your company's name, you need an organization developer account in each store, a D-U-N-S number for your business, a published privacy policy, completed data disclosure forms, and then a pass through review. What delays most companies is not the code; it is the paperwork left until the final week. This guide puts the steps in the right order, with the fees, realistic timings and the most common reasons apps get rejected.
Who should own the developer accounts?
The rule we give every client: the accounts belong to your business, not to your developer or agency. Your app is a company asset. Whoever owns the account controls updates, ratings, user data and store revenue. If an account is opened under a freelancer's name and the relationship ends, transferring the app is possible but can be slow and frustrating.
The right way is to open the accounts yourself and invite your development team with specific roles: through Users and permissions in Google Play Console, and through Users and Access in App Store Connect. Your developers can work freely while ownership stays with you.
Personal account or organization account?
| Criterion | Personal account | Organization account |
|---|---|---|
| Name shown in the store | Your personal name | Your company's legal name |
| D-U-N-S number | Not required | Required by Apple and Google |
| Customer trust for business apps | Lower | Higher, especially with payments and personal data |
| Pre-launch testing | Google may require closed testing for some new accounts | Depends on Google's current policy |
| Best fit | Individual developers, personal projects | Any app that represents a business |
If the app is for a clinic, a store, a real-estate brokerage or a restaurant, an organization account is the natural choice. A customer who sees an unknown individual's name instead of your brand may hesitate before entering their details or card.
The D-U-N-S number: the step that delays most Gulf companies
A D-U-N-S number is a nine-digit identifier issued free of charge by Dun & Bradstreet. Both Apple and Google use it to verify your organization. Issuing one can take up to around 30 days, so request it in the first week of the project, not after development is finished.
How to avoid D-U-N-S delays
- Use your legal entity name exactly as it appears on your commercial registration, and the same English spelling everywhere.
- Make sure the address and phone number in the D-U-N-S request match what you will enter in the developer accounts.
- For a Google Play organization account, the legal name and address must match your Google payments profile. A small spelling difference can stall verification.
- Check first whether your company already has a number; some businesses have one without knowing it.
Publishing on Google Play, step by step
- Register an organization developer account in Google Play Console. The registration fee is a one-time USD 25.
- Complete identity verification with your company details, D-U-N-S number and contact information.
- Create the app and set the default language; ideally add both Arabic and English store listings.
- Enable Play App Signing. Google holds the app signing key and you hold the upload key. Store the upload key and its passwords somewhere your company controls.
- Complete the content forms: privacy policy URL, the Data safety form, content rating and target audience.
- Start with a testing track, internal or closed. Google may require some new accounts to complete testing before production access, so check the current policy when you open the account.
- Promote the release to production and watch the review status.
On our own work, including the Azkar Almumin app and the Tap Arrows puzzle game, signed Google Play releases move through a clear path from testing to production. That is the standard to expect from any team you hire.
Publishing on the Apple App Store, step by step
- Create a company Apple ID using an email address on your own domain, not someone's personal inbox.
- Enroll in the Apple Developer Program as an organization. The fee is USD 99 per year. Apple requires a D-U-N-S number, a person with legal authority to bind the company, and typically a public website for the organization.
- Set up certificates and provisioning profiles with your developers, and make sure they live inside your company account.
- Test through TestFlight with your team and a handful of real customers before submitting.
- Complete the App Store Connect listing: description, screenshots, privacy policy URL, support URL and the App Privacy details shown on your product page.
- Submit for review, with a working demo account if the app requires sign-in.
Store listing, privacy policy and data disclosures
Your store listing is the first thing customers see, so write it in Arabic first for your Saudi and Gulf audience, then in English for residents and visitors. Use real screenshots in the matching language; English screenshots on an Arabic listing look careless.
Your privacy policy must be a published page on your website explaining what you collect, why, and who you share it with. If your app serves users in Saudi Arabia, the Personal Data Protection Law (PDPL), supervised by SDAIA, has been enforceable since September 2024. In practice that means a clear privacy notice, plus consent and a stated purpose at the point of collection. In the UAE, Federal Decree-Law 45 of 2021 applies, and free zones such as DIFC and ADGM have their own regimes. This is not legal advice, but these points should be visible in the app itself.
Make the disclosures match reality
Google's Data safety form and Apple's App Privacy details must reflect what the app really does, including analytics, advertising and notification SDKs. And if your app lets users create an account, both stores expect you to provide a way to delete it, so plan that feature from the start.
App Store review rejection: common causes and how to avoid them
| Common rejection cause | How to avoid it |
|---|---|
| Crashes, blank screens or broken links | Full testing on real devices before submission |
| No demo account for the reviewer | Provide working credentials and short instructions |
| App is just a website in a wrapper | Give the app its own value: account, notifications, orders |
| Privacy disclosures do not match behaviour | Audit every SDK that collects data |
| Permission requests without explanation | Explain in-app why you need location or camera |
| Selling digital content outside in-app purchase | Check Apple's rules on digital goods before you design |
| Screenshots or description do not match the app | Use real captures from the submitted build |
A rejection is not the end. Read the reviewer's message carefully, fix exactly what was flagged, and resubmit with a polite note explaining what changed. No developer can guarantee approval; the decision belongs to the store.
A realistic timeline from company to live app
| Step | Planning estimate |
|---|---|
| D-U-N-S number issued | Up to around 30 days |
| Google Play organization verification | Usually several days |
| Apple Developer Program enrollment as an organization | Days to weeks, depending on verification |
| Store listings and privacy forms | A few working days |
| Closed testing, if Google requires it | Per current policy |
| Review in each store | Often days; longer after a rejection |
These are planning estimates, not promises, but they show why the administrative steps should run in parallel with development. For help choosing a team that handles this stage well, read our guide to choosing an app development company in Saudi Arabia. If you are still budgeting, see Mobile App Development Cost in 2026.
Pre-submission checklist
- D-U-N-S number issued under the exact legal name.
- Developer accounts owned by the company, with developers added as users.
- Signing keys stored by the company.
- Published privacy policy and a working support URL.
- Data forms that match the app's actual behaviour.
- Demo account for the reviewer.
- Arabic and English store listings with real screenshots.
- Account deletion option if the app allows sign-up.
This checklist is a standard part of our mobile app development service, because an app that never reaches the store is worth nothing, however well it is built.
Frequently asked questions
How much does it cost to publish an app on the App Store and Google Play?
Google Play developer registration is a one-time USD 25, and the Apple Developer Program costs USD 99 per year. These are account fees only; they do not cover development, hosting or updates. The D-U-N-S number itself is free from Dun & Bradstreet, but plan for the time it takes, which can be up to around 30 days.
Do I need a commercial registration to open a company developer account?
Organization accounts at Apple and Google require a legal entity with a D-U-N-S number, which in practice means your business needs to be registered. Use the legal name exactly as it appears on your commercial registration, with the same English spelling everywhere. Without a registered entity you can open a personal account, but your own name will appear as the seller.
Who should own the developer account, me or the development company?
You, always. Open the accounts under your company with a company email address, then add your developers as users with specific roles in each console. You keep control of the app, ratings, user data and revenue, and you can change development partners later without having to transfer the app between accounts.
Why was my app rejected by the App Store, and what should I do?
The most common causes are crashes during review, a missing demo account, an app that only shows a website, privacy disclosures that do not match the app, or permission requests without explanation. Read the reviewer’s message carefully, fix exactly what was flagged, and resubmit with a short note on what changed. Nobody can guarantee approval in advance.
Ready to launch?
Have an app in development, or an idea you want live in Saudi Arabia or the GCC? Tell us where you are today and we will review your accounts, paperwork and timeline with you, then propose a clear launch plan before you start.
