A consistent interface does not come from talent, it comes from a system: a small set of rules about typography, colour and spacing, applied everywhere. This course teaches how to build that system and work inside it.
Figma is the working tool, and we cover the parts that genuinely matter: auto layout, components, variants and variables. But the subject is not the software. It is how to design components that survive as the product grows, and how to hand them to developers without a hundred clarification questions.
Accessibility and dark mode are not a bonus module at the end: they are criteria that shape decisions from day one, because retrofitting them costs far more.
Modular scales, hierarchy, grids and vertical rhythm. The rules that make an interface legible before they make it attractive.
Building a library of reusable components, with naming and structure that hold up as the team grows.
The features that save hours: auto layout for components that adapt, variants for states, variables for themes and tokens.
Contrast ratios, target sizes, visible focus and hierarchy. Requirements that are increasingly legally binding, not optional.
What a delivered file has to contain: states, responsive behaviour, edge cases. Everything that otherwise gets invented by someone else.
Setting colours as semantic tokens rather than fixed values, so multiple themes do not mean redoing the work.
No course is a fixed package. Duration, angle and depth are agreed around the objectives of the people taking part, and topics from different courses can be combined into a single programme. I work with corporate groups and with one person alone: tell me what you need and we will build the programme.
Request informationNo, the free tier covers the entire programme.
Not necessarily, but UX then UI is the sequence that gives the best results. They can also be combined into a single tailored programme.
In corporate courses, yes: it is the most frequent use case and the most useful, because the output stays with the team.
It has a dedicated module and is applied as a criterion across all exercises. We cover the WCAG requirements relevant to interface work.