UX & UI for apps & web
Interfaces should feel confident and quiet — hierarchy that reads at a glance, motion that explains state, and accessibility that is not bolted on the week before store submission.
What you get
Flows that respect thumbs, desks, and intermittent networks; typography and spacing that scale from compact Android surfaces to marketing pages; and components you can hand to engineering without a translation layer. I bias toward restraint — elevation through clarity, not decoration.
How the work runs
We align on jobs-to-be-done and edge cases early. Wireframes or low-fi prototypes when ambiguity is high; high-fi when the risk is polish and brand fit. I document states — loading, empty, error, offline — because those are where products earn trust, especially in hill towns and metros alike.
Android, web, and the gap between
Much of my recent UI work sits on Android (see MoCabs) and on the web (studios, commerce, civic tools). The same rhythm applies: predictable navigation, honest feedback, and patterns that do not fight the platform.
Accessibility and performance
Contrast, focus order, and touch targets are part of the default brief — not a separate line item. Where it matters, we keep motion purposeful and assets disciplined so first paint and scroll stay credible on mid-range devices and slower links.
A good fit when
You are shipping or refreshing a product customers actually tap through, not a one-off poster site. If you need pure brand mythology without screens, a specialist studio may serve you better — if you need UI that ships, we should talk.
“The UI finally matched how calm the operations side needed to feel. Users stopped asking where to tap — that sounds small until you see support volume drop.”
Other ways I can help
Product architecture · full-stack build