
Build interfaces people actually want to use
We skip the theory lectures and outdated examples. Instead, you'll work on projects that mirror what design teams face every week—messy requirements, tight deadlines, and users who don't behave like textbooks say they should.
Start your applicationLearning that mirrors actual studio work
Most courses hand you clean mockups and perfect briefs. That's not how it works when you're three days from launch and the client just changed their mind about navigation.
Our curriculum throws you into scenarios lifted straight from production environments. You'll collaborate with designers who have conflicting visions, inherit codebases that make you question humanity, and present work to people who "just want it to pop more."
This isn't about memorizing CSS properties. It's about building the judgment to know when to push back on a design request and when to find a creative solution under constraint.

How we structure the experience
Every cohort follows a progression that gradually increases complexity while maintaining connection to real deliverables.
Project-centered weeks
Each module revolves around a specific deliverable—landing pages, dashboards, checkout flows. You build something complete, not isolated components that never connect.
Critique sessions that matter
Twice weekly, you present work to peers and practicing designers. Feedback focuses on usability decisions and implementation tradeoffs, not surface aesthetics.
Code review culture
Every project goes through structured review where we examine architecture choices, accessibility concerns, and performance implications. You learn to defend your decisions.

Who this works for
Our strongest students come from adjacent fields—graphic designers tired of static work, backend developers who want to own the full stack, product managers who need to speak design language fluently.
You should already be comfortable with HTML and basic CSS. We won't spend time on syntax—we assume you can look that up. What we teach is harder to Google: when to use Grid vs Flexbox for a specific layout challenge, how to structure components for maintainability, why that animation feels wrong even though it's technically correct.
If you're looking for certification or structured career guarantees, this probably isn't the right fit. We focus on capability. Learn more about our approach and see if it aligns with how you want to grow.
Sixteen weeks of focused building
The program runs in four distinct phases. Each builds on previous work while introducing new constraints and complexity.
Foundations and tooling
First month covers responsive principles, browser dev tools, and Git workflows. You build three progressively complex layouts while establishing code review habits.
Component thinking
Weeks five through eight focus on modular design systems. You create reusable patterns and learn when abstraction helps versus when it creates unnecessary complexity.
Performance and accessibility
Third phase introduces optimization techniques and WCAG compliance. Projects now include performance budgets and screen reader testing as requirements.
Capstone integration
Final month is self-directed work on a substantial project. You pitch concepts, iterate based on feedback, and present the finished product to working professionals.
Applications open February 2026
Next cohort begins March 10, 2026 and runs through June. Classes meet Tuesday and Thursday evenings Taiwan time, with recorded sessions available for review. Limited to eighteen participants to maintain meaningful feedback loops.