I help teams build products that make sense.
Good products aren't coherent by accident.
Preserving their intent means following them through evolving requirements, edge cases, and implementation.
Users shouldn't have to guess what's interactive.
Hover states and conventions answer questions implicitly before users even have to ask.
Empty states, validation errors, 404s, server failures.
Users don’t mind things going wrong. Much.
Waiting isn't the problem, uncertainty is. Good loading states acknowledge the user's time, communicate progress, and quietly disappear the moment they're no longer needed.
Users shouldn't have to guess what's interactive.
Hover states and conventions answer questions implicitly before users even have to ask.
Full-time UI/UX designer and front-end developer
Dense interfaces need type that can separate, prioritize, and stay readable under pressure.
A small amount of structure can make complex workflows feel safer, clearer, and less chaotic.
Independent work as UI/UX designer and front-end developer
Designing and building with accessibility in mind keeps small decisions from turning into expensive problems.
The requirements for apps close to government bodies actually make for pretty interesting challenges. Sometimes.
...but what if they were, anyway?
...and they can still have their entire content area clickable.
Links, cards, buttons, toggles, tabs — keyboard users need to see where they are.
Or: Why exactly is this link a button?
Sometimes accessibility work means making bad markup less bad without pretending you fixed the system.