Short answer. Publishing takes six steps: an account in the company’s name on each store, a listing (name, screenshots, description, privacy policy), a signed version, tests, a review by the store, then a staged rollout. Two delays cannot be compressed: account verification, which at Apple requires a D-U-N-S Number for a company, and, at Google, for a recent personal account, a closed test with twelve testers for fourteen days. Add a review and a possible refusal: start eight weeks before the announced date. And do not publish on the developer’s account: the day he leaves, the app leaves with him.
This guide is for the manager whose app is ready, or nearly, and for the founder based in France preparing a launch in Algeria. The conditions quoted were read in the Google Play help pages and on Apple’s developer pages in November 2026; they change every year, so check them when you open your accounts. The days, the reasons for refusal and the calendar in the example are constructed. This guide covers neither the taxation of sales in the stores nor contracts.
Whoever owns the account owns the app
The figure publishes the same app in two ways, then looks at what happens the day the developer leaves.
Two types of account. Each store distinguishes a person’s account from an organization’s. At Apple, for an individual account, it is the person’s name that is displayed as the seller of the app; for an organization, a D-U-N-S Number is required, a nine-digit company identifier, along with a legal entity: trade names and branches are not accepted. At Google Play, registration costs US$25 once, and the holder’s identity is verified. The shortcut. Publishing on the developer’s account avoids that verification: the app is online sooner, under his own name.
What it costs. The listing, the users, the ratings, the statistics and the right to send an update belong to the account holder. The day he changes job, country or mind, the company no longer controls its own app. A transfer exists: according to the Google Play help pages, it moves the users, statistics, ratings and reviews to the target account; according to Apple’s, the app keeps its ratings and stays available during the operation. But it is the former holder who has to start it. The right way. The account is created in the company’s name, with two administrators; the developer is invited with a role, and leaves it at the end. It is the same rule as for the domain name, and one of the proofs to ask for before signing, as in the guide to choosing a company. A founder based in France can open the accounts in the name of the company that will carry the app; check, for the country where it is registered, the conditions for registration and, if the app is paid, for receiving payments.
«The day the developer leaves, the app leaves with the account.»
Google Play and App Store: what each one asks for
The figure compares the two stores on seven points.
Tests. Google Play requires personal accounts created after 13 November 2023 to run a closed test with a minimum of twelve testers, opted in continuously for at least fourteen days, before production access is opened; the review of that request usually takes seven days or less, occasionally longer. The requirement targets personal accounts: one more reason to open the account in the company’s name. At Apple, the testing tool is called TestFlight: it accepts up to 10,000 external testers, and the first build sent to them also goes through a review.
Review. Apple states that it typically reviews at least half of submissions in less than 24 hours and 90 % in less than 48 hours. Two requirements people forget. Since 31 August 2026, a new app or an update must target Android 16 to be accepted on Google Play, and that threshold is raised every year: an app delivered two years ago no longer passes as it is. And both stores require that a user who can create an account can also delete it. Rollout. Both let you serve only part of the users at first: a chosen percentage at Google, seven days of gradual increase at Apple. The fees and the yearly upkeep are detailed in the guide to keeping an app alive; if an installable web app is enough for you, there is no store at all: see the guide to PWA or native app.
What must be ready before sending, in five layers
The accented layer is the first: the account.
The account and the identity. The account is started first, because its verification does not depend on you. The app’s unique identifier is chosen once: it can no longer be changed after publication, and it should carry the company’s name, not the provider’s. The keys used to send versions are kept by the company, in a password vault, not on one person’s computer.
The listing and compliance. The listing is written in French, Arabic and English, with real screenshots. The privacy policy is a public page that says which data the app collects and why; the declaration made to the store has to say the same thing. The technical side. The review opens the app the way a user would: it needs a demo account if a login is required, a server switched on, and no empty screen. The decisions taken upstream, login, payment, notifications, are those of the guide to the seven decisions.
The path of a version, in six steps
The first step is accented: the account.
Account, listing, signed version. These three steps are prepared in parallel. The version carries a number, which goes up with each submission, and a signature, which proves it really comes from you. Tests. First the team, on real phones and on an ordinary mobile network; then a closed group of real users, customers, employees, partners, who find what the team no longer sees.
Review and rollout. The store tries the version, accepts it or refuses it with a reason. Once accepted, it is not necessarily served to everyone: you start with a few per cent of users, watch the crashes, then open up. And afterwards. Each update goes through the last two steps again, more briefly. That is why an urgent fix is not delivered “within the hour” on a store, and why you keep, on the server side, a way to switch a feature off without waiting for a review.
Review: five gates, and a refusal costs one more round
The figure follows a version sent on a Monday, refused a first time, then accepted.
The five gates. Apple’s review guidelines are arranged in five chapters: safety, performance, business, design, legal. Behind those words, concrete checks. Is the app complete? If it asks for a login, the guidelines ask you to include demo account information and to turn on your back-end service. Is it more than a repackaged website? Does it say which data it collects? Does it let users delete their account? Google Play applies similar rules.
After a refusal. The reason is written; you can correspond with the review team to resolve the issue before resubmitting the build, and appeal if you disagree. In the example, a forgotten demo account costs two days. A refusal that goes to the substance, a payment to redo, a feature judged insufficient, costs weeks: that is the one you avoid by reading the rules before designing, not before sending.
«The refusal that costs weeks is avoided by reading the rules before designing, not before sending.»
Eight weeks before the announced date, in 2027
Eight weeks in the example, counted back from the announced date.
- What the manager receives: the two accounts in the company’s name with the list of people who have access, the listing in three languages, the countdown calendar and, after each submission, the store’s answer.
- What the company no longer does: announce a date before having a verified account, publish on a provider’s account, discover a refusal the day before the launch, deliver an update to everyone in one go.
- What is measured: days between submission and acceptance, number of refusals and their reason, share of users on the latest version, crash rate during the rollout.
- What Symloop does: opening the accounts in the client’s name, the listing, compliance, tests, the submission and the reply to the review, the staged rollout, then every update; and the transfer of an app left on a former provider’s account.
Weeks 1 to 3, the accounts. This is the delay you do not control: obtaining the D-U-N-S Number, identity verification, exchanges with support. Weeks 2 to 4, the listing and compliance, while development is finishing. Weeks 4 and 5, the version and the team’s trials.
Weeks 5 and 6, the closed test of fourteen days. Week 7, the review, with one refusal counted in advance. Week 8, the staged rollout, to open to everyone on the announced day. If the accounts already exist in the company’s name, you gain three weeks; if the app is already on a former provider’s account, the first step becomes its transfer.
- How do you publish an app on Google Play and the App Store?
- In six steps: an account in the company’s name on each store, a listing with texts, screenshots and a privacy policy, a signed version, tests, the store’s review, then a staged rollout. The account is started first, because its verification is the delay you do not control.
- How long does it take to publish an app?
- Eight weeks in our example, starting from nothing: three for verified accounts, two for the closed test, one for the review with a possible refusal, one for the staged rollout. Only a few days if the accounts exist and the app is already tested.
- How much does it cost to publish an app?
- The store fees are known: US$25 once for Google Play, 99 USD a year for Apple’s programme. The rest is work: the listing, compliance, the tests and the exchanges with the review.
- Can the app be published on the developer’s account?
- Technically yes, and it is faster on day one. But the listing, the users, the ratings and the right to update then belong to his account. Open an account in the company’s name and invite the developer to it with a role.
- My app is on my former provider’s account: how do I get it back?
- Through a transfer from one account to the other, which both stores provide for and which keeps the users and the ratings. It has to be started by the current holder, so you need his cooperation. Without it, what remains is to publish again under a new identifier, starting from zero.
- What is a D-U-N-S Number, and why does Apple ask for it?
- It is a nine-digit company identifier, assigned by Dun & Bradstreet. Apple requires it to enrol an organization in its programme, to check that it is a real legal entity. Obtaining it takes time: ask for it at the very start of the project.
- Why does Google ask for twelve testers for fourteen days?
- It is a Google Play rule for personal accounts created after 13 November 2023: a closed test with a minimum of twelve testers, opted in continuously for fourteen days, before production access. Put those two weeks in the calendar.
- Why was my app refused?
- The reason is written in the review’s answer. Simple causes: no demo account, server off during the examination, no privacy policy, no way to delete an account. A cause of substance: an app that is only a repackaged website.
- Can you publish from Algeria, or do you need a company abroad?
- The accounts are opened in the name of the company that carries the app, in the country where it is registered. The conditions for registration and, for a paid app, for receiving payments vary by country and change: check them on the stores’ pages when you open the account.
- Does every update have to go through review again?
- Yes: each version goes through the review, then a staged rollout, more briefly than the first time. So an urgent fix is not delivered within the hour; you keep on the server side a way to switch a feature off without waiting.