Recomposition concept in Android Kotlin - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is recomposition in Jetpack Compose?

Recomposition is the process where Compose updates the UI by re-running composable functions when their input data changes.

beginner

Which of these triggers recomposition in Jetpack Compose?

Changing a State variable that a composable reads triggers recomposition.

beginner

True or False: Recomposition always recreates the entire UI from scratch.

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

intermediate

What role does remember play in recomposition?

remember helps keep state across recompositions so that values are not reset every time the UI updates.

intermediate

How can you minimize unnecessary recompositions?

By keeping state as local as possible and using derivedStateOf or remember to avoid recomposing unaffected parts.

What causes recomposition in Jetpack Compose?

A Rotating the device without state change

B Changing the app's theme only

C Opening a new activity

D A change in a State variable used by a composable

Recomposition happens when a State variable that a composable reads changes, triggering UI update.

Which keyword helps preserve values across recompositions?

A lateinit

B var

C remember

D val

remember stores values so they survive recompositions and are not reset.

True or False: Recomposition recreates the entire UI tree every time.

A False

B True

C Only on app start

D Only on configuration change

Recomposition only updates parts of the UI affected by data changes, not the entire UI.

How can you reduce unnecessary recompositions?

A Use global variables for all state

B Keep state local and use derivedStateOf

C Avoid using remember

D Recreate all composables on every change

Localizing state and using derivedStateOf helps limit recomposition to needed parts.

What is recomposition's main benefit?

A Efficient UI updates only where needed

B Slower UI rendering

C Forces full app restart

D Disables state management

Recomposition updates only changed UI parts, making UI updates efficient and smooth.

Explain recomposition in Jetpack Compose and why it is important.

Think about how the UI updates when data changes.

Describe how to optimize recomposition to improve app performance.

Consider how to limit UI updates only to parts that need it.

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