App development
What to prepare before launching an app on the App Store and Google Play
What to prepare before submitting a business app to the App Store and Google Play: accounts, D-U-N-S, testing, privacy disclosures, account deletion and technical requirements.

If your app will be published under your company's name, start the administrative work at least a few weeks before the target date: organization accounts with Apple and Google, a D-U-N-S Number, a privacy policy and a clear list of the data you collect. Code is rarely the only cause of delays. Often the app is ready, but publishing waits on organization verification, a mandatory testing period or a missing account deletion feature.
This article is for owners and managers who commission a mobile app and need to plan its launch. By the end you will know what to ask your development team for, what the company itself must provide and which lead times to build into the plan. The requirements below were checked against Apple's and Google's official documentation as of November 2026. The platforms change them, so check again before you submit.
What takes the longest
The table orders the tasks by when it makes sense to start them. The time frames are the ones the platforms themselves state, not a guarantee of approval.
| Task | What the platform says | When to start |
|---|---|---|
| D-U-N-S Number for the company | Google says getting one can take up to 30 days and that you cannot create an organization account without it; Apple also requires one for organizations. | As soon as the project is commissioned |
| Closed test on Google Play for a new personal account | At least 12 testers opted in continuously for at least 14 days, then you apply for production access; review usually takes up to 7 days. | At least 3 weeks before launch |
| Payment method verification on Google Play | If you monetize, verification can take up to 5 days. | Before your first paid content |
| Privacy policy and data forms | Required by both stores before submission, including data collected by third-party SDKs. | In parallel with development |
Organization or personal account
For a business app, an organization account is usually the better choice. On Apple, the organization's name is shown as the seller; with an individual account, the developer's personal name is shown. Apple requires organizations to be a legal entity with a D-U-N-S Number, an email address on the company domain and a working public website. Membership costs 99 USD per year, and prices may vary by region. Google requires organization accounts to provide a D-U-N-S Number, address, phone number and website, and it shows the developer's legal name, address, email and phone number on Google Play.
If an outside contractor registers the account in their own name, the app will be listed as theirs. Agree in advance who owns the accounts and how you get access if you change teams.
The closed test with 12 testers for 14 days applies to personal Google Play accounts created after November 13, 2023. Testers who opt out before day 14 do not count. If you use such an account, recruit people from your real target audience, give them clear tasks and collect their feedback, because you have to summarize it when you apply.
Technical requirements that block submission
- Android: since August 31, 2026, new apps and app updates on Google Play must target Android 16 (API level 36) or higher. The possible extension ran until November 1, 2026. An existing app that targets API level 34 or lower is no longer shown to new users on newer Android versions.
- iOS: since April 28, 2026, apps uploaded to App Store Connect must be built with Xcode 26 and the iOS 26 SDK or later.
- EU: to distribute on the App Store in the European Union, Apple requires a trader status declaration under the Digital Services Act. Without it, the app is not available in the EU.
- Age rating: Apple introduced a new age rating system, and the questions in App Store Connect must be answered to avoid interruptions to app updates.
The practical question for an owner is whether keeping up with these requirements is part of the maintenance contract. They change every year, so an app without maintenance can stop receiving updates even when its code still works.
Privacy: the two forms are not the same
Both stores show users what data an app collects, but their categories differ. Google itself notes that the Data safety form asks for additional and different information than iOS does. So do not copy your answers mechanically.
- List every SDK: analytics, ads, push notifications, sign-in, payments and crash reporting. The data they send must be declared as yours.
- Complete App Privacy in App Store Connect: data types, what they are used for, whether they are linked to the user and whether they are used for tracking.
- Complete Data safety in Play Console. It is required for apps on closed or open testing tracks too, not only in production.
- Publish a privacy policy at a public URL. Apple requires a link to it both in the metadata and inside the app (guideline 5.1.1).
- If your declaration does not match the app's actual behavior, Google may block updates or remove the app.
Account deletion: check it before review
If users can create an account in your app, both platforms require that they can also delete it. Apple requires that deletion can be initiated in the app and removes the whole account and the associated personal data; offering only temporary deactivation is not enough. Outside highly regulated industries, you should not make people call or send an email. Google requires an in-app deletion path and a web page where people can request deletion without reinstalling the app.
This affects the backend, not just one button: you need to decide which data is deleted, which must be kept by law, how active subscriptions are handled and what message the user receives. Ideally, these decisions are already written down in the brief before you request a quote.
Final checklist before submission
- The app has been tested on real devices, not only in iOS Simulator, and has no visible crashes.
- If there is a login, the review notes include a working demo account, and the backend is switched on. Apple explicitly rejects incomplete builds, placeholder text and broken links (guideline 2.1).
- In-app purchases are configured, visible and working.
- Screenshots and descriptions match the actual version.
- The privacy policy, App Privacy and Data safety describe the same data.
- Account deletion works from inside the app, and for Google there is also a web page.
- Target API level, Xcode version, EU trader status and age rating have been checked against the current requirements.
- It is clear who maintains the app after launch and who monitors messages from Apple and Google.
A hypothetical example
This example is invented for illustration only. A chain of three salons wants a booking app before the start of the season. If the company has no D-U-N-S Number and the team only thinks about the stores once the code is ready, getting the number alone can take up to 30 days. Add a 14-day closed test and the review if a new personal Google Play account is used, and the date easily slips. If the administrative tasks start in week one and the app launches as an MVP with a clear scope, these timelines run in parallel rather than one after another.
Next step
If you are planning a mobile app, Hostado's app development service covers iOS, Android and web apps, including maintenance and upgrades. In UI/UX design, it helps to plan the consent, account settings and deletion screens from the start. The most useful thing you can bring to a first conversation is your answers to the questions in this checklist, even if some of them are "we don't know yet".