Licences
Which licence fits you?
Applies to all licences: You purchase usage rights, not ownership. Raw files may not be resold, publicly shared or offered as your own product · no use as training material for AI models.
Simplified overview — legally binding are the full licence terms; in case of doubt, the terms of the larger licence category apply. Full licence terms
UI — User Interface Design
A UI you operate in ten seconds — and don't hate in ten years.
What the service covers
What UI design does for your product
The UI is the surface where users actually touch the product. It decides trust in the first seconds — and efficiency in daily use. Bad UI isn't „ugly", bad UI is „I can't find the button". Good UI today has to do three things at once: be operable in 10 seconds (for new users), be workable in 10 weeks without re-learning (for existing users), and not look dated in 10 years.
I design interfaces with a clear visual hierarchy, consistent component logic and a design system that grows with the product. Concretely: a design system (component library with states, variants, tokens), a visual language (typography, colour, spacing, shadow, motion), interaction patterns (hover, focus, loading, error, empty states) and concrete screen designs for the most important use cases. From the style guide to the pixel-ready handover to development.
Your product looks like a considered tool, not a pile of mismatched screens. Users find their way in ten seconds. Existing users still like it after ten months. And you can add new features without the UI falling apart — because the design system carries the extension.
How I approach UI design
- Design system foundations
Type system, colour system, spacing system, component architecture — built on brand strategy and UX specs. Tokens instead of hardcoded values, so changes stay easy.
- Component library
Produce the twelve to twenty most common UI components (buttons, inputs, cards, navigation, modals, etc.) — all states per component (default, hover, focus, disabled, error). Usage rules documented.
- Screen designs
Design the most important screens in detail — with real content, not „lorem ipsum". Edge cases considered (long texts, empty lists, error states). Responsive behaviour defined.
- Handover & dev support
Designs cleanly structured in Figma, components linked to variables, handover docs for development. Optional: sprint support so the design implementation doesn't drift in the code.
Frequently asked questions
Web design is mostly marketing-driven: a presence that grabs attention and drives conversion. UI is product-driven: an interface that works in daily use. Web design gets looked at once, UI gets used every day. That changes the requirement significantly — UI has to be clear in ten seconds AND efficient over ten weeks.
If the system is proven and components are cleanly documented, extending it is often enough rather than rebuilding. But if the system is just a collection of components without clear tokens, or if every new feature page gets reinterpreted from scratch, you're missing a UI language with rules. In the audit we work out what's sound and what isn't — before producing anything new.
With a clear component library in Figma, variables for tokens, all relevant states documented (hover, focus, loading, error, empty) and edge cases covered. Plus a handover workshop where designers and developers walk through the components together. Optional: sprint support in the first few weeks, so the design implementation doesn't drift in the code.
Ideally a designated designer or front-end developer on your team. In smaller teams, often the same person who does the UX/UI. The system doesn't need constant updating, but changes have to be coordinated — otherwise forks appear and the system falls apart. Clear ownership beats high frequency.
Web Design & Development
What else belongs to “Web Design & Development”.
Let’s talk.
A strategy call, straight in the calendar — pick a time.