The App Store and Google Play publishing process

1. Developer accounts — in your company's name

The Apple Developer Program and Google Play Console accounts determine who legally owns the app. We recommend opening these accounts in your company's name; moving an app that was published under the developer's account later is a hassle.

When you open an organization account, both stores require company verification, which usually means a D-U-N-S number (an international company identifier). If you don't have one, getting it can take anywhere from a few days to a few weeks, so we start this step in the first week of the project. Apple charges an annual membership fee and Google a one-time registration fee; you can find the current amounts on the stores' own pages.

2. Privacy and data declarations

Both stores ask you to declare which data the app collects, for what purpose, and whether it is shared with third parties (privacy labels on Apple, the Data safety section on Google). An accessible link to a privacy policy is also mandatory. For apps where users create an account, users are also expected to be able to delete that account from within the app.

These declarations need to be consistent with your privacy notice in Türkiye. Our KVKK compliance work — KVKK being Türkiye's Personal Data Protection Law — covers these texts as well.

3. The store listing

• App name and short description
• Full description (in Turkish, plus other languages if needed)
• Screenshots for each device size
• App icon and feature graphic
• Category, age rating, support email and website

4. Test builds

Before launch, we test the app with real users. On iOS we use TestFlight; on Android, the internal and closed testing tracks. Google Play requires a closed testing period of a certain length for new apps published from personal developer accounts, so going with an organization account makes things easier here too.

5. Review and release

Once the app is submitted, the store review begins. How long it takes varies; it is usually quick, but a rejection can happen. The most common reasons for rejection are:

• No test account provided so the review team can sign in
• The privacy declaration doesn't match how the app actually behaves
• The app does little more than wrap a website
• Buttons that don't work, or empty screens
• The description mentions features that aren't in the app

If the app is rejected, we read the reason, fix the issue and resubmit. We build a buffer for this into the schedule from the start.

Release checklist

• Were the developer accounts opened in the company's name, and is the D-U-N-S number ready?
• Is the privacy policy live and consistent with the declarations?
• Are the test account and review notes ready?
• Are the screenshots from the current version?
• Is error and crash tracking (crash reporting) set up?

After launch

Every year the stores update their target operating system version requirements; apps that aren't updated can gradually become invisible to new users. As part of maintenance, we keep up with these updates and monitor user reviews.

Frequently asked questions

We handle the publishing process end to end as part of our mobile app service. For questions, call +90 850 432 55 13 or use the contact page.