CAREER PATH · UI DESIGN
We explain new ideas in plain language, practise repeatedly and build useful projects. No programming background is required; curiosity about how people use interfaces is enough.
Understand → sketch → prototype → test → improveYour first useful result is only a few careful steps away.EXPLORE BEFORE YOU START
Learn typography, colour, layout, Figma, research, usability, accessible interaction, design systems and handoff.
No programming background is required; curiosity about how people use interfaces is enough.
You can read this outline without signing in or completing onboarding. Start with the welcome screen above when you are ready to practise. Use a current browser; a keyboard and larger screen can make longer coding tasks easier, but the lesson interface also adapts to phones.
The in-page coding tasks use pattern checks to confirm required pieces. They do not replace installing the relevant framework, design application, Python environment or hosted service for full execution. Each section includes guided practice, projects and a ten-question exam.
Read an explanation, study the example, try the task and review feedback. Keep your own project files and test them in their intended environment. Completing an activity or a course certificate is not an accredited qualification or a guarantee of employment.
Expand a section to read its chapters and projects. This is the actual course curriculum, not a separate list of promised future topics.
Guide attention with purpose, hierarchy and consistent feedback.
Section outcome: Critique and redesign a confusing interface with evidence.
Begin with the task a person must complete rather than decoration.
Use position, size, weight and spacing to communicate order.
Rebuild and vary the hierarchy and scanning example until every important piece feels familiar.
Make possible actions and system responses understandable.
Reuse patterns so learners do not repeatedly solve the same interaction.
Rebuild and vary the consistency and conventions example until every important piece feels familiar.
Redesign one crowded screen and explain every removed or emphasised element.
Design a complete small workflow around one important user outcome.
Use type and colour to communicate without excluding readers.
Section outcome: Create a readable type and colour system with documented contrast.
Choose a small type hierarchy based on reading tasks.
Support comfortable reading with line height, measure and paragraph spacing.
Rebuild and vary the spacing and line length example until every important piece feels familiar.
Use contrast and additional cues instead of colour alone.
Write concise labels and instructions that match user vocabulary.
Rebuild and vary the content language example until every important piece feels familiar.
Build a small palette and reject combinations that fail target contrast.
Create typography, colour, labels and examples for a service product.
Design flexible structures for content, touch and varied screens.
Section outcome: Prototype a flow across phone, tablet and desktop without losing task order.
Create repeatable alignment and spacing relationships.
Decide what must remain visible and what may reflow as space changes.
Rebuild and vary the responsive priority example until every important piece feels familiar.
Give interactive controls enough size and separation.
Test long names, translations, zoom and missing images.
Rebuild and vary the content stress testing example until every important piece feels familiar.
Sketch one screen at three widths and document priority changes.
Prototype and test a complete task across phone, tablet and desktop.
Create reusable components and realistic interactive prototypes.
Section outcome: Build a small component library and connected prototype.
Create structures that respond to content and resizing.
Represent related states without duplicating disconnected screens.
Rebuild and vary the components and variants example until every important piece feels familiar.
Connect key journeys with meaningful state and transition cues.
Name, organise and comment so a team can understand the design.
Rebuild and vary the file organisation and collaboration example until every important piece feels familiar.
Design and connect all important states of one form control.
Build a component-based prototype for a complete user journey.
Replace assumptions with observed needs and task evidence.
Section outcome: Plan, conduct and report a small ethical usability study.
Define what you need to learn and recruit relevant participants.
Ask neutral questions and watch behaviour before offering help.
Rebuild and vary the interview and observation skills example until every important piece feels familiar.
Give realistic goals without revealing the intended interaction.
Group evidence and prioritise issues by impact and confidence.
Rebuild and vary the synthesis and prioritisation example until every important piece feels familiar.
Test one critical task and identify repeated problems.
Recruit, test, synthesise and revise a real workflow.
Design for keyboard, screen reader, low-vision and cognitive access needs.
Section outcome: Audit and repair an interactive prototype against accessibility principles.
Preserve logical order, visible focus and escape from overlays.
Provide names, roles, states and reading order that match the visual interface.
Rebuild and vary the screen-reader semantics example until every important piece feels familiar.
Connect labels, instructions and errors and preserve entered data.
Respect reduced motion, zoom, clarity and time needs.
Rebuild and vary the motion, vision and cognition example until every important piece feels familiar.
Annotate focus order and recovery for one multi-step flow.
Design, prototype and test an inclusive application form.
Document reusable decisions and collaborate without throwing static pictures over a wall.
Section outcome: Create a tokenised component reference with implementation notes.
Name reusable colour, type, spacing and elevation decisions.
Document structure, variations, content and interaction rules.
Rebuild and vary the component anatomy and states example until every important piece feels familiar.
Share dimensions, responsive behaviour and accessibility semantics.
Define how patterns are proposed, reviewed, changed and deprecated.
Rebuild and vary the governance and contribution example until every important piece feels familiar.
Document one component deeply enough for implementation.
Create foundations, six components, accessibility notes and contribution guidance.
Combine research, systems, accessibility and communication in one case study.
Section outcome: Present an evidence-backed inclusive product prototype.
Name the user need, context and limitations without inventing certainty.
Move from low fidelity to tested high-fidelity decisions.
Rebuild and vary the iterative prototype example until every important piece feels familiar.
Show what was tested, what failed and how the design changed.
Explain reasoning and contribution rather than displaying screens alone.
Rebuild and vary the portfolio storytelling example until every important piece feels familiar.
Turn one small redesign into a concise evidence story.
Research, design, test, document and present a complete accessible product flow.
Guest progress is saved in this browser on this device. Clearing site data or switching browsers can remove access to that local progress. An optional account can synchronize supported course progress; it is not required to access the lessons. Download or back up project work separately.
Certificates recognize completion of the course activities on this site. They are not university credit, professional accreditation or proof that every program you write is correct.