App Store submission
Your app, through review and onto the store.
Having a finished build and having a live app are two different things. Submission has its own rules, and it is where a surprising number of finished apps quietly stall.
The problem
Finished is not the same as ready to submit.
The build being done says nothing about whether the listing is right, whether the privacy labels match the binary, or whether a reviewer can reach the feature behind your login. Those are the things that send an app back, and none of them are visible from inside the code.
We have taken our own apps through this process. The rejections that come up are predictable, which is exactly why they are avoidable.
Doing it yourself
- ·Reading the review guidelines cold and guessing which apply to you
- ·Filling in privacy labels that must match what the app actually does
- ·Producing screenshots at every size Apple asks for
- ·Discovering account deletion is mandatory after you submit
- ·Decoding a rejection written in guideline numbers
- ·Doing all of it again for every update
Handing it to us
- ✓A pre-flight check against the guidelines that actually cause rejections
- ✓Privacy labels completed against what the app really does
- ✓Listing built: screenshots, description, keywords, categories
- ✓Submitted under your account, so the app stays yours
- ✓If Apple pushes back, we read the guideline and answer it
- ✓Available the same way for later releases, if you want us
What we handle
From a finished build to a live listing.
Pre-flight check
We go through the build against the guidelines that actually bite: minimum functionality, privacy labels, account deletion, permission prompts, and anything you are charging for.
Listing and assets
Screenshots at the sizes Apple requires, a description written to be read, categories, keywords and the privacy declarations that have to match the binary.
Submission
Submitted under your developer account with working demo credentials, so the reviewer can reach every part of the app without hunting.
Review and response
If it comes back, we read the guideline cited, fix the specific thing, and reply. You get told what happened rather than forwarded a rejection notice.
Later releases, if you want them
If you want us for later releases, it is the same process each time, so shipping an update is not a fresh research project. If you would rather handle them yourself, nothing about the setup stops you.
What you need
What to have ready.
A build that runs
Something we can install and use. It does not have to be finished to the last pixel, but it has to work.
A developer account
Your own Apple Developer account, so the app is genuinely yours. We will help you set one up if you do not have it.
A privacy policy
Live at a real URL, and accurate about what the app collects. Apple checks, and a mismatch is a rejection.
Questions
The things people ask first.
Who owns the app and the listing?
You do. We submit under your Apple Developer account, so the app, the listing and the customer relationship stay yours. If you ever stop working with us, nothing needs to move.
Do I need my own Apple Developer account?
Yes, and that is deliberate. Publishing under someone else's account means the app is not really yours. If you do not have one, we will walk you through setting it up, including the enrolment steps that trip people up.
What happens if Apple rejects it?
We handle it. We read the actual guideline cited, fix the specific thing, and reply in Resolution Center. A rejection is a normal part of the process rather than a failure, and planning for one round is realistic.
How long does review take?
Apple's review is usually days rather than weeks, but it is their queue and nobody can promise a date. What we can control is not adding a round to it by submitting something avoidable.
Do you handle Google Play as well?
Yes. The rules differ and Play has its own requirements around data safety declarations and target API levels, but the job is the same shape.
Is this included, or separate?
It is included when we build the app: getting it live is part of building it. If you have a build from somewhere else and need it published, that is standalone work and we will quote it once we have seen the app.
Get in touch
Got a build that needs to go live?
Tell us what you have and where it is stuck. If it is close, we will say so. If it needs work before it stands a chance, we will tell you that instead.