How to launch an app: the timeline nobody plans for

The short answer: your launch date is not the day the build is finished. Budget two to three weeks between first submission and approval, one to two weeks for later updates, and assume at least one round of fixes. Every launch we have seen slip, slipped here, and almost none of it was engineering.

We get a version of the same message several times a year: “we’re launching Tuesday, can you just submit the app to the stores, it takes a day, right?” The team submits Monday night. Wednesday morning the rejection arrives. Marketing is already booked, the announcement is written, and now everyone is fixing icon sizes under pressure. The problem was never the review. It was treating submission as an upload instead of a dependency.

If you want the launch handled rather than explained: we are Digital U, we build and ship mobile apps from $5,000 (pricing page), store submission included. A free 30-minute call gets you a launch date you can actually hold to. The rest of this article is how that date is calculated.

What actually has to exist before you can submit

This is the part that surprises people, because none of it is code. Before a build can even go up, the accounts have to exist, and they take real time to set up.

For Apple, the Apple Developer Program is $99 per year. Enrolling as an individual or sole proprietor needs your Apple Account with two-factor authentication, legal age of majority and your legal name, which then appears publicly as the seller on the App Store. Enrolling as an organization is a different process: Apple requires a recognized legal entity (trade names and DBAs are not accepted), a D-U-N-S number from Dun & Bradstreet, a work email on your organization’s domain, and a publicly available, functional website on that same domain. Some cases need notarized business documents.

Read that last requirement again, because it catches people: Apple will not enroll your company until your company has a working website on its own domain. If your plan was to launch the app first and sort out the website later, the order is wrong.

For Google, the Play Console developer account is a one-off $25 registration fee, considerably lighter, though Google runs its own identity verification.

Alongside the accounts, both stores want the same paperwork before review: a privacy policy at a public URL, data collection disclosures, a content rating, and store assets at the right sizes for every device class. None of it is hard. All of it takes longer than a day when nobody has been assigned to it.

What the launch actually costs to get off the ground

Item	Cost
Apple Developer Program	$99 per year
Apple Developer Enterprise Program	$299 per year
Google Play developer account	$25, one-off
D-U-N-S number (organization enrolment with Apple)	Free in most jurisdictions
Privacy policy hosted at a public URL	Your website, which you need anyway for Apple

Those are the gate fees, not the cost of the app. The build itself is a separate conversation, and we put real published ranges in how much a mobile app costs in 2026.

Have a launch date already promised to someone? Tell us what it is in a free 30-minute call or drop us two lines. We will tell you honestly whether it survives contact with store review, even if we never work together.

Plan the launch backwards from the store, not forwards from the build

The fix here is not technical, it is operational. Treat the first submission as a rehearsal you expect notes on, and put it on the critical path where it belongs.

Working backwards from the date you want to announce:

• Three weeks out. Accounts exist and are verified, privacy policy is live, store assets are done. Submit the first build even if the last feature is still in progress. The goal of this submission is to collect feedback, not to go live.
• Two weeks out. First review response is in. Fix whatever came back and resubmit. This is the round almost everybody forgets to budget, and it is the one that always happens.
• One week out. Approved build sits ready for release. Both stores let you hold an approved build and release it manually, which is the whole point of being early.
• Launch day. You press a button on something already approved, instead of refreshing a review status with marketing waiting.

A team that has done this before is never surprised by it. The difference is not engineering skill, it is having built the buffer in.

What first submissions usually get caught on

Almost never the interesting parts of the app. In practice it is the boring surface: privacy disclosures that do not match what the app actually collects, screenshots missing for a device size, a login the reviewer cannot get past because there is no demo account, a feature that only works behind a code the reviewer was not given, placeholder content still visible, or a payment flow that routes around the store’s own purchase rules.

There is an upside to going early that people miss. Review feedback is often genuinely useful, and it is far easier to act on when you are not racing a launch date. Accessibility problems and confusing flows are much cheaper to fix in week three than in the final forty-eight hours.

The things that are due on launch day but are not the launch

Launch is the start of the part you cannot undo cheaply, so a few things need to be in place before the first real user arrives, not after.

You need to know what people do in the app, which means analytics and crash reporting configured and separated from your test data. We covered what to track, and what to ignore, in mobile app analytics: what to track. You need a way for someone to reach you that is not a one-star review. And you need to be able to tell which version somebody is on, because from day one your users are spread across builds you no longer control.

That last point is the one that matters most later, and we wrote about it in what remains after AI writes the code.

The annual cost nobody puts in the launch budget

A launch is not the end of spending, and this is the part that reaches founders as a surprise roughly a year later.

Both platforms move their minimum requirements every year, and compliance is not optional. Google Play required, from 31 August 2026, that new apps and updates target Android 16 (API level 36), with existing apps needing at least Android 15 (API level 35) to stay available to new users on newer devices. Apple has required since 28 April 2026 that anything uploaded to App Store Connect be built with Xcode 26.

So an app that works perfectly and needs no new features still needs a maintenance slot every year, purely to stay in the stores. Teams that budget for it do a small incremental update. Teams that do not get a store warning and an emergency multi-version jump, usually at the worst possible moment, and usually priced as a surprise.

Frequently asked questions

What is needed to launch an app? A developer account on each store (Apple $99 per year, Google $25 one-off), a privacy policy at a public URL, data collection disclosures, a content rating, store assets at the correct sizes, and a build that passes review. Apple’s organization enrolment additionally requires a legal entity, a D-U-N-S number and a working website on your organization’s domain.

How much will it cost to launch an app? The store gate fees are $99 per year for Apple and a one-off $25 for Google Play. That is separate from building the app, which in published Romanian offers ranges from a few thousand dollars to over $110,000 depending on complexity, detailed in how much a mobile app costs in 2026.

Can I launch an app for free? No. Both stores charge for a developer account before you can publish: $25 once for Google Play and $99 per year for Apple. You can build an app for free, but you cannot distribute it through the official stores without those accounts.

Do I need an LLC to launch an app? Not for Apple, if you enrol as an individual or sole proprietor, but there is a trade-off: your legal name becomes the seller shown publicly on the App Store. To publish under a company name you need organization enrolment, which per Apple requires a recognized legal entity (trade names and DBAs are not accepted), a D-U-N-S number, a work email on your organization’s domain and a functional public website on that domain.

How long does app store review take? Individual reviews are often fast, but review time and approval time are different things. Plan two to three weeks from first submission to approval and one to two weeks for later updates, because first submissions almost always come back with at least one round of fixes, and each resubmission restarts the clock.

Is it difficult to launch an app? Technically, no. Operationally, it catches most first-time teams out, because the work that blocks a launch is administrative rather than technical: accounts, verification, privacy disclosures, assets and review feedback. It is difficult mainly when it is left until the last week.

How much money do I need to start an app? At minimum $124 in the first year to hold both store accounts, plus whatever the build costs and a website you will need anyway for Apple’s organization enrolment. Budget separately for a maintenance slot each year, since both platforms raise their minimum requirements annually.

Should I launch on both stores at the same time? You can, but they are different processes with different timelines, and Apple is usually the slower and stricter of the two. If a simultaneous launch matters for your announcement, plan the whole schedule around Apple’s timeline and hold the approved Android build until Apple clears.

Planning a launch and want to know whether the date is realistic? Drop us two lines or book a 30-minute call: we go through what has to exist before submission and work the schedule backwards with you, no obligation.