Publishing

From build to the store, and the inbox after.

Release work is detailed and easy to underestimate. We take care of it and leave you a routine to follow.

What publishing involves

TaskWhat we doWhat you keep
AccountsSet up or tidy developer accounts in your organisation’s name.Ownership and billing
ListingTitle, description, keywords and screenshots in plain British English.Editable listing copy
PrivacyPrivacy labels and data-safety answers matched to the code.A record of what was declared
ReviewSubmission, reviewer notes and responses to any rejection.Correspondence history
RolloutPhased release where available; monitor crash reports.Release checklist
Web contentPage inventory, migration, redirects, accessibility of new content.Redirect map and style notes

Release notes people read

Release notes are a small chance to show care. We write them in plain language: what changed, why it matters, and what to do if something looks different. No "bug fixes and performance improvements" unless that is genuinely all.

Content we will not write

We do not author regulated financial, medical or legal content. We publish text your qualified people approve, and we format it so it reads well.