Our ServicesDesign
Marketing pages have to persuade once; product interfaces have to be used, sometimes every working day. We design the flows, screens and states behind web applications, dashboards, booking systems and content-heavy sites. That includes the Bubble.io products we have shipped and the web admin panels running behind live mobile apps.
Included as standard on every engagement — not an upsell list.
We list every role that touches the product and what each of them is trying to finish, then map the shortest honest route through it. Screens then exist because a real task needs them, not because a competitor happens to have one.
Navigation, hierarchy, naming and grouping are decided before pixels. On admin panels and marketplaces this is most of the work: getting the object model and the labels right is what stops staff guessing where anything lives.
Not only the happy path. Empty states, loading, partial data, permission errors, validation failures and long-content overflow all get drawn, because those are precisely the screens that make a product feel unfinished when nobody designed them.
Buttons, inputs, selects, tables, modals, tabs, toasts and cards are designed once with all their states, then assembled into screens. Because developers build from components, the twentieth screen costs a fraction of the first one.
A clickable prototype you can put in front of actual users, staff or investors before a line of code exists. Changing a flow in Figma takes an afternoon; changing the same flow after it is built takes a sprint and a budget conversation.
Keyboard order, visible focus, target sizes, contrast on data-dense screens, and form errors that say what to fix rather than that something went wrong. Applied through the component library so it holds across every screen automatically.
Stage by stage, with the approval points marked. UI/UX Design follows the same rhythm on every project.
We work through the purpose, the user roles, the permissions and the data the product holds. On Bubble.io and web-app work this doubles as a first pass at the data model, because interface problems are usually structure problems wearing a costume.
We diagram each core journey end to end and agree the navigation model. You approve flows before screens, which is the cheapest possible place to discover a step nobody actually needed.
Greyscale screens for every route, including the awkward states. We annotate the rules alongside them — what happens on save, what an administrator sees that a member does not — so the build has answers rather than assumptions.
We design the component library, then compose the screens from it at desktop and mobile widths. Data tables, filters and long forms get particular attention, because that is where product interfaces usually fail first.
We assemble the clickable prototype, walk stakeholders or users through it, and fold what we learn back into the screens before anything is handed to development.
The concrete artefacts handed over at the end — files, access and documentation you keep.
If two or three of these sound like your situation, this is the right place to start.
Standard, portable tooling. The licences, accounts and source stay in your name, so nothing here is a reason you cannot leave.
Live projects where this work did the heavy lifting:
Work that usually runs alongside this one:
What we have written about this, in more depth than a service page allows:
The questions we get asked most about UI/UX Design.
Send us the brief — or just the problem. You will get a written scope, a timeline and a fixed price, usually within one working day.
