Getting your app into the stores

Yours. Apps should belong to your organisation's Apple and Google developer accounts. We help you enrol, then you invite us as team members. That way you are never locked out if we part ways.

• Organisation details and possibly a D-U-N-S number for verification
• App name, description and keywords
• Screenshots for different screen sizes
• A privacy policy web page
• Answers about what data the app collects
• Age rating questionnaire answers

We prepare drafts of all of this for you to approve.

It happens, and it is usually fixable. We read the reason, check the guideline, fix the app or add missing information, and reply to the reviewer clearly. Common causes include missing demo login details, privacy answers that do not match the app, or no way to delete an account.

Yes. We start with a quick check of the build, accounts and signing keys, then prepare the submission.

We use phased release on iPhone and staged rollout on Android, so a small share of users get the update first. If crash reports rise, we pause.