UI/UX Quick Start for Developers Curriculum

Public curriculum preview for visitors and enrolled students. Use this page to evaluate module scope, outcomes, and learning path.

Curriculum

UI/UX Quick Start for Developers

Design better interfaces: user research, wireframing, prototyping, and usability.

Duration: 12 Weeks
Level: Beginner
Study Time: 2 hours/week + labs
School: Hexadigitall Academy

Welcome to UI/UX Quick Start for Developers! 🎓

This curriculum is designed to take you from core understanding to confident delivery through weekly applied practice, measurable outcomes, and portfolio evidence.

Each week builds progressively with practical tasks, implementation checkpoints, and reflection points so you can convert knowledge into repeatable professional performance.

Your success is our priority. Stay consistent with weekly execution, document your work, and use feedback loops to continuously improve your delivery quality.

Essential Resources

  • Design system templates, component libraries, and accessibility audit checklists
  • Figma starter kits with typography scales, color systems, and responsive breakpoints
  • Usability testing scripts and design critique frameworks

Learning Roadmap

  • Early Weeks: Design fundamentals, visual hierarchy, and component basics
  • Middle Weeks: Design systems, accessibility standards, and interaction patterns
  • Late Weeks: Portfolio building, stakeholder communication, and design leadership
  • Accessibility Basics Every Developer Should Know
  • Visual Hierarchy, Spacing, and Typography in User Interfaces
  • Design Systems, Tokens, and Reusable Components
  • Working in Figma as a Developer
  • Prototyping Interactions and State Changes
  • Forms, Error States, and Usability Patterns
  • Testing Interfaces with Real Users or Teammates
  • Turning Feedback into Interface Iterations
  • Capstone: Design and Build a Developer-Friendly Product Screen

Detailed Weekly Curriculum

Each week includes outcomes and practical lab work aligned to the curriculum structure.

Week 1

Thinking Like a User: UX Fundamentals for Developers

2 hours/week + labs
Learning Outcomes
  • Identify the principles of Thinking Like a User: UX Fundamentals for Developers and link them to course outcomes in time-boxed sprints with rapid feedback loops.
  • Explain Thinking Like a User: UX Fundamentals for Developers in a guided scenario using realistic tools, constraints, and quality gates.
  • Apply trade-offs, risks, and decision points for Thinking Like a User: UX Fundamentals for Developers, then record rationale for stakeholder review.
  • Document a portfolio-ready delivery strategy memo for Thinking Like a User: UX Fundamentals for Developers with measurable success criteria and next actions.
  • Track measurable progress using rubric scores, defect/risk trends, and evidence completeness each week.
  • Run a short retrospective focused on what to retain, improve, and scale into the following week.
  • Incorporate peer or mentor feedback and revise the week deliverable to professional publication quality.
  • Publish the week output into your cumulative portfolio with concise outcome narrative and proof artifacts.
Week 2

Reading Requirements as User Flows and Journeys

2 hours/week + labs
Learning Outcomes
  • Identify the principles of Reading Requirements as User Flows and Journeys and link them to course outcomes in time-boxed sprints with rapid feedback loops.
  • Explain Reading Requirements as User Flows and Journeys in a guided scenario using realistic tools, constraints, and quality gates.
  • Apply trade-offs, risks, and decision points for Reading Requirements as User Flows and Journeys, then record rationale for stakeholder review.
  • Document a portfolio-ready delivery strategy memo for Reading Requirements as User Flows and Journeys with measurable success criteria and next actions.
  • Track measurable progress using rubric scores, defect/risk trends, and evidence completeness each week.
  • Run a short retrospective focused on what to retain, improve, and scale into the following week.
  • Incorporate peer or mentor feedback and revise the week deliverable to professional publication quality.
  • Publish the week output into your cumulative portfolio with concise outcome narrative and proof artifacts.
Week 3

Wireframes, Layout Planning, and Information Architecture

2 hours/week + labs
Learning Outcomes
  • Identify the principles of Wireframes, Layout Planning, and Information Architecture and link them to course outcomes in time-boxed sprints with rapid feedback loops.
  • Explain Wireframes, Layout Planning, and Information Architecture in a guided scenario using realistic tools, constraints, and quality gates.
  • Apply trade-offs, risks, and decision points for Wireframes, Layout Planning, and Information Architecture, then record rationale for stakeholder review.
  • Document a portfolio-ready delivery strategy memo for Wireframes, Layout Planning, and Information Architecture with measurable success criteria and next actions.
  • Track measurable progress using rubric scores, defect/risk trends, and evidence completeness each week.
  • Run a short retrospective focused on what to retain, improve, and scale into the following week.
  • Incorporate peer or mentor feedback and revise the week deliverable to professional publication quality.
  • Publish the week output into your cumulative portfolio with concise outcome narrative and proof artifacts.
