Chapter 7 of 11
Getting through the store doors
Building an app is one adventure; getting it accepted, listed and updated is another. We help with both — including apps someone else built.
Accounts set up properly
Developer accounts should belong to your organisation, not to a freelancer's personal login. We walk you through Apple's and Google's enrolment steps, including the D-U-N-S number Apple asks organisations for, and set up team roles so nobody is locked out if a person leaves.
Listings that explain themselves
Store pages are tiny shop windows. We help you write a clear name and description, prepare screenshots for every required device size and fill in the privacy and data-safety forms accurately — mismatches between what an app does and what its listing claims are a common reason for rejection.
When review says no
Rejections are normal and usually fixable. We read the reviewer's notes, explain what they mean in everyday language, make or suggest the changes and write a polite, specific reply through the resolution centre. We can't promise approval — nobody honestly can — but we can make the conversation much less baffling.
Release trains, not release panics
Phased roll-outs, staged percentages, test tracks and release notes. We'll help you set a calm rhythm for updates so that a small fix doesn't turn into a weekend emergency.
Pre-flight checklist
Tick off what's ready. The list stays on this page only — nothing is saved or sent.
0 of 10 ready.
Questions people ask
Can you publish an app you didn't build?
Yes, provided we can access the source and the accounts. We'll check the build first and tell you if anything is likely to trip review.
Do you publish under your own account?
No. Apps should be published under your organisation's own developer accounts so you stay in control.
Is there a guaranteed approval time?
No. Review times are set by Apple and Google and vary. We'll plan launches with sensible buffers.