Writing
Notes from the studio on process, design and engineering. Written by the people doing the work, not a content team. A new post most fortnights.
Why we start engineering in week five
Waiting for every screen to be finished before writing code is how projects slip. Here's how the overlap actually works.
The handoff problem, and how we avoid it
Most products get worse the moment a designer hands over a file. We stopped handing over.
React Native in 2026: when we still go native
One codebase for both stores is the default. These are the four cases where we don't.
Pricing pages are product design
The upgrade flow is the most-read screen you'll ever ship. Treat it like one.
What a two-week design sprint actually produces
A prototype, five user sessions, and a build estimate you can take to your board.
Fast marketing sites without a build team
How we set up Framer so a two-person marketing team ships pages weekly.
Thirty days after launch: what breaks
The bugs that only real users find, and why we keep the team on for a month.
The SEO work that's just good engineering
Most of what moves rankings on a new site is markup, speed and structure. Here's the checklist we ship with.
One email a fortnight.
New posts, plus the occasional note on what we're building. No launches, no drip campaigns, unsubscribe in one click.