Service
App Store and Google Play Publishing
Most rejections come from the same handful of causes. We clear them before you submit, and handle the fix if a review comes back anyway.
We publish apps to the App Store and Google Play. Developer accounts, store listings, screenshots, privacy declarations, review notes, the submission itself, and whatever the reviewer comes back with.
It is the step most app estimates leave out, and the one that turns a finished app into a delay. Each rejection costs another review cycle, typically one to three days.
What does publishing an app involve?
More than uploading a build.
- Developer accounts. The Apple Developer Program at $99 a year and Google Play at a one-off $25, set up under the right legal entity.
- Store listings. Metadata, descriptions and screenshots at every required device size.
- Privacy declarations. Apple's privacy labels and Google's data safety form, matched to what the app and every SDK inside it actually collect.
- Review access. Working demo credentials in the review notes, tested on a clean install, covering every role.
- Builds and signing. Provisioning, signing and the release builds themselves.
Why do apps get rejected?
The same six reasons, most of the time. These are the ones we see most often:
- No way to delete an account from inside the app.
- A login screen with no way through for the reviewer.
- A wrapped website that fails the minimum functionality rule, Guideline 4.2.
- Payments routed outside in-app purchase, Guideline 3.1.1.
- User-generated content with no moderation tools.
- Privacy labels that do not match the SDKs in the binary.
What do you check before submitting?
A fixed pre-submission audit, run against every build. Do the privacy labels match what the app collects. Does every permission request explain itself. Is there placeholder text or test data in a screenshot. Is login hiding content the reviewer needs to see. Is a debug flag still set.
The point is to find these before the review clock starts rather than after.
What happens if the app is rejected anyway?
We read the rejection, fix the cause and resubmit. Reviewers work from a published set of guidelines, so a rejection nearly always names something specific. Where it is ambiguous, we reply through App Review rather than guessing.
Do you handle updates after the first release?
Yes. Every update goes through review too, and both stores change their requirements every year. An app nobody updates eventually stops being installable.
What does app publishing cost?
It is quoted after a short call, because the work depends on the app: how many platforms, whether the accounts already exist, and whether it uses payments, sign-in or user content, which are the areas reviewers look at most closely.
J
Get your app through review
A free call. Tell us where the app is, and we come back within 24 hours with a plan and a quote.