7 pieces
Writing
Notes on product design, interface decisions and frontend architecture, written from work we have actually done. No invented metrics, no case-study numbers we cannot show the method for.
What "production-ready frontend" means in practice
The gap between an approved design and a shippable frontend is mostly made of states nobody drew. That gap is where projects lose their last three weeks.
FrontendHandoffEngineering practiceDesigning a mobile app that never shipped, and why that is still useful
Most portfolios contain unshipped work and are quietly vague about which pieces those are. Being precise about it is what makes the rest of the page believable.
Concept workMobilePortfolioDesigning a payments flow people finish
A payment flow is a form someone fills in while slightly anxious, on a phone, with a card in their other hand. Design for that person and most of the rest follows.
PaymentsCheckoutProduct UXWhat makes a marketplace feel trustworthy
A marketplace asks two strangers to trust each other, and offers itself as the reason they should. That is an interface problem far more than a branding one.
MarketplacesProduct UXTrustReact or Next.js for a product marketing site
The choice is usually framed as a framework question. It is really a question about what your pages contain before any JavaScript runs.
ReactNext.jsFrontend architectureWhy TypeScript pays off before a team gets large
Types are treated as a tax that big teams pay. The mechanism that makes them useful is strongest on small teams changing their minds often.
TypeScriptEngineering practiceConcept, published, and client work: how to read a design portfolio
Most portfolios use one word for three different claims. Here is what each label on this site means, and what it deliberately does not say.
PortfolioCase studiesStudio practice