Why Compose is the modern UI toolkit in Android Kotlin - Challenge Your Understanding

Challenge - 5 Problems

🧠 Conceptual

intermediate

Why does Jetpack Compose simplify UI development?

Jetpack Compose uses a declarative approach to build UI. What is the main advantage of this compared to the traditional XML layouts?

A It allows UI to be described in code, making it easier to read and update dynamically.

B It requires writing more XML files to separate UI and logic clearly.

C It forces developers to use imperative programming for UI updates.

D It disables live previews, making debugging harder.

💡 Hint

Think about how describing UI in code can help with dynamic changes.

Jetpack Compose lets you write UI as functions in Kotlin, so you can easily change UI based on state without managing XML files separately.

❓ ui_behavior

intermediate

What happens when state changes in Compose?

In Jetpack Compose, when a state variable used in a composable changes, what is the expected behavior?

A The composable automatically recomposes to reflect the new state.

B The app crashes because state changes are not allowed.

C Nothing happens until the user restarts the app.

D The UI freezes until the state is manually refreshed.

💡 Hint

Think about how Compose keeps UI in sync with data.

Compose tracks state changes and automatically updates the UI by recomposing affected parts, so the UI always matches the current state.

❓ lifecycle

advanced

How does Compose handle lifecycle compared to Views?

Which statement best describes how Jetpack Compose manages UI lifecycle compared to traditional Android Views?

A Compose does not support lifecycle awareness and ignores activity states.

B Compose requires manual calls to lifecycle methods like onCreateView for each composable.

C Compose automatically disposes and recreates UI elements during recomposition, reducing manual lifecycle handling.

D Compose UI elements persist forever and never get recreated.

💡 Hint

Consider how Compose updates UI without explicit lifecycle calls.

Compose manages UI elements internally and recreates them as needed during recomposition, so developers don't have to manually handle lifecycle events for UI components.

❓ navigation

advanced

How does Compose integrate with navigation?

What is a key benefit of using Jetpack Compose with the Navigation component?

A Compose requires separate XML navigation graphs for each screen.

B Navigation destinations can be defined as composable functions, simplifying navigation code.

C Navigation is not supported in Compose apps.

D Compose forces navigation to be handled only by activities.

💡 Hint

Think about how Compose uses functions for UI.

With Compose, you can define navigation destinations as composable functions, making navigation code more concise and easier to maintain without XML graphs.

🔧 Debug

expert

What causes this Compose recomposition bug?

Consider this code snippet: @Composable fun Greeting(name: String) { var counter = 0 Button(onClick = { counter++ }) { Text("Hello, $name! Clicked $counter times") } } Why does the counter not increase when the button is clicked?

A Because Compose does not support state inside composables.

B Because the Button onClick lambda is not called.

C Because the Text composable cannot display variables.

D Because 'counter' is a local variable and resets to 0 on every recomposition.

💡 Hint

Think about where the variable is declared and how Compose recomposes.

Local variables inside composables reset every time the function recomposes. To keep state, you must use remember or state holders.