UI/UX DESIGN
Web and mobile product design by the person who can also build it, so every state, interaction, and layout has a practical route to production.
DESIGN THAT GETS BUILT
The usual design failure is not poor taste. It is a screen handed to a developer who has to quietly change it because an interaction is not feasible, a state was not considered, or the layout collapses with real content.
When design and build sit together, those gaps close early. Every screen is designed knowing how it will behave once it has data, errors, loading states, and a real person using it.
“A design is only complete when it works with the product around it.”
The operating principle
WHAT I DESIGN
The visual work follows the user flow and commercial goal, whether the product is for customers, a team, or an internal operation.
SaaS applications, dashboards, and platforms where people work rather than simply browse.
iOS and Android interfaces that respect platform conventions while staying one coherent product.
Components, tokens, and patterns that keep a product consistent as new screens are added.
Conversion-focused pages organised around a clear next action rather than only a visual mood.
Practical interface improvements that work within the constraints of the existing application.
PROCESS
Clarify who uses it, what they need to finish, and what currently gets in their way.
Set information architecture and user flows before visual design makes the wrong direction expensive.
Agree layouts and hierarchy while the work is still quick to adjust.
Create the visual system and every meaningful screen state in Figma.
Review clickable flows that behave like the product rather than static pages.
Implement the approved design directly, so the finished product does not become an approximation.
WHAT'S INCLUDED
The deliverables cover the decisions a developer needs in order to build without filling the gaps by guesswork.
The structure behind a product, not just polished screens.
Low-fidelity agreement on layout and journey before visual work begins.
Every relevant screen and state, including empty, loading, error, and long-content cases.
Deliberate desktop, tablet, and mobile behaviour rather than a design squeezed down at the end.
A scalable library where the product needs one, plus an interactive flow for review.
Figma files and clear documentation, fully owned by your team.
ACCESSIBILITY
Accessibility is design quality: sufficient contrast, targets that work on a phone, keyboard navigation, labelled forms, and states that do not rely on colour alone.
These choices make the product clearer for everyone. They are considered in the interface from the start, not sold as a compliance upgrade after the design is approved.
“A usable interface is a better interface for every user.”
COMMON QUESTIONS
The practical questions to answer before opening the first Figma file.
Yes. You receive Figma files, a clickable prototype, and handover documentation for your own developers.
Yes. I implement them faithfully and raise any issue that will not survive real content before work starts.
I use light-touch discovery and existing analytics. For a full research programme, I will recommend a specialist researcher.
Figma, with the working files transferred in full.
A focused product interface usually takes two to four weeks. Larger products and design systems take longer.
Yes. A targeted redesign within an existing architecture is often far more economical than a full rebuild.
Tell me what it does and who uses it. You will get a focused scope that can carry from design through to a working product.
