Recomposition concept in Android Kotlin

Introduction

Recomposition lets your app update the screen automatically when data changes. It helps keep the app UI fresh without extra work.

When you want to show updated information after a user action, like clicking a button.

When data changes in your app and you want the screen to reflect those changes immediately.

When building interactive UI components that depend on user input or live data.

When you want to avoid manually refreshing or redrawing parts of your app screen.

Syntax

Android Kotlin

@Composable
fun Greeting(name: String) {
  Text(text = "Hello, $name!")
}

Use @Composable to mark functions that describe UI.

Recomposition happens automatically when parameters or state used inside change.

Examples

This simple composable shows a greeting. If name changes, the UI updates automatically.

Android Kotlin

@Composable
fun Greeting(name: String) {
  Text(text = "Hello, $name!")
}

This example uses state. When count changes, the button text updates by recomposition.

Android Kotlin

@Composable
fun Counter() {
  var count by remember { mutableStateOf(0) }
  Button(onClick = { count++ }) {
    Text("Clicked $count times")
  }
}

Sample App

This app shows a greeting and a button. When you click the button, the name changes and the greeting updates automatically because of recomposition.

Android Kotlin

import androidx.compose.material3.*
import androidx.compose.foundation.layout.Column
import androidx.compose.runtime.*
import androidx.compose.ui.window.singleWindowApplication

fun main() = singleWindowApplication {
  var name by remember { mutableStateOf("World") }

  Column {
    Text(text = "Hello, $name!", style = MaterialTheme.typography.headlineMedium)
    Button(onClick = { name = "Compose" }) {
      Text("Change Name")
    }
  }
}

Important Notes

Recomposition only updates the parts of the UI that depend on changed data, making it efficient.

Use remember and mutableStateOf to hold state that triggers recomposition.

Too many unnecessary recompositions can slow your app, so keep state minimal and focused.

Summary

Recomposition updates UI automatically when data changes.

Use @Composable functions with state to enable recomposition.

It helps build interactive and responsive apps easily.

Practice

1. What does recomposition mean in Jetpack Compose?

easy

A. The app restarts when the user rotates the screen

B. The UI updates automatically when data changes

C. The app saves data to the database

D. The UI is drawn only once at app launch

Solution

1. Step 1: Understand recomposition meaning

   Recomposition means the UI redraws when the data it depends on changes.

2. Step 2: Compare options with definition

   Only The UI updates automatically when data changes describes this automatic UI update behavior.

3. Final Answer:

   The UI updates automatically when data changes -> Option B

4. Quick Check:

   Recomposition = UI updates on data change [OK]

Hint: Recomposition means UI changes with data changes [OK]

Common Mistakes:

• Confusing recomposition with app restart
• Thinking recomposition saves data
• Believing UI draws only once

2. Which of the following is the correct way to declare a state variable in Jetpack Compose to trigger recomposition?

easy

A. var count = 0

B. val count = 0

C. var count = mutableListOf(0)

D. val count = remember { mutableStateOf(0) }

Solution

1. Step 1: Identify state declaration for recomposition

   In Compose, state variables use remember { mutableStateOf() } to trigger recomposition.

2. Step 2: Check options for correct syntax

   Only val count = remember { mutableStateOf(0) } uses remember { mutableStateOf(0) } correctly.

3. Final Answer:

   val count = remember { mutableStateOf(0) } -> Option D

4. Quick Check:

   State variable uses remember + mutableStateOf [OK]

Hint: Use remember { mutableStateOf() } for state [OK]

Common Mistakes:

• Using plain variables without remember
• Using val without state wrapper
• Using mutableList instead of mutableStateOf

3. Given this code snippet, what will be displayed when the button is clicked once?

var count by remember { mutableStateOf(0) }
Button(onClick = { count++ }) {
  Text("Clicked: $count")
}

medium

A. Clicked: 0

B. Clicked: null

C. Clicked: 1

D. Clicked: 2

Solution

1. Step 1: Understand initial state and click effect

   Initial count is 0. Clicking the button increments count by 1.

2. Step 2: Determine displayed text after one click

   After one click, count becomes 1, so text shows "Clicked: 1".

3. Final Answer:

   Clicked: 1 -> Option C

4. Quick Check:

   State increments on click, text updates [OK]

Hint: Count starts 0, increments by 1 on click [OK]

Common Mistakes:

• Thinking count stays 0 after click
• Assuming count increments twice
• Confusing null with zero

4. What is wrong with this code that prevents recomposition when the button is clicked?

var count = 0
Button(onClick = { count++ }) {
  Text("Count: $count")
}

medium

A. count is not a state variable, so UI won't update

B. Button onClick syntax is incorrect

C. Text composable cannot display variables

D. count should be a val, not var

Solution

1. Step 1: Identify state usage in code

   Variable count is a plain var, not wrapped in state, so Compose won't track changes.

2. Step 2: Understand recomposition trigger

   Without state, UI does not recompose on count change, so text stays the same.

3. Final Answer:

   count is not a state variable, so UI won't update -> Option A

4. Quick Check:

   State needed for recomposition [OK]

Hint: Use state variables to trigger UI updates [OK]

Common Mistakes:

• Thinking var alone triggers recomposition
• Believing onClick syntax is wrong
• Assuming Text can't show variables

5. You want to create a counter that resets to zero when it reaches 5, updating the UI automatically. Which code snippet correctly uses recomposition to achieve this?

@Composable
fun Counter() {
  var count by remember { mutableStateOf(0) }
  Button(onClick = {
    count = if (count == 5) 0 else count + 1
  }) {
    Text("Count: $count")
  }
}

hard

A. Correct: count resets at 5 and UI updates

B. Incorrect: count never resets to zero

C. Incorrect: count is not a state variable

D. Incorrect: Button onClick syntax is invalid

Solution

1. Step 1: Analyze state and logic in code

   Variable count is a state variable with remember and mutableStateOf, so UI updates on change.

2. Step 2: Check reset logic correctness

   When count reaches 5, it resets to 0; otherwise, it increments by 1. This logic is correct.

3. Final Answer:

   Correct: count resets at 5 and UI updates -> Option A

4. Quick Check:

   State + reset logic triggers recomposition [OK]

Hint: Use state and conditional update for reset [OK]

Common Mistakes:

• Not using state variable for count
• Missing reset condition
• Incorrect Button onClick syntax