Week 4

Accessibility Basics Every Developer Should Know

2 hours/week + labs
Learning Outcomes
  • Identify the principles of Accessibility Basics Every Developer Should Know and link them to course outcomes in time-boxed sprints with rapid feedback loops.
  • Explain Accessibility Basics Every Developer Should Know in a guided scenario using realistic tools, constraints, and quality gates.
  • Apply trade-offs, risks, and decision points for Accessibility Basics Every Developer Should Know, then record rationale for stakeholder review.
  • Document a portfolio-ready delivery strategy memo for Accessibility Basics Every Developer Should Know with measurable success criteria and next actions.
  • Track measurable progress using rubric scores, defect/risk trends, and evidence completeness each week.
  • Run a short retrospective focused on what to retain, improve, and scale into the following week.
  • Incorporate peer or mentor feedback and revise the week deliverable to professional publication quality.
  • Publish the week output into your cumulative portfolio with concise outcome narrative and proof artifacts.
Week 5

Visual Hierarchy, Spacing, and Typography in User Interfaces

2 hours/week + labs
Learning Outcomes
  • Apply the principles of Visual Hierarchy, Spacing, and Typography in User Interfaces and link them to course outcomes in time-boxed sprints with rapid feedback loops.
  • Analyze Visual Hierarchy, Spacing, and Typography in User Interfaces in a guided scenario using realistic tools, constraints, and quality gates.
  • Evaluate trade-offs, risks, and decision points for Visual Hierarchy, Spacing, and Typography in User Interfaces, then record rationale for stakeholder review.
  • Document a portfolio-ready delivery strategy memo for Visual Hierarchy, Spacing, and Typography in User Interfaces with measurable success criteria and next actions.
  • Track measurable progress using rubric scores, defect/risk trends, and evidence completeness each week.
  • Run a short retrospective focused on what to retain, improve, and scale into the following week.
  • Incorporate peer or mentor feedback and revise the week deliverable to professional publication quality.
  • Publish the week output into your cumulative portfolio with concise outcome narrative and proof artifacts.
Week 6

Design Systems, Tokens, and Reusable Components

2 hours/week + labs
Learning Outcomes
  • Apply the principles of Design Systems, Tokens, and Reusable Components and link them to course outcomes in time-boxed sprints with rapid feedback loops.
  • Analyze Design Systems, Tokens, and Reusable Components in a guided scenario using realistic tools, constraints, and quality gates.
  • Evaluate trade-offs, risks, and decision points for Design Systems, Tokens, and Reusable Components, then record rationale for stakeholder review.
  • Document a portfolio-ready delivery strategy memo for Design Systems, Tokens, and Reusable Components with measurable success criteria and next actions.
  • Track measurable progress using rubric scores, defect/risk trends, and evidence completeness each week.
  • Run a short retrospective focused on what to retain, improve, and scale into the following week.
  • Incorporate peer or mentor feedback and revise the week deliverable to professional publication quality.
  • Publish the week output into your cumulative portfolio with concise outcome narrative and proof artifacts.
Week 7

Working in Figma as a Developer

2 hours/week + labs
Learning Outcomes
  • Apply the principles of Working in Figma as a Developer and link them to course outcomes in time-boxed sprints with rapid feedback loops.
  • Analyze Working in Figma as a Developer in a guided scenario using realistic tools, constraints, and quality gates.
  • Evaluate trade-offs, risks, and decision points for Working in Figma as a Developer, then record rationale for stakeholder review.
  • Document a portfolio-ready delivery strategy memo for Working in Figma as a Developer with measurable success criteria and next actions.
  • Track measurable progress using rubric scores, defect/risk trends, and evidence completeness each week.
  • Run a short retrospective focused on what to retain, improve, and scale into the following week.
  • Incorporate peer or mentor feedback and revise the week deliverable to professional publication quality.
  • Publish the week output into your cumulative portfolio with concise outcome narrative and proof artifacts.
Week 8

Prototyping Interactions and State Changes

2 hours/week + labs
Learning Outcomes
  • Apply the principles of Prototyping Interactions and State Changes and link them to course outcomes in time-boxed sprints with rapid feedback loops.
  • Analyze Prototyping Interactions and State Changes in a guided scenario using realistic tools, constraints, and quality gates.
  • Evaluate trade-offs, risks, and decision points for Prototyping Interactions and State Changes, then record rationale for stakeholder review.
  • Document a portfolio-ready delivery strategy memo for Prototyping Interactions and State Changes with measurable success criteria and next actions.
  • Track measurable progress using rubric scores, defect/risk trends, and evidence completeness each week.
  • Run a short retrospective focused on what to retain, improve, and scale into the following week.
  • Incorporate peer or mentor feedback and revise the week deliverable to professional publication quality.
  • Publish the week output into your cumulative portfolio with concise outcome narrative and proof artifacts.
