NavHost and NavController in Android Kotlin

Introduction

NavHost and NavController help your app move between screens smoothly. They keep track of where you are and where you want to go.

When you want to switch between different screens in your app.

When you want to handle back button presses automatically.

When you want to pass data between screens easily.

When you want to keep your navigation organized and simple.

Syntax

Android Kotlin

val navController = findNavController(R.id.nav_host_fragment)

// To navigate to a destination
navController.navigate(R.id.destinationFragment)

NavHost is a container that shows different screens (fragments) inside it.

NavController controls the navigation actions like moving forward or back.

Examples

This moves the app from the current screen to the Profile screen.

Android Kotlin

val navController = findNavController(R.id.nav_host_fragment)
navController.navigate(R.id.profileFragment)

This goes back to the previous screen in the navigation stack.

Android Kotlin

navController.popBackStack()

This navigates with data (itemId) from Home to Details screen using safe args.

Android Kotlin

val action = HomeFragmentDirections.actionHomeToDetails(itemId)
navController.navigate(action)

Sample App

This app has a button on the first screen. When you tap it, the app moves to the second screen using NavController.

Android Kotlin

class MainActivity : AppCompatActivity() {
  override fun onCreate(savedInstanceState: Bundle?) {
    super.onCreate(savedInstanceState)
    setContentView(R.layout.activity_main)

    val navController = findNavController(R.id.nav_host_fragment)

    // Navigate to second screen when button clicked
    val button = findViewById<Button>(R.id.button_navigate)
    button.setOnClickListener {
      navController.navigate(R.id.secondFragment)
    }
  }
}

Important Notes

Always define your navigation graph XML to list all screens and actions.

Use safe args plugin to pass data safely between screens.

NavController handles the back button automatically, so you don't need extra code.

Summary

NavHost shows your app screens inside one container.

NavController moves you between screens and manages back stack.

Use navigation graph XML to organize your app's navigation paths.

Practice

1. What is the main role of NavHost in Android navigation?

easy

A. It displays the current screen inside a container.

B. It handles network requests between screens.

C. It stores user data for the app.

D. It manages background services.

Solution

1. Step 1: Understand NavHost purpose

   NavHost is a container that shows the current screen (fragment) in your app.

2. Step 2: Compare options

   Only It displays the current screen inside a container. correctly describes NavHost's role as a screen container.

3. Final Answer:

   It displays the current screen inside a container. -> Option A

4. Quick Check:

   NavHost = Screen container [OK]

Hint: NavHost is like a window showing your current screen [OK]

Common Mistakes:

• Confusing NavHost with NavController
• Thinking NavHost manages data or services
• Assuming NavHost handles navigation logic

2. Which of the following is the correct way to get a NavController inside a Fragment?

easy

A. val navController = getNavHost()

B. val navController = NavController()

C. val navController = findNavController()

D. val navController = NavigationHost()

Solution

1. Step 1: Recall NavController retrieval method

   In a Fragment, the standard way is to call findNavController() extension function.

2. Step 2: Check other options

   The other options are invalid or do not exist in Android navigation API.

3. Final Answer:

   val navController = findNavController() -> Option C

4. Quick Check:

   Use findNavController() in Fragment [OK]

Hint: Use findNavController() to get NavController in Fragment [OK]

Common Mistakes:

• Trying to instantiate NavController directly
• Using wrong method names like getNavHost()
• Confusing NavHost with NavController

3. Given this code inside a Fragment:

findNavController().navigate(R.id.action_home_to_detail)

What happens when this code runs?

medium

A. The app restarts the Home screen.

B. The app navigates from Home screen to Detail screen.

C. The app closes the current screen.

D. The app shows an error because navigate() needs a string.

Solution

1. Step 1: Understand navigate() usage

   The navigate() method moves the app to the destination defined by the action ID.

2. Step 2: Interpret the action ID

   R.id.action_home_to_detail is an action from Home to Detail screen in navigation graph.

3. Final Answer:

   The app navigates from Home screen to Detail screen. -> Option B

4. Quick Check:

   navigate(actionId) moves between screens [OK]

Hint: navigate() with action ID moves to target screen [OK]

Common Mistakes:

• Thinking navigate() closes or restarts screens
• Assuming navigate() requires a string route
• Confusing action IDs with fragment IDs

4. What is wrong with this code snippet inside a Fragment?

val navController = NavController()
navController.navigate(R.id.action_main_to_settings)

medium

A. NavController must be declared as lateinit var.

B. navigate() requires a string route, not an ID.

C. The action ID is invalid inside a Fragment.

D. NavController cannot be instantiated directly with constructor.

Solution

1. Step 1: Check NavController instantiation

   NavController is obtained via findNavController(), not by calling constructor.

2. Step 2: Validate navigate() usage

   Using an action ID with navigate() is correct; no string needed.

3. Final Answer:

   NavController cannot be instantiated directly with constructor. -> Option D

4. Quick Check:

   NavController is retrieved, not created [OK]

Hint: Never create NavController with constructor; use findNavController() [OK]

Common Mistakes:

• Trying to create NavController with new keyword or constructor
• Confusing action IDs with string routes
• Misunderstanding lateinit usage

5. You want to navigate from Screen A to Screen B and pass a user ID as an argument using NavController. Which approach correctly achieves this?

hard

A. val action = ScreenADirections.actionScreenAToScreenB(userId)
findNavController().navigate(action)

B. findNavController().navigate(R.id.screenB, bundleOf(userId))

C. val navController = NavController()
navController.navigate(R.id.screenB)

D. Use Intent to start Screen B with extras.

Solution

1. Step 1: Understand safe args usage

   Using generated directions class with arguments is the recommended way to pass data safely.

2. Step 2: Compare other options

   Using Intent bypasses the Navigation Component. Passing a bundle without proper key-value pair syntax is invalid. Instantiating NavController directly fails.

3. Final Answer:

   val action = ScreenADirections.actionScreenAToScreenB(userId) findNavController().navigate(action) -> Option A

4. Quick Check:

   Safe args = directions class + navigate(action) [OK]

Hint: Use generated directions class to pass arguments safely [OK]

Common Mistakes:

• Instantiating NavController manually
• Passing arguments without safe args
• Using Intent instead of NavController for navigation