What State Hides in Compose
summary
The talk explains how Jetpack Compose State works internally: what State hides, how it notifies compose about changes to trigger recomposition, and why it’s more complex than it appears. It covers thread-safety of State, how state change notifications are implemented, and how transaction-like mechanisms (similar to database transactions) relate to Compose’s update model.
AI-written summary · about
chapters (11)
- 0:00Introduction
- 2:51State in Compose purpose
- 5:46State internals
- 8:17Concurrency Control in Compose
- 12:11Public Snapshot API
- 16:06Concurrent writes and conflicts
- 20:10Primitive Snapshot creation
- 24:30Mutable State read/write
- 26:16Snapshot ID mechanism
- 30:51How recomposition works
- 35:05Summary
related talks
42mJetpack Compose: Art of the State
17mWhat's new in Jetpack Compose
11mInvest in Real State: A workshop for State in Compose
45mMastering Recomposition: Optimizing State Changes for Efficient UI
40mJetpack Compose Mechanisms
40mThe Compose Runtime, Demystified
40mMaking Large Screens Easier in Compose
34mBeyond the UI: Compose as a Foundation for Multiplatform Apps