Building Compose APIs
summary
Jetpack Compose team replaces a brittle swipeable API with a simpler, iteration-first design that becomes anchorDragable state plus modifier.dragable. The old API forces a composition pass, layout measurement, then a recomposition for layout dependent anchors, slowing components and making tests flaky. The new design moves the core into foundation, exposes updateAnchors safely, removes a separate swipe‑anchors modifier, and proves workable after internal MVPs and migrations, reducing complexity and surprising two‑pass behavior.
AI-written summary · about
chapters (13)
- 0:00Introduction
- 1:31Problem with Swipeable API
- 6:25Redesigning the API
- 10:41Breaking down the API
- 13:34Modifier vs Composable
- 16:02Naming challenges
- 18:27Core API parts
- 19:32Layering in Compose
- 22:02Iterating on APIs
- 23:05Prototype lessons
- 26:42Simplifying APIs
- 28:10Public API release
- 31:21Final thoughts
related talks
37m5 Easy steps to build a Compose API
38mDesigning scalable Compose APIs
37mAdopting Jetpack Compose Safely
17mWhat's new in Jetpack Compose
01h 12mJetpack Compose over inheritance
31mDesigning Media Friendly Jetpack Compose Components
39mRe-Compose your UI: building an atomic design library
32mJetpack Compose — Next Gen Kotlin UI Toolkit for Android
