UI Development Made Simple
summary
Argues that component API quality, not framework choice, determines long-term UI health and demonstrates a concrete tool: via Cosmos scans a React codebase, lists components, and loads fixtures as plain JavaScript objects so each state runs in isolation. Shows proxies that inject mocked Redux or network responses, visual snapshot screenshots for CI, and an existing codebase with hundreds of tests. Claims this workflow surfaces hidden dependencies, makes reuse measurable, and reduces refactor cost from exponential to linear.
AI-written summary · about
chapters (12)
- 0:00Start
- 1:43Intro
- 3:59Component Design
- 6:40Reusable Component
- 9:49What Does Vi Cosmos Do
- 11:45Fixture Editor
- 12:11Slide Component
- 13:37Presentation Component
- 15:10Redux
- 15:39Proxies
- 21:49Cosmos versus Storybook
- 29:04How Much Time Does It Take In a Project Make all Components Usable Does It Worth the Effort
related talks
35mDesign system - From a Developer Point-of-View
44mA Practical Guide for Crafting Resilient UI Components
24mDesigning Components for Fun, Profit and Sanity
44mWriting good components
01h 04mBuilding Design Systems for Scale: From Tokens and Components to Motion & AI Tools
25mBuilding Loveable UIs
43mHow to build your reusable UI component library like a pro
34mFunctional UIs and Unidirectional Dataflow