Service · Websites and web apps

UI/UX design

Companies usually come to design once they have a measurable problem: users who never finish a booking, staff spending ten minutes on a two-minute task, customers phoning to do something the website already allows. At that point new colours will not help; you need to see where people get stuck and why. Take a chain of physiotherapy clinics in Seville adding online appointments. Older patients cannot find the confirm button, and younger ones leave when asked to register. Those two findings, which come from watching six people use a prototype, are worth more than any internal opinion.

Figma
prototype and component library
Remote sessions
over video, no test lab needed
Severity report
problems ranked for fixing
WCAG 2.1 AA
settled at design stage

What falls within the scope of this service

Each design cycle produces concrete deliverables your team can use without Apply. These are the usual ones.

Pin down the details with one of our engineers

User research

Video interviews with people from your real audience, plus analysis of analytics and support queries.

Journey map

A step-by-step account of the main tasks: the user's goal, the steps, the information needed and where people drop out today.

Clickable prototype

Greyscale layouts turned into a Figma prototype, enough to test the journey before any coding.

Usability testing

Sessions with five to eight participants per profile, recorded with consent, and a report of issues ranked by severity.

Interface and design system

Final visual design covering colours, type, states, error messages and mobile layouts, organised as a component library.

Accessibility

Contrast, touch sizes, focus order and labels decided to WCAG 2.1 AA and, for public projects, UNE-EN 301549.

Support during development

Specifications, exported assets and reviews of the built product so the end result matches what was tested.

How the engagement unfolds, one stage at a time

One full cycle, from interviews to a tested prototype, normally takes a few weeks. Larger projects are split into several cycles, one per journey.

01

Watch before drawing

Video interviews with real users plus a review of analytics and support queries to locate where people get stuck.

02

Quick prototype

Greyscale layouts of the main journey turned into a clickable Figma prototype, without spending time on visual styling yet.

03

Test sessions

Five to eight people try to complete specific tasks on the prototype while we observe. Problems are fixed between one session and the next.

04

Final design and handover

Finished interface, a documented component library and a session with the developers to clear up questions before they code.

Users say one thing and do another. In a survey, almost everyone claims to prefer registering so their details are saved; in practice, many leave the moment a registration form appears. So major decisions are taken by watching people use a prototype, not by asking what they would prefer. An interview explains the why; a test session reveals the what.

Common questions

That depends on the number of journeys and test sessions. A single journey, such as a booking or sign-up, takes a few weeks; a whole application is split into cycles. We quote per cycle at €75 per hour + VAT, so you can stop after any of them.

No. Sessions run over video call: participants share their screen from their own computer or phone and use the prototype in their normal setting. It is easier for them and more realistic for the findings.

Five to eight people from the real audience are enough to find the main problems in a journey. Where profiles differ sharply, say patients and reception staff, a small group of each works best.

Yes, that is the usual set-up. We deliver a component library in Figma with specifications and hold sessions with your developers during implementation, so the final product matches what was tested.

It is. Contrast, touch target size, keyboard order and form labels are decided at design stage to WCAG 2.1 AA. On public sector projects we also apply UNE-EN 301549, the standard Real Decreto 1112/2018 refers to.

Test your interface before building it

Describe what needs designing and who will use it. We will suggest a method and the number of rounds it needs.

Hours
Monday to Friday, 9:00-18:00 Spanish time (CET), answers within a working day
Meetings
Video calls via Google Meet or Teams

This site only stores the cookies it needs to work and to remember your chosen city. No advertising or tracking cookies are set. See our privacy policy for the details.