Writing

Organized by topic. Starting with Compose internals — more areas of the Android framework on the way.

Kotlin1

Closures and inline in Kotlin, from First PrinciplesA closure is a function bundled with the variables it captured; inline decides whether that bundle becomes a real heap object or gets pasted into the call site — and almost every Kotlin footgun here comes from misreading when and where a captured variable is read.

Compose Internals6

Animation Patterns: Which Tool Fits Which AnimationWhich animation tool to reach for - built-in animate*AsState, Modifier.Node, or a wrapper - mapped to value-change, triggered, and continuous animations, with code.
When (and When Not) to Write a Custom Modifier.NodeA decision framework for choosing between built-in modifiers, lambda modifiers, wrapper composables, effects, and a full Modifier.Node - grounded in Compose internals.
The Compose Measure Phase: Measurable, Constraints, Placeable, layout(), place()The measure phase as a top-down conversation: the parent hands a child a Constraints budget, the child returns a sized Placeable, and the layout between can rewrite both.
Custom Modifiers with Modifier.NodeBuilding production custom modifiers from three pieces - an extension function, a ModifierNodeElement, and a Modifier.Node - with real lifecycle and in-place updates.
Compose: Component Identity, the Slot Table, and State LifecycleHow Compose tracks composable identity through the slot table, how remember and key() really work, and the only three ways state ever resets.
Modifiers vs Single-Child Wrapper ComposablesWhy a Modifier.foo() beats a Foo { content } wrapper for decorating a single child: preserved node identity, flat chaining, and fewer layout nodes.