Week 9

Forms, Error States, and Usability Patterns

2 hours/week + labs
Learning Outcomes
  • Analyze the principles of Forms, Error States, and Usability Patterns and link them to course outcomes in time-boxed sprints with rapid feedback loops.
  • Evaluate Forms, Error States, and Usability Patterns in a guided scenario using realistic tools, constraints, and quality gates.
  • Create trade-offs, risks, and decision points for Forms, Error States, and Usability Patterns, then record rationale for stakeholder review.
  • Defend a portfolio-ready delivery strategy memo for Forms, Error States, and Usability Patterns with measurable success criteria and next actions.
  • Track measurable progress using rubric scores, defect/risk trends, and evidence completeness each week.
  • Run a short retrospective focused on what to retain, improve, and scale into the following week.
  • Incorporate peer or mentor feedback and revise the week deliverable to professional publication quality.
  • Publish the week output into your cumulative portfolio with concise outcome narrative and proof artifacts.
Week 10

Testing Interfaces with Real Users or Teammates

2 hours/week + labs
Learning Outcomes
  • Analyze the principles of Testing Interfaces with Real Users or Teammates and link them to course outcomes in time-boxed sprints with rapid feedback loops.
  • Evaluate Testing Interfaces with Real Users or Teammates in a guided scenario using realistic tools, constraints, and quality gates.
  • Create trade-offs, risks, and decision points for Testing Interfaces with Real Users or Teammates, then record rationale for stakeholder review.
  • Defend a portfolio-ready delivery strategy memo for Testing Interfaces with Real Users or Teammates with measurable success criteria and next actions.
  • Track measurable progress using rubric scores, defect/risk trends, and evidence completeness each week.
  • Run a short retrospective focused on what to retain, improve, and scale into the following week.
  • Incorporate peer or mentor feedback and revise the week deliverable to professional publication quality.
  • Publish the week output into your cumulative portfolio with concise outcome narrative and proof artifacts.
Week 11

Turning Feedback into Interface Iterations

2 hours/week + labs
Learning Outcomes
  • Analyze the principles of Turning Feedback into Interface Iterations and link them to course outcomes in time-boxed sprints with rapid feedback loops.
  • Evaluate Turning Feedback into Interface Iterations in a guided scenario using realistic tools, constraints, and quality gates.
  • Create trade-offs, risks, and decision points for Turning Feedback into Interface Iterations, then record rationale for stakeholder review.
  • Defend a portfolio-ready delivery strategy memo for Turning Feedback into Interface Iterations with measurable success criteria and next actions.
  • Track measurable progress using rubric scores, defect/risk trends, and evidence completeness each week.
  • Run a short retrospective focused on what to retain, improve, and scale into the following week.
  • Incorporate peer or mentor feedback and revise the week deliverable to professional publication quality.
  • Publish the week output into your cumulative portfolio with concise outcome narrative and proof artifacts.
Week 12

Capstone: Design and Build a Developer-Friendly Product Screen

2 hours/week + labs
Learning Outcomes
  • Analyze the principles of Capstone: Design and Build a Developer-Friendly Product Screen and link them to course outcomes in time-boxed sprints with rapid feedback loops.
  • Evaluate Capstone: Design and Build a Developer-Friendly Product Screen in a guided scenario using realistic tools, constraints, and quality gates.
  • Create trade-offs, risks, and decision points for Capstone: Design and Build a Developer-Friendly Product Screen, then record rationale for stakeholder review.
  • Defend a portfolio-ready delivery strategy memo for Capstone: Design and Build a Developer-Friendly Product Screen with measurable success criteria and next actions.
  • Track measurable progress using rubric scores, defect/risk trends, and evidence completeness each week.
  • Run a short retrospective focused on what to retain, improve, and scale into the following week.
  • Incorporate peer or mentor feedback and revise the week deliverable to professional publication quality.
  • Publish the week output into your cumulative portfolio with concise outcome narrative and proof artifacts.

Capstone Projects

Project 1: UX Audit and Wireframe Redesign

Analyze an existing product screen, identify usability gaps, and deliver a low-fidelity redesign with improved task flow.

  • Heuristic audit report with severity ranking
  • Wireframe redesign with annotated decisions
  • Accessibility and usability improvement checklist

Project 2: Developer-Ready Figma Component Kit

Create a reusable component and token system in Figma aligned to practical frontend implementation needs.

  • Component variants and state definitions
  • Design tokens for spacing, type, and color
  • Handoff documentation for engineering

Project 3: Capstone: Product Screen Case Study

Deliver a full UI/UX case study for a product screen, including research insights, prototype states, testing feedback, and final handoff assets.

  • End-to-end design process documentation
  • Interactive prototype with key user paths
  • Portfolio-ready narrative and next-step roadmap