Publishing
Launch is a step, not a finish line.
Publishing is where good software is most often let down: a rushed screenshot, a privacy label that no longer matches, a domain renewal nobody owned. We treat it as part of the product.
App store submissions
We prepare and check the store listing: name, subtitle, description, keywords, screenshots for required device sizes, preview text and support URL. We complete Apple’s privacy nutrition labels and Google Play’s data safety form by tracing what the app actually collects, including through third-party SDKs.
We write review notes that help reviewers: test credentials for a demonstration account, explanations of features that need a physical location or device, and any context that avoids a delay. If a review is rejected, we read the guideline cited, propose a fix and resubmit.
The checklist we argue through before every release
- Does the privacy label still match every SDK in the build?
- Do screenshots show the current interface, not last year’s?
- Are release notes written for users rather than developers?
- Is the minimum OS version a decision, or an accident?
- Does the support link lead somewhere a person reads?
- Has the account holder confirmed their developer programme membership is current?
Website launches
For sites we configure DNS, TLS, redirects from old addresses, a sitemap and robots file, a custom 404 page and basic security headers. We document who owns the domain, when it renews and how to restore from backup. Launch day ends with a short written note of what went live.
Content and publishing help
Where you publish written material such as guides, newsletters or documentation, we can set up the tooling and templates and advise on structure and plain English. We help you publish; we do not ghost-write opinions on your behalf.
Ask about a launch