Android Expert·3d agoQuayside Benchmarks: Making Compose Faster Without Fooling YourselfProfile with Perfetto, choose computedStateOf or derivedStateOf, use keyed SideEffect, and dodge the traps that make tuning backfire.
Android Expert·Oct 25Where You Read Matters: Steering Compose Work with Deferred State Reads, derivedStateOf, and…Defer state reads to layout or draw, filter noisy input with derivedStateOf, and verify the gains with Layout Inspector counts.
Android Expert·Oct 24The Skip That Never Happens: Hunting Compose Stability Bugs in ProductionWhy a harmless List<String> can silently disable skipping in Jetpack Compose, and how to find and fix it with compiler reports.
Android Expert·Oct 20Same Type, No Guarantees: Why Compose Distrusts Your List, Set and MapUnstable collections quietly break skipping in Jetpack Compose. Here are two fixes, four real failure modes, and how to choose.
Android Expert·Oct 4Three Moments in a Composable’s Life: Composition, Recomposition, and Measure-Time SubcompositionHow Compose decides when your code runs, what re-runs, and why SubcomposeLayout exists, with six production failure modes and fixes.
Android Expert·Oct 4The Slot Tax: What Compose’s remember Really Costs, and When to Leave It OutWhen caching pays off, when it’s dead weight, and six production bugs that come from wrapping everything in remember.
Android Expert·Oct 3State, MutableState, and SnapshotStateList: What Actually Differs (and How Each One Fails in…How Compose tracks reads and writes, why mutableIntStateOf only helps if you read .intValue, and six failure modes that bite in production.
Android Expert·Oct 2Inside the Compose Slot Table: Positional Memoization, Gap Buffers, and the Bugs They CauseHow gap buffers, group keys, and positional memoization drive recomposition, and the production state bugs they cause when ignored.A response icon1A response icon1
Android Expert·Oct 1The Function You Wrote Isn’t the Function That RunsWhat the Jetpack Compose compiler really emits, and how to stop it from silently costing you frames, from $changed bits to stability.
Android Expert·Sep 27Modifier.Node: Why Compose Killed composed {}Inside the allocation storms, hidden recompositions, and GC stutters that pushed Compose toward Modifier.Node.
