No More Getting Lost! A Practical Guide to Writing Jetpack Compose

When writing Compose, have these thoughts ever crossed your mind? “Should I always include a modifier parameter? Is it okay to have more than one?” “What’s the best method name when I split up Composables?” or even “Do I need to split this into separate Composables at all?” This session digs into best practices for building maintainable UIs with Jetpack Compose and shares practical know-how so you can put those doubts to rest. I’ll explain why these practices matter, weaving in Compose’s internals—composition and recomposition—along the way. With plenty of concrete code samples (recommended patterns and anti-patterns to avoid), you’ll learn how to apply them in day-to-day development. Agenda - Writing patterns that hurt performance and how to avoid them - Criteria for properly dividing Composable responsibilities - The importance of Modifiers and how to pass them around - Concrete implementation patterns that consider performance and accessibility when using core standard components - Rolling this out in a team: tips on code reviews and tooling to share and apply these practices together (Translated by the DroidKaigi Committee)