Navigating between composables in Android Kotlin - UI Render Trace

Component - Navigating between composables

This UI component demonstrates how to move from one screen to another using navigation between composables in Android Jetpack Compose. It shows a simple button that, when clicked, takes the user from the first screen to the second screen.

Widget Tree

NavHost
├─ NavGraph
│  ├─ Composable(Screen1)
│  │  └─ Column
│  │     ├─ Text
│  │     └─ Button
│  └─ Composable(Screen2)
│     └─ Column
│        └─ Text

The NavHost holds the navigation graph. The graph has two composable destinations: Screen1 and Screen2. Screen1 contains a vertical column with a text label and a button. Screen2 contains a column with a text label. The button on Screen1 triggers navigation to Screen2.

Render Trace - 4 Steps

Step 1: NavHost

Step 2: Composable(Screen1)

Step 3: Button

Step 4: Composable(Screen2)

State Change - Re-render

Trigger:User taps the 'Go to Screen 2' button on Screen1

Before

Current screen is Screen1 showing welcome text and button

→

After

Current screen changes to Screen2 showing welcome text for Screen2

Re-renders:The NavHost re-renders to display the composable for Screen2

UI Quiz - 3 Questions

What happens when the user taps the button on Screen1?

A The button text changes to 'Clicked'

B The app navigates to Screen2 and shows its content

C The app closes

D Nothing happens

Key Insight

Using a NavHost with a navigation graph lets you easily switch between different composable screens. Buttons can trigger navigation actions to move users through your app smoothly. Organizing UI elements in Columns or Rows helps create clear layouts for each screen.

Practice

1. What is the main purpose of NavController in Jetpack Compose navigation?

easy

A. To create UI elements inside a composable

B. To handle database operations

C. To manage navigation between composable screens

D. To style composables with themes

Solution

1. Step 1: Understand the role of NavController

   NavController is responsible for controlling navigation actions between composables in an app.

2. Step 2: Differentiate from other components

   It does not create UI elements, handle databases, or style components; those are handled by other parts of Compose or Android.

3. Final Answer:

   To manage navigation between composable screens -> Option C

4. Quick Check:

   NavController manages navigation [OK]

Hint: NavController controls screen changes in Compose [OK]

Common Mistakes:

• Confusing NavController with UI creation
• Thinking NavController handles data or styling
• Mixing NavController with ViewModel

2. Which of the following is the correct syntax to navigate to a composable with route "profile" using NavController named navController?

easy

A. navController.navigate("profile")

B. navController.goTo("profile")

C. navController.move("profile")

D. navController.open("profile")

Solution

1. Step 1: Recall the navigation method

   The correct method to navigate is navigate() on NavController.

2. Step 2: Check method names

   Only navigate() is valid; others like goTo(), move(), or open() do not exist.

3. Final Answer:

   navController.navigate("profile") -> Option A

4. Quick Check:

   Use navigate() to change screens [OK]

Hint: Use navigate() method on NavController [OK]

Common Mistakes:

• Using non-existent methods like goTo or move
• Forgetting to pass route as a string
• Calling navigation on wrong object

3. Given this code snippet inside a composable:

val navController = rememberNavController()
Button(onClick = { navController.navigate("details") }) {
  Text("Go to Details")
}

What happens when the button is clicked?

medium

A. The app navigates to the composable with route "details"

B. The app closes immediately

C. Nothing happens because navigate() is incorrect

D. The app crashes due to missing NavHost

Solution

1. Step 1: Understand the button's onClick action

   The button calls navController.navigate("details") which triggers navigation to the "details" route.

2. Step 2: Consider NavHost presence

   Assuming NavHost is set up correctly with "details" route, navigation will succeed and show that screen.

3. Final Answer:

   The app navigates to the composable with route "details" -> Option A

4. Quick Check:

   Button triggers navigate() to details [OK]

Hint: Button click calls navigate() to change screen [OK]

Common Mistakes:

• Assuming navigate() does nothing
• Confusing navigation with app closing
• Ignoring NavHost setup requirement

4. Consider this code snippet:

navController.navigate("home")
navController.popBackStack()

What is the likely problem here?

medium

A. popBackStack() is not a valid NavController method

B. Calling popBackStack() immediately after navigate() may prevent navigation

C. navigate() requires a NavHost to be null

D. No problem; this code navigates then goes back correctly

Solution

1. Step 1: Analyze the sequence of calls

   Calling navigate("home") pushes a new screen, but immediately calling popBackStack() removes the top screen.

2. Step 2: Understand effect on navigation

   This means the navigation to "home" is undone immediately, so user may not see the new screen.

3. Final Answer:

   Calling popBackStack() immediately after navigate() may prevent navigation -> Option B

4. Quick Check:

   popBackStack() right after navigate() cancels navigation [OK]

Hint: Don't popBackStack() right after navigate() [OK]

Common Mistakes:

• Thinking popBackStack() is invalid
• Assuming navigation always succeeds despite popBackStack()
• Ignoring call order effects

5. You want to navigate from a composable "list" to "details/{itemId}" passing an item ID as argument. Which code correctly navigates to details screen with itemId = 42?

hard

A. navController.navigate("details/{itemId}")

B. navController.navigate("details")

C. navController.navigate("details?itemId=42")

D. navController.navigate("details/42")

Solution

1. Step 1: Understand route parameter usage

   When route has a placeholder like "details/{itemId}", you replace {itemId} with actual value in the route string.

2. Step 2: Check each option

   navController.navigate("details/42") correctly replaces {itemId} with 42. navController.navigate("details") misses the parameter. navController.navigate("details?itemId=42") uses query syntax which is not standard here. navController.navigate("details/{itemId}") uses the placeholder literally, which won't work.

3. Final Answer:

   navController.navigate("details/42") -> Option D

4. Quick Check:

   Replace {itemId} with actual value in route [OK]

Hint: Replace placeholders with actual values in route string [OK]

Common Mistakes:

• Passing route with placeholder instead of value
• Using query parameters incorrectly
• Omitting required route arguments