Interface design judged on how it is used, not how it presents
A mockup that wins approval and then confuses users has failed. UI and UX work here covers wireframing, prototyping and interface design for both web and mobile, with each platform's own conventions respected rather than one generic layout stretched across both. Designs hand off cleanly into development because the same person builds them.
What this covers
UI/UX Design
Interface design for websites and apps focused on how someone actually uses the product, not just how it looks in a mockup.
- Wireframing & prototyping
- Interface design
- Usability & accessibility
Web Design
Visual design for websites, built to hand off cleanly into development rather than existing as a disconnected mockup.
- Landing page design
- Design systems
- Responsive layouts
Mobile App Design
App interface design for iOS and Android, designed around each platform's own conventions rather than a single generic layout.
- App UI design
- Design systems for apps
- App store visuals
How this works in practice
Design that survives contact with development
A lot of interface design falls apart at handover. It looks right in the design file and then breaks in the browser, because the layout assumed one text length, the states were never drawn, and nobody decided what happens on a 360px screen.
Because the same person builds it afterwards, the design is made against what the browser will actually do. Long names, empty states, error states and loading states are decided during design rather than improvised during development, which is where most of the visual drift between a mockup and a live site comes from.
Phone first, properly
Most traffic arrives on a phone, and most designs are still drawn at desktop width and squeezed down afterwards. The result is a hero cropped so the product is out of frame, a primary button below the fold, and a form that needs two hands.
Designing at the small size first forces the real decisions: what the one message is, which single action matters, and what can be cut. The desktop layout is then an expansion of something already proven to work in the harder constraint rather than a compression of something that was never tested in it.
What you actually receive
Wireframes for structure, then interface design in Figma with the components, spacing scale and type scale defined so the design can be extended without guessing. Where the work will keep growing, that becomes a small design system rather than a set of one-off screens.
Prototypes are used for anything with real interaction, so a flow can be clicked through and corrected before it is expensive to change. Testing with real users is part of the work where the budget allows, because how something is actually used is more useful than any opinion about it, including mine.
Accessibility is part of the design, not a retrofit
Contrast, focus states, target sizes and reading order are decided during design because retrofitting them afterwards means reopening layouts that were signed off months earlier. It is far cheaper as a design constraint than as a remediation project.
In practice that means text contrast checked against WCAG rather than eyeballed, interactive elements that are reachable and visible by keyboard, and motion that respects a visitor's reduced-motion setting. That is good practice everywhere, and it matters commercially if you sell to organisations that ask about accessibility during procurement.
Frequently asked
Do you deliver design systems or one-off screens?
Design systems where the product will keep growing, single screens where it will not. Building a system for a one-page campaign site is wasted effort.
Is accessibility part of this?
Usability and accessibility are considered as part of the design rather than retrofitted, which is considerably cheaper than fixing it later.
What is the difference between UI design and UX design?
UX is how it works, UI is how it looks. UX decides what the screens are, what order they come in and what a person is trying to get done. UI is the type, colour, spacing and components that make it feel like something. Most projects need both, and separating them across two suppliers is where designs usually fall apart.
Is web design the same as UI/UX design?
They overlap but are not identical. Web design usually means the visual design of a marketing site. UI/UX covers that plus product interfaces, app screens, flows and states. If you need a site that looks good, that is web design. If you need something people have to use repeatedly, that is UI/UX.
Do you design mobile apps as well as websites?
Yes, and I design them phone first rather than shrinking a desktop layout. That matters: most designs that break on a phone were drawn at desktop width and squeezed afterwards, which is how you end up with the main action below the fold.
Can you redesign an existing site without rebuilding it?
Often yes, and it is usually the cheaper call. If the structure is sound, reworking the type, spacing, hierarchy and key pages gets most of the benefit for a fraction of a rebuild. I will look at what you have and tell you which one you actually need.
Do I get the Figma files?
Yes, shared with you and yours to keep, with components and styles named so another designer or developer can pick them up without a handover call. Withholding source files to keep a client dependent is common and not something I do.
Do you design in Figma?
Yes. Files are shared with you and stay accessible, with components and styles named so another designer or developer can pick them up without a handover call.
Can you design without building it?
Yes, design-only engagements are common. You get files built to be handed to a developer, with states and breakpoints specified rather than left implied, which is usually where design-only handovers go wrong.
How many revision rounds are included?
Two rounds of structured feedback at each stage, which is enough for genuine iteration without turning into an open-ended loop. Anything beyond that is quoted, and I will say so before the work happens rather than after.
Still not sure if this is what you need?
Send it here and it comes straight to me. You will get a straight answer about whether I am the right fit, including when the answer is no.
Have a project in mind? Let's start it.
Whether it's a paid campaign, a website or app, or ongoing design and social support — tell me what you need and I'll get back to you with next steps.