Designing in the browser, not in Figma.
Why our team retired the static mock six months ago — and what we replaced it with. The case for designing live, in code, against real data.
Essays, deep-dives and case notes from the team — what we're learning about design systems, AI products, and the craft of shipping.
After deploying retrieval pipelines for fourteen products in 2025, a pattern emerged: most AI features die not from bad models but from bad surfaces. Here's our playbook for shipping copilots users actually open — five principles, eight anti-patterns, and the eval loop that saved our biggest launch.
Why our team retired the static mock six months ago — and what we replaced it with. The case for designing live, in code, against real data.
A practical, boring system for catching regressions before users do. Fixtures, scorecards, gold sets, and the meeting we run every Friday.
The four CSS techniques we use to make stacks, panels, and reveals feel buttery — without scroll-jacking or scroll-jank.
Five years of design systems taught us this: tokens need a roadmap, a release notes channel, and somebody whose job it is to ship them.
A behind-the-scenes look at our biggest 2025 launch: the brief, the timeline, the moments that nearly broke us, the call that saved it.
One typographic choice — and the eight reasons it shows up in every Foxmen brief. Yes, including this one.
RAG is mostly plumbing. Here's our hard-won checklist for a retrieval stack you can actually leave alone for a quarter.
Why our 38 active client codebases live in one repo, what it cost to get there, and the day it paid for itself ten times over.
From Figma to App Store, with AI-generated itineraries and offline maps. A complete project breakdown — scope, stack, sprint cadence.