Recomposition concept in Android Kotlin - Practice Problems & Coding Challenges

Challenge - 5 Problems

❓ ui_behavior

intermediate

What triggers recomposition in Jetpack Compose?

In Jetpack Compose, which of the following changes will cause a composable function to recompose?

A Changing a local variable inside the composable without State

B Changing a variable declared outside the composable but not observed

C Modifying a parameter passed as a constant value

D A change in a State variable used inside the composable

💡 Hint

Think about what Compose observes to know when to update the UI.

Compose tracks State variables used inside composables. When a State changes, Compose triggers recomposition to update the UI. Local variables or constants do not trigger recomposition.

❓ lifecycle

intermediate

How does recomposition affect performance?

Which statement best describes how recomposition impacts app performance in Jetpack Compose?

A Recomposition always recreates the entire UI tree, causing slow performance

B Recomposition freezes the UI until all composables finish rendering

C Recomposition only updates the parts of the UI that depend on changed State, improving efficiency

D Recomposition disables user input during the update process

💡 Hint

Think about how Compose optimizes UI updates.

Compose recomposes only the composables affected by State changes, avoiding full UI redraws and improving performance.

🔧 Debug

advanced

Why does this composable not recompose when State changes?

Consider this code snippet: @Composable fun Greeting(name: String) { Text(text = "Hello, $name!") } val userName = mutableStateOf("Alice") // In UI Greeting(name = userName.value) Why might the UI not update when userName.value changes?

A Because Greeting is not marked with @Composable

B Because userName is not passed as a State object, only its value is passed

C Because mutableStateOf does not trigger recomposition

D Because Text composable does not update on parameter changes

💡 Hint

Think about how Compose tracks State changes through parameters.

Passing only the value of a State variable does not let Compose track changes. The composable must receive a State or be called with a value that changes to trigger recomposition.

🧠 Conceptual

advanced

What is the role of remember in recomposition?

In Jetpack Compose, what does the remember function do during recomposition?

A It stores a value across recompositions to avoid resetting it

B It forces recomposition to happen immediately

C It disables recomposition for the composable

D It clears all State variables when recomposition occurs

💡 Hint

Think about how to keep values stable during UI updates.

remember keeps a value in memory across recompositions so it is not recreated each time the composable runs.

❓ navigation

expert

How does recomposition interact with navigation state?

In a Jetpack Compose app using Navigation Compose, what happens to composables when navigating between screens regarding recomposition?

A Composables of the previous screen are disposed and do not recompose when navigating away

B All composables in the app recompose on every navigation event

C Navigation Compose disables recomposition to improve speed

D Composables keep their State but never recompose after navigation

💡 Hint

Consider the lifecycle of composables in navigation stacks.

When navigating away, the previous screen's composables are removed from the composition and do not recompose until navigated back.