Your app is ready. Next stop, the store.

The App Store and Google Play publishing process covers all the steps your app has to go through to be listed in the stores and become available for users to download. Most of these steps aren't technical but administrative and content-related: whose name the account is opened in, how privacy information is declared, what the store page says. In this article we go through the points companies most often get stuck on, in order.

An important note: Apple and Google update their store rules regularly. The information below is a general framework; before every release, check the current requirements in Apple's and Google Play's developer policies.

Whose name should the developer account be in?

The most common mistake, and the hardest to fix later, is publishing the app on the software agency's account or an employee's personal account. The app is your brand and your customer relationship; the account should be in your company's name too.

• Open an organization account. Both Apple and Google require company verification for accounts opened in an organization's name. This verification usually relies on an international company identifier called a D-U-N-S number. If your company doesn't have one, it can be obtained free of charge, but it can take anywhere from a few days to a few weeks, so start early.
• You own the account; the team gets access. Both stores let you add other users to the account with specific roles. The development team is added with release permissions, while you remain the account owner.
• Use a company email address. Link the account not to a personal Gmail address but to a shared company address, so access isn't lost when staff change.

What to prepare for the store page

The store page is your app's shop window. What you need to prepare:

Privacy labels and data declarations

Both stores ask you to declare which data your app collects, what it is used for and whether it is shared with third parties. On Apple's side, this is the App Privacy section shown on the store page; on Google Play, it is the Data safety section.

Getting this declaration right matters. Remember that analytics, crash reporting, advertising or map libraries built into your app can also collect data; the declaration covers not only your own code but these as well. A gap between the declaration and the app's actual behavior can cause problems both during review and afterwards.

This declaration must also be consistent with your privacy notice under KVKK (Türkiye's Personal Data Protection Law). Preparing the two together makes the job easier and prevents contradictions. We handle this side together with our KVKK compliance work.

Testing and review

Before submitting to the store, the app needs to be tried out with real users. TestFlight on Apple's side, and closed and open testing tracks on Google Play, exist for exactly this. For some newly created account types, Google Play may require a period of closed testing before public release; build this requirement into your plan from the start.

Things to watch for during review:

• Provide a test account for apps that require login. If the review team can't get into the app, it will be rejected outright. This step is often forgotten for closed dealer or staff apps.
• Write a review note. Briefly explain who the app is for and whether any special hardware or location is required.
• Offer account deletion. If accounts are created inside the app, both stores expect users to be able to request deletion of their account easily.
• Justify permissions. State clearly in the permission prompt's description why you ask for camera, location, contacts and similar permissions.

Common rejection reasons

• The app only displays a website inside a frame and offers no additional functionality
• Broken links, empty screens, "coming soon" pages
• A privacy policy that is missing or doesn't match the app
• No test account provided, or a test account that doesn't work
• Not following the store's payment rules when selling digital content

A rejection is usually not the end but a list of fixes. Correcting the issues according to the review team's explanation and resubmitting is a normal part of the process.

Pre-launch checklist

• Are the developer accounts opened in the company's name?
• Are the D-U-N-S number and company verification complete?
• Is the privacy policy live on the website?
• Have the privacy labels been filled in, including all libraries used?
• Are the test account and review note ready?
• Are the screenshots and descriptions ready?
• Have real users tried the app in closed testing?

How we do it at Globya

We help you open the store accounts in your company's name and have ourselves added as team members; ownership of the account always stays with you. We prepare the privacy declaration and the privacy notice together, and we manage the testing process and review notes. After launch, we keep monitoring the app's compliance with the current store rules; we cover that part in our article on app maintenance and updates. You will find the overall framework on our mobile app page.

Frequently asked questions