How to publish your app to the App Store
To publish an app to the App Store you need an Apple Developer account, owned by you, not the agency, plus assets like screenshots, a description, and a privacy declaration. The app is uploaded and reviewed by Apple, which takes a day to a few days. It can be rejected and need fixes before release.
Finishing the app doesn’t mean it’s in the App Store. Between the last line of code and an app users can download lie a number of steps: accounts, assets, review, and sometimes a rejection to handle. None of it is hard, but it takes time and works best planned ahead. Here’s the path, from your perspective as the client.
Why the developer account should be yours
The most important question is settled before publishing even starts: who owns the Apple Developer account. The answer should be you, the client, never the agency.
The account is the hub of the entire app. It’s tied to the app in the store, to the users, and to any revenue. If the agency owns the account, you’re in a position of dependence that can turn uncomfortable. If you want to switch providers, or a conflict arises, you could in the worst case lose control of your own app, users and all. Moving an app between accounts after the fact is also a hassle.
The solution is simple: register the Apple Developer account in your name from the start and give the agency access as a developer, not ownership. That way they can do their job while control stays with you. This is one of the questions worth settling in writing before the project kicks off.
Assets required for publishing
The app itself is one thing, but the app store also requires a package of assets around it. That’s often underestimated and becomes a bottleneck at the end if it isn’t prepared.
- Screenshots in the formats and sizes Apple requires, showing the app’s key views.
- Title, description, and keywords that explain what the app does and make it searchable.
- An icon at the correct resolution.
- A privacy declaration describing what data the app collects and how it’s used.
- Support contact and privacy policy, often with a link that needs to work.
| Asset | Purpose |
|---|---|
| Screenshots | Show the app in the store |
| Description and keywords | Explain and make the app searchable |
| Privacy declaration | Required disclosure of how data is handled |
| Privacy policy | Link that must be in place |
Start gathering the assets early. Writing a good description and producing screenshots takes longer than people expect, and there’s no reason to let that hold up an otherwise finished app.
Review times and rejections without panic
Once the app and its assets are submitted, Apple takes over for review. It usually takes anywhere from a day to a few days, but there’s no guarantee it will go quickly. Review should therefore always be built into the timeline with margin, especially if the launch is tied to a date or a campaign.
It’s also common for an app to be rejected the first time, and it’s rarely dramatic. Apple states the reason, and it’s often a single detail: an unclear point in the description, a missing piece of information, or an interface requirement that isn’t met. Treat the rejection as a checklist. Read the reason carefully, fix what’s flagged, and resubmit. Panic doesn’t help, and a rejection isn’t a final no, it’s a step in the process.
A concrete scenario
Say you’re planning to launch an app in time for an event. You own the developer account, you’ve gathered the assets, and you submit the app two weeks ahead. Review takes three days and the app is rejected: the privacy declaration is missing a detail about data collection. You fix it the same day and resubmit, and the next review is approved. Thanks to the margin in the plan, the rejection became a footnote instead of a crisis. Had you submitted the day before the event, that same small detail could have derailed the launch.
That kind of planning ahead is exactly what keeps a launch calm. At Weapp, we’ve taken many apps all the way to the store and know where things tend to snag. Read more about our services or get in touch if you’d like support through the publishing process.
Frequently asked questions
Who should own the Apple Developer account?
You, as the client, not the agency. The account is tied to the app, its users, and its revenue, and if the agency owns it, you're in a position of dependence. If you switch providers or end up in a dispute, you could in the worst case lose control of your own app. Register the account in your name from the start and give the agency access, not ownership.
What does it cost to publish on the App Store?
An Apple Developer account costs USD 99 a year. That fee is separate from the development cost and runs for as long as the app stays in the store. Stop paying and the app disappears. Count it as an ongoing cost, alongside servers and other services the app depends on to function.
What assets do I need ready?
Screenshots in the correct format, a title and description, keywords, an icon, and a privacy declaration describing how the app handles data. A support contact and a link to a privacy policy are often required too. Gathering the assets takes more time than most people think, so start early, well before the app is ready to submit.
How long does Apple's review take?
Usually anywhere from a day to a few days, but there's no guarantee. The review can drag on, and the app can be rejected and need fixes before it's approved. Plan review time with margin, especially if the launch is tied to a date. Assuming approval within a day builds in unnecessary risk.
What do I do if the app is rejected?
Stay calm, it's common and rarely dramatic. Apple states the reason for the rejection. Read it carefully, fix what's flagged, and resubmit. It's often a detail in the description, a missing piece of information, or an interface requirement. A rejection is a checklist to work through, not a final no.