SERVICES — UX/UI DESIGN
UX/UI design in Turin, Italy
We design the experience before writing a line of code: understanding who will use the product and letting them try a prototype costs far less than rebuilding the software later.
Empatix designs the user experience (UX) and the interface (UI) of web apps, business software and digital products. Here design is not a separate phase, handed over and forgotten: it grows together with development, in Turin, and knows its constraints.
Why start from design
The most expensive way to find out a screen does not work is after building it. A prototype changes in an afternoon; software already in use changes in weeks, and by then users have learned to work around it.
Signs the problem is design, not technology:
- people avoid the software and go back to email and spreadsheets;
- every new colleague needs days of shadowing to use it;
- the same support requests keep coming back, identical;
- the product has every feature, but customers cannot find them.
What we do
Research. We talk to the people who will use the product and watch them work. Which tasks they perform, how often, in what hurry, on which device. This is where you learn what is really needed.
Architecture and flows. Before the screens, the paths: which steps lead to a result, what can be removed, what must be within reach.
Clickable prototypes. In days, not months, you have something you can touch and let people try. Decisions are made on a concrete object, not on a description.
Interface. Final screens, states, error messages, mobile version. Every detail the user will meet, not just the ideal case.
Design system. Documented components, colours, typography and usage rules: the interface stays consistent even as the product grows and more people work on it.
Validation. Tests with real users on the prototype and, after launch, measurement of what actually happens.
Design that can be built
The people designing here know how it will be developed. Every screen accounts for real data, loading times, edge cases, the length of translated text. The result is a design that reaches production the way it was approved, and this holds for business software as much as for an interactive website.
Accessibility
We design to the WCAG guidelines: readable contrast, controls that are large enough, keyboard navigation, a structure screen readers can understand, respect for people who prefer less motion. It is not a final add-on: decided at the start it costs almost nothing, added later it costs a lot.
Tools
We work in Figma for prototypes and design systems. Designed components become components in code (React or Vue), so design and product do not drift apart over time.
Cost and timing
Cost depends on the number of flows and screens and on how much research is needed. You can start small: an analysis of an existing product with priorities for action, or a prototype of the main flow only. After a first conversation you receive an estimate split into phases.
How we work
PHASE 01
Listen
We understand the problem before proposing a solution. Workshops, questions, zero pointless slides.
Interviews and observation of the people using the product: tasks, frequency, obstacles.
PHASE 02
Design
Clickable prototypes in days, not months. You decide on something you can actually touch.
Flows, clickable prototypes and tests with real users before the final screens.
PHASE 03
Build
Short sprints, frequent releases. Watch the product grow week after week.
The design system becomes components in code; we work alongside developers until launch.
PHASE 04
Evolve
We don't vanish after launch. We measure, improve and stay by your side.
After launch we look at usage data and fix the screens that cause friction.
Frequently asked questions
What is the difference between UX and UI design?
UX (user experience) is about how the product works: which steps lead to a result, what the user finds and in what order. UI (user interface) is about how it looks: screens, colours, typography, components. They are designed together, because a beautiful interface on the wrong flow is still hard to use.
Do you offer design only, without development?
Yes. We can hand over research, prototype and design system to an in-house or external development team. Because we design alongside people who build software every day, what we deliver can be implemented as it is, with no surprises along the way.
Can we redesign existing software without rebuilding it from scratch?
Often, yes. We start from an analysis of what slows users down today and work on the screens that weigh the most, one at a time. Rewriting everything is the last option, not the first.
How do you involve users?
Through interviews, observation of real work and prototype testing: a few well-chosen people are enough to surface most problems before they turn into code.
Is accessibility included?
Yes, it is part of the project and not an add-on: contrast, control sizes, keyboard navigation and screen reader labels follow the WCAG guidelines from the very first screens.
Last updated:
