W4 / Publishing
Launch as a planned milestone.
Publishing tasks have lead times and dependencies. We schedule them from the first week so launch day holds no surprises.
| Item | Start by | Why |
|---|---|---|
| Developer accounts in your name | Week 1 | Organisation verification can take time |
| Privacy policy and data map | Week 3 | Needed for store privacy disclosures |
| Store listing copy and screenshots | Two increments before launch | Screens must reflect the real product |
| Reviewer demonstration account | Gate C | Prevents rejections for inaccessible features |
| Domain, DNS and certificates | Week 2 for websites | DNS changes need time to settle |
| Rollback plan | Gate C | Every launch needs a way back |
App stores
We prepare App Store Connect and Google Play Console listings, complete privacy and data safety declarations by tracing what each library collects, write reviewer notes and manage resubmission if a review raises an issue.
Websites
DNS, TLS certificates, redirects from old URLs, sitemap, robots file, error pages, security headers and backups. We document ownership, renewal dates and restore steps in the handover.
Publishing written content
Where your project includes guides, documentation or regular updates, we set up publishing workflows and templates so your team can publish confidently. We support publishing; we do not write opinions on your behalf.
Plan a launch