AAndroid Expert2d ago · 12 min readThree Moments in a Composable’s Life: Composition, Recomposition, and Measure-Time SubcompositionMost Compose bugs I get pulled into are not syntax bugs. They are timing bugs. Someone reads state in the wrong place, builds a layout that needs a size before it exists, or assumes a remember block landroid-expert.hashnode.dev
AAndroid Expert2d ago · 10 min readState, MutableState, and SnapshotStateList: What Actually Differs (and How Each One Fails in Production)Every Compose codebase eventually grows the same three bugs: a list that never updates, a counter that quietly allocates in a scroll handler, and a “read-only” state that someone mutated from the wronandroid-expert.hashnode.dev
AAndroid Expert3d ago · 9 min readInside the Compose Slot Table: Positional Memoization, Gap Buffers, and the Bugs They CauseMost Compose bugs I see in code review share one root cause: someone treated a @Composable function like a view factory instead of a function whose call position is its identity. Once you understand tandroid-expert.hashnode.dev