# How to Publish an App on the App Store and Google Play from Kuwait

URL: https://www.upgrade-kwt.com/articles/publish-app-store-google-play-kuwait

By UPGRADE · Published: 2026-11-03 · Updated: 2026-11-03

To publish an app from Kuwait you need organisation developer accounts with Apple and Google under your company's legal name, both verified with a D-U-N-S number. You also need store listings with screenshots captured on each platform, accurate privacy declarations, a public privacy policy, in-app account deletion and working demo accounts for the reviewers. Then comes review, which has taken us two to four days per cycle at Apple and about two days for a new account's first review at Google. This guide walks through each step in order, with the traps we hit along the way.

## Before you start: the choices you only make once

A few fields in the publishing process are permanent or very expensive to change, and the forms don't warn you. Decide them deliberately before you open either console.

- Account type: an organisation account shows your company's name; an individual account shows a person's name
- Account country: set at sign-up and not something you can switch later
- Apple's public developer name: comes from your legal entity and appears on every app you publish
- Bundle ID (Apple) and package name (Google): the app's permanent identity, and a new one means a different app

## Step 1: Get a D-U-N-S number for your company

A D-U-N-S number is a nine-digit company identifier issued by Dun & Bradstreet. Apple and Google both use it to confirm that an organisation is a real, registered company and that its legal name matches the developer account. Look up whether your company already has one before requesting a new number, and leave time for it to be issued or corrected.

The name has to match exactly, character for character, across the D-U-N-S record, the developer accounts and what you publish. Apple also asks organisations for a public website on the company's own domain, so make sure your website shows the same legal name.

## Step 2: Enrol in the Apple Developer Program as an organisation

Enrol with an Apple Account on a company email address rather than someone's personal one, choose the organisation option, and enter the legal entity name and D-U-N-S number. The person enrolling must have the authority to sign legal agreements for the company, and Apple may contact them to verify. Once approved, invite your developer as a team member instead of sharing the login.

Two agreements follow. The free-apps agreement is enough for an app that is free to download and takes no in-app purchases. Sign the paid-apps agreement only if the app will have a price or sell digital content through Apple. If you distribute in the European Union you will also be asked whether you are a trader under the EU Digital Services Act.

## Step 3: Create a Google Play organisation account

Create the Play Console account as an organisation, with the same legal name and D-U-N-S number, and complete Google's identity verification. Google shows the developer name, email and website on your public developer page, so use company details.

Account type matters more on Google Play than most people expect. A new personal account must run a closed test with at least 12 testers for 14 days in a row before it can publish to production. Organisation accounts are not subject to that rule. Google is also extending developer verification to apps installed outside the Play Store, so register your apps under the right account from the start.

## Step 4: Make sure the app meets the rules before you build the release

Several requirements need code, so check them before the final build rather than the day you submit:

- If users can create an account, they must be able to delete it from inside the app (Apple), and Google Play also requires a web page explaining how to request deletion
- A public privacy policy that describes what the app really collects
- A support URL for the App Store listing
- Working demo logins for every role in the app, which must not expire or need a one-time code
- No in-app path that signs a business up to a plan billed outside the App Store, including a link to do it on your website
- On Android: the target API level Google currently requires and 16 KB memory page support
- On iOS: an app icon with no transparency channel, and your encryption declaration answered

## Step 5: Prepare the store listing in Arabic and English

Both stores give the app name 30 characters. Apple adds a separate 100-character keyword field, while Google Play has no keyword field at all, so its title and description carry the search weight. Add Arabic as a localisation on both stores so customers in Kuwait see the listing in their language.

Screenshots are where Apple rejected one of our apps. The iPhone images had been captured on an Android emulator and showed an Android status bar, which breaks Apple's rule against non-iOS content in the listing. Capture every image on the platform whose store it is going to. Apple accepts only specific screenshot sizes and rejects others rather than resizing them. It uses the same screenshots for every language unless you upload localised ones, and it needs a separate iPad set only if your app supports iPad.

## Step 6: Fill in the privacy and content forms honestly

Apple's App Privacy section and Google Play's Data safety form ask what data the app collects, why, and whether it is linked to the user. Answer them from what the app and its libraries actually do, not from what you intend, because reviewers compare the declarations with the app. Google Play also asks whether the app uses the advertising ID, and the answer must match the permissions in the built app, including ones added by third-party libraries.

Both stores also have an age or content rating questionnaire and, on Google Play, a target-audience section. They take minutes, but each one blocks submission until it is done.

## Step 7: Test, submit and get through review

Test the exact build you will submit, through TestFlight on iOS and an internal or closed testing track on Google Play, on real phones, starting from a fresh install. Then submit. These are the review times we have actually measured:

When an app is rejected, the message cites a guideline number. Read it literally, fix exactly that, and reply in the review thread. A rejection that is only about the listing, such as screenshots or descriptions, can be fixed without uploading a new build. One more Google Play trap: when you promote an app from closed testing to production, the list of countries starts empty. Select your countries, or the app goes live nowhere.

- Apple, first submission from a new account: 2 days
- Apple, resubmission after a rejection: 2 to 4 days
- Google Play, a new account's first app on a closed track: about 2 days
- Google Play, promotion from closed testing to production: about 5 days

## After approval: keep the accounts healthy

Publishing is not a one-off. Apple's membership renews every year and the signing certificates have their own expiry dates. Google raises its target-API requirement every August and checks the builds in every track, including old testing tracks. Keep the developer accounts under a company email, keep at least two people with admin access, and write down which account, key and certificate each app depends on. The day you need an urgent update is the wrong day to discover an expired certificate.

## Questions people also ask

**How long does it take to publish an app on the App Store?**
Apple says most submissions are reviewed in under 24 hours. In our own submissions a review cycle has taken two to four days. Setting up the developer account, including the D-U-N-S number and verification, can take longer than the review itself, so start it early.

**Can I publish an app as an individual instead of a company?**
Yes, but the listing then shows your personal name, and on Google Play a new personal account must run a closed test with at least 12 testers for 14 days before publishing to production. A company app is better published under an organisation account.

**Do I need a website to publish an app?**
You need a public privacy policy on both stores and a support URL for Apple, and Apple asks organisations for a website on their own domain when they enrol. Google Play also needs a web page explaining how users can request deletion of their data.

**Why do apps get rejected by Apple?**
In our experience Apple rarely rejects code. Rejections come from the listing (for example screenshots with non-iOS content), from reviewers being unable to reach parts of the app, and from business-model rules such as signing organisations up to a plan billed outside the App Store.

**Do I need Arabic screenshots for the App Store?**
No. Apple uses the same screenshots for every language unless you upload localised ones. You do need to add the Arabic listing text so customers searching in Arabic see it.

## Related services

- [Mobile App Development](https://www.upgrade-kwt.com/services/mobile-app-development)

## Related work

- [Salwa — Grocery delivery platform for the Salwa area in Kuwait](https://www.upgrade-kwt.com/work/salwa)
- [Hodori — School attendance system for schools, nurseries and kindergartens in Kuwait](https://www.upgrade-kwt.com/work/hodori)

---

UPGRADE is a software solutions company in Kuwait building ERP and CRM systems, company management systems, mobile apps, websites and automation — in Arabic and English.

- Email: info@upgrade-kwt.com
- Location: Kuwait
- Website: https://www.upgrade-kwt.com
