Compose beyond Material
summary
Argues that you can drop Material and reuse Compose foundation to implement a custom design system: remove the Material dependency (or hide its packages in IntelliJ), reuse basicText and BasicTextField to cover ~90–98% of text and editable text work, implement themes with composition locals, use indications/modifiers for interactions, and draw custom widgets (progress bar) on Canvas with a clip trick to avoid ugly rounded-corner artifacts. Emphasizes slot APIs, scoping, and adding semantics for accessibility.
AI-written summary · about
chapters (8)
- 0:00Introduction
- 1:54Material design overview
- 9:23Removing Material dependency
- 12:57Foundation and building blocks
- 15:25Custom theme implementation
- 21:47API design principles
- 29:56Creating custom composables
- 40:28Key takeaways
related talks
35mCompose beyond Material
26mCompose Beyond Material Design
39mRe-Compose your UI: building an atomic design library
38mDesigning scalable Compose APIs
15mBuild beautiful Material Design apps with Jetpack Compose
50mCustom Design Systems in Compose
49mImplement your own design system with Jetpack Compose
41mCompose by Example