Learn UI/UX design online
Design
3 topics under this pillar
Design is the pillar that covers how software looks, how it moves, and how a person decides whether to keep using it after the first five seconds. The courses under this hub run from pure UI/UX fundamentals — typography, colour, layout, design systems — through motion and web animation, into the frontend implementation skills that designers increasingly need to stay close to production.
The 2026 picture for product design is less crowded than the doom-loop on Twitter suggests, but the bar has moved. Most companies hiring designers now expect comfort with Figma plus at least a passing familiarity with the design tokens and component libraries the engineering team uses — Tailwind, Material, shadcn/ui, a brand-specific system. The "design engineer" hybrid role has gone from rare to common, especially at startups under 100 people, which is why this pillar deliberately surfaces the Frontend topic alongside the pure design topics: the line between the two roles is thinning, and the highest-leverage designers ship code as well as Figma frames.
What you'll find under this pillar
- UI/UX design — interface design, design systems, Figma, prototyping, usability heuristics
- Web animations — CSS transitions, Framer Motion, GSAP, scroll-driven animation, interaction patterns
- Frontend — the implementation side of the wall: HTML, CSS, modern component frameworks, accessibility
- Design system courses — building, documenting, and shipping a reusable component library
- Prototyping and handoff — the daily craft of designing in a way engineers can actually build
The pillar is structured around the way design careers actually compound. Most working designers start in pure UI/UX — Figma, layouts, components, a handful of finished case studies — then either deepen into design systems and engineering collaboration, or pick up motion and interaction as a specialty. The featured rail surfaces top-rated picks across all three so you can see the shape of the work before committing to a track. If you already know which corner you want — pure visual, motion-heavy, or design-engineer hybrid — jump directly to that topic.
Design roles hire at every size of company but the work looks very different at each end. At early-stage startups one designer covers research, UI, brand, and sometimes the implementation. At larger product companies the role splits — product designer, design-systems designer, UX researcher, design engineer, motion designer — and the pillar's topics map onto those specialisations cleanly. If you're starting from zero, the order to follow is: UI/UX fundamentals first, one finished portfolio case study, then animation or frontend as a second specialty depending on where you want to angle.
Browse by topic (3)
Featured design courses
Frequently asked questions
- Is UI/UX design saturated in 2026?
- The entry-level market is genuinely competitive, especially for purely visual roles with no engineering or research overlap. The middle of the market — designers who can run a small research session, contribute to a design system, and read enough code to handoff cleanly — is still healthy and growing. The honest framing is that the pure-visual UI designer who only pushes pixels in Figma is the saturated end. The designer who can also ship a small frontend change, or who specialises in animation, or who carries the research side, is where the open roles sit.
- Do I need a design degree to get hired?
- No. The industry has hired on portfolio over credential for at least a decade, and the trend has continued. What companies look for is three or four finished case studies that show how you think — problem framing, constraints, alternatives considered, the final solution and why — plus a clean visual standard. A degree helps mostly because it forces those case studies to exist. A self-taught designer with the same body of work gets the same interviews, and often faster because the portfolio is more current.
- Should designers learn to code in 2026?
- Enough to be dangerous, yes. You don't need to ship production code, but you should be able to clone a frontend repo, make a small CSS or component change, and open a pull request. The design-engineer role has gone from niche to common at startups, and even when the job title stays product designer the people who can read the codebase tend to ship better-implemented designs. The Frontend topic on this pillar is the practical starting point — HTML, CSS, one component framework, and a working dev setup.
- Figma, Sketch, Adobe XD, or something newer?
- Figma. The market has consolidated around it almost entirely — most companies hiring in 2026 list it as a requirement, the AI-assisted plugins are far ahead of competitors, and the collaboration model is what the rest of the industry copies. Sketch survives mostly in macOS-heavy agencies. Adobe XD is in maintenance mode. Newer tools (Penpot, Framer, Rive) are worth knowing as supplements — Framer especially if you focus on motion — but Figma is the one to learn first and the one to put on your CV.
- How long does it take to build a hireable design portfolio?
- Three to six months of focused work to produce four solid case studies, assuming you already have basic visual taste. Each case study should show a problem statement, the constraints, two or three alternatives you considered, the chosen design, and ideally a real or simulated outcome. Quantity beyond four hurts more than it helps — recruiters skim the first three pieces. Most candidates underestimate how much time the writing takes; the visual work is often the easy half.
- What's the difference between UI design and UX design?
- UI design is the surface — visual hierarchy, typography, colour, component design, the craft of making a screen look right. UX design is the underlying decision-making — what problem are we solving, who for, what flow makes that easiest, how do we know it worked. In practice most working product designers do both, and almost every course on this pillar covers both as a single discipline. The split matters more in larger organisations where the roles separate, and on academic course pages where the terms are still taught as distinct fields.