UI/UX & PRODUCT DESIGN
Good design that doesn't get built right isn't good design. It's a mockup.
I design interfaces and then build them myself, so nothing gets lost between the Figma file and the browser. That's useful on a marketing site. On a product it matters even more, because every screen has empty, loading and error states, and the developer is usually the one who finds out about them.
"If the developer has to guess, the design isn't finished."
How I Design and Build
UX Research & Strategy
Before I open Figma, I want to know who uses the product and what they're trying to get done. That might mean five user interviews, a dig through your analytics, or an afternoon reading support tickets. The goal is to find where people get stuck.
Interface Design
This is where the product takes shape, screen by screen and state by state. I design the empty, loading and error states along with the happy path everyone designs first, and I prototype the tricky flows so you can click through them before anyone writes code.
Frontend Development
I build what I design in HTML, CSS, Sass and React, on Bootstrap, MUI or Tailwind depending on what your team already uses. It's accessible from the start, responsive, and tested across browsers.
Design Systems & Handoff
A design system only earns its keep if developers use it instead of working around it. I set up tokens, components and documentation that match the code, so the Figma library and the production UI stay the same thing.
Selected Related Work
Have a product that needs designing and building?
Send me what you have, even if it's a sketch or a broken staging link.
All Services
Have a product that needs designing and building?
Send me what you have, even if it's a sketch or a broken staging link.
Direct line
