Interfaces people understand instantly

Before we pick a colour, we work out who uses the interface and what that person is trying to achieve. We look at how your customers or staff work today, where they get stuck and which steps can be merged. Out of that come user flows and an information architecture - the decision about what belongs on which screen and what deliberately does not.

This phase saves the most money. Reorganising a structure in a draft is trivial - in a finished application the same change ripples through the whole build. That is why we start with greyscale wireframes: no logo, no imagery, just content, hierarchy and sequence.

From the wireframes we build a prototype you can actually operate on your phone or desktop. You click through the checkout, the form or the dashboard instead of imagining a written description. The gap between "that is what I meant" and "that is how I understood it" all but disappears.

On request we put the same prototype in front of five to eight people from your target group and give them a concrete task. What they do tells you more than any round of opinions inside the team. You get the observations summarised, and we rework the places that genuinely cause trouble. None of it needs a testing lab: sessions run wherever your target group can be reached - at your premises, at our office in Neuhausen am Rheinfall or over video.

We do not hand over a collection of pretty pictures, we hand over a system: defined spacing, type sizes, colours as tokens, buttons, form fields, tables and messages - each with every state, including hover, focus, error, loading and empty. Those states are exactly what classic mockups leave out, and exactly what eats development time later.

The system is built so developers can implement it directly, and so the twentieth screen still looks like the first - even when it is added a year later. We hand over the files including the rights, so you are never tied to us.

We design with sufficient contrast, readable type sizes, touch targets big enough to hit and full keyboard operation. We use the WCAG level AA criteria as our benchmark. That helps not only people with impairments but everyone - in bright sunlight, one-handed on a train platform, or on an old screen.

Language is part of it: clear labels, error messages people can act on, buttons that say what they do. A form field that explains what went wrong is worth more than any animation.