/publishing
Release
engineering.
Shipping to the stores is a pipeline with gates you do not control. We make each gate predictable.
- 01
Accounts
Apple Developer Program and Google Play Console accounts registered to your organisation, including D-U-N-S and identity verification where required. We join as invited users with scoped permissions.
- 02
Signing
Certificates, provisioning profiles and upload keys generated, stored securely and documented so a future team can release without starting over.
- 03
Listing
Name, subtitle, descriptions, keywords, categories, age rating questionnaire and screenshots for each required device class. Copy is accurate and avoids claims the app cannot support.
- 04
Disclosure
App Store privacy details and Google Play data safety form completed from an audit of the app’s actual behaviour, including SDKs. Mismatches with your privacy policy are flagged for you to resolve.
- 05
Review
Reviewer notes, demo credentials and instructions for reaching every feature. On rejection we interpret the cited guideline, propose a fix or a reasoned response and resubmit.
- 06
Roll-out
Testing tracks, phased release, release notes and semantic versioning. A release runbook so each update follows the same steps.
What we cannot promise
Approval decisions belong to Apple and Google. Review times vary and policies change. We will not help publish apps designed to mislead users or evade store rules, and we will tell you plainly if we think a feature is likely to be rejected.
Already in the stores?
We can take over release duties for an existing app: audit the signing setup, tidy listings, bring disclosures up to date and establish a release runbook. Usually the first job is recovering lost credentials or documenting who holds which keys.