The launch kit.
Practical resources we use ourselves. Filter by topic; every link goes to a real, public source.
Reading list
- App Store Review GuidelinesApple's rules for what can be published.
- Google Play Data safetyHow to complete the Data safety form.
- Human Interface GuidelinesApple's platform design guidance.
- Material Design 3Google's design system for Android.
- web.dev: Learn performancePractical web performance course.
- MDN Web DocsThe reference for web technologies.
- WCAG 2.2 quick referenceAccessibility success criteria.
- GOV.UK: user researchClear guidance on researching with users.
Launch brief template
Copy these headings into a document before you contact any supplier. Half a page under each is plenty.
- The problem, in one paragraph
- Who has it, and how often
- What "launched" means for you
- What must not change
- Known constraints: budget range, dates, systems
- Who decides, and who is consulted
Common questions from first-time founders
Should we build an MVP?
Usually, yes: the smallest version that real users can get value from. It must still be reliable and accessible; minimum does not mean broken.
What ongoing costs should we expect?
Developer accounts, hosting, domains, third-party services and maintenance time. We list these in every proposal.