Publishing
The last bar is still music
Shipping is a craft of its own. We help teams publish apps and websites calmly, repeatedly and with a route back if something goes wrong.
Release checklist we work through
| Stage | What happens | Who signs off |
|---|---|---|
| Freeze | Feature work stops on the release branch; only fixes enter. | Lead developer |
| Verify | Automated suite, manual device pass, accessibility spot checks. | Developer and reviewer |
| Describe | Release notes in plain English; store text and screenshots updated. | You, as product owner |
| Submit | Store submissions or production deploy behind a staged rollout. | Lead developer |
| Watch | Error logs and feedback channels monitored during working hours. | Support rota |
| Rollback | Previous build ready; the route back is tested, not assumed. | Lead developer |
App stores
We prepare listings, privacy declarations, screenshots and review notes, and handle back-and-forth with reviewers. Store rules change, so we check the current guidelines at every submission rather than relying on memory.
Web publishing
Deployment pipelines with preview links for every change, so you approve what you have actually seen. For simpler sites on shared hosting we document a safe manual process.
Documentation
Handover documents cover setup, deployment, credentials management (without containing credentials), known issues and a glossary.
Content publishing
For content-heavy products we set up editorial workflows, preview environments and image handling so editors publish without asking a developer.