How does Material-UI build components?
summary
Material-UI shows the autocomplete case study and says the initial implementation costs about 100 hours initial bet, uses analytics (npm downloads) to choose work, and ships experiments in a lab package before promotion. Accessibility testing uses screen readers (VoiceOver, NVDA) and testing-library. The project records ~500 issues on that component, has 54 contributors to the hook API, reports doubled revenue in 2020 versus 2019, and is building a data grid (250 hours so far, expecting ~10× more).
AI-written summary · about
chapters (26)
- 0:00Start
- 0:53Structure
- 1:15React
- 1:27What is a component?
- 2:01What is Material-UI?
- 2:51Market share
- 3:47Diverse use cases
- 4:50The challenges
- 5:14Our mission
- 5:59Our priorities
- 6:32Case study
- 6:53Find a problem worth solving
- 7:47Have the right timing
- 8:27Quality vs Quantity
- 9:45Product benchmark
- 10:45Find the features worth implementing
- 11:24Implement the smallest possible set of fea
- 14:23Accessibility & - How?
- 15:16API dilemma
- 19:28Why hooks?
- 20:40From lab to core
- 22:16Publish it in the core
- 22:45Make it sustainable
- 23:50A quick update on our roadmap & strateg
- 25:13Upcoming data grid
- 26:00Our team
related talks
46mBuilding Reusable Components ... That Are Actually Reusable
58mChasing the holy grail: reusable web components and design tokens
27mAccelerating Development using UI frameworks
24mCase Study: Creating a Component Library in React JS
32mUI Development Made Simple
28mLet's talk about design systems
24mDesigning Components for Fun, Profit and Sanity
28mBuilding reusable UI components in Vue