Skip to content
make this work.dev
Home Blog Courses FitHub About
Courses / Mastering Jetpack Compose

Reading a recomposition trace

From "it feels slow" to a named Composable in four minutes.

Lesson 4 of 5 ·34 min

This lesson isn't open to you yet

Part of Mastering Jetpack Compose. Sign in if you've bought it, or get access below.

See the course
PreviousRecomposition scopes and where they end NextLazyColumn: keys, contentType, and the cost of getting them wrong

Mastering Jetpack Compose

  1. 01 The slot table, demystified
  2. 02 Stability is a promise, not an annotation
  3. 03 Recomposition scopes and where they end
  4. 04 Reading a recomposition trace
  5. 05 LazyColumn: keys, contentType, and the cost of getting them wrong
make this work.dev

Deep dives into modern Android engineering — Kotlin, Jetpack Compose, coroutines and clean architecture, explained from the source code up.

Site

Home Blog Courses FitHub About

Topics

Android Architecture Kotlin & Core Concepts System Design Design System Kotlin Multiplatform

Elsewhere

LinkedIn GitHub Email
© 2026 Make This Work. All rights reserved. Let's make this work.