Why NavHost and NavController in Android Kotlin? - Purpose & Use Cases

The Big Idea

Discover how to make your app's screen changes smooth and stress-free with NavHost and NavController!

The Scenario

Imagine you have a mobile app with many screens, like a shopping app with Home, Cart, and Profile pages. Without a system to manage moving between these screens, you have to write lots of code to switch screens manually.

The Problem

Manually handling screen changes means writing repetitive code for each button or action. It's easy to make mistakes, like forgetting to pass data or causing the app to crash. It also becomes hard to keep track of where the user is in the app.

The Solution

NavHost and NavController work together to handle screen navigation smoothly. NavHost shows the current screen, and NavController manages moving between screens. This setup reduces errors and makes navigation clear and easy to manage.

Before vs After

✗ Before

startActivity(Intent(this, CartActivity::class.java))

✓ After

findNavController().navigate(R.id.action_home_to_cart)

What It Enables

With NavHost and NavController, you can build apps where users move between screens effortlessly, and your code stays clean and easy to update.

Real Life Example

Think of a food delivery app where you tap on a restaurant, then see the menu, add items to your cart, and finally check out. NavHost and NavController make these screen changes smooth and reliable.

Key Takeaways

Manual screen switching is slow and error-prone.

NavHost displays the current screen in your app.

NavController handles moving between screens safely and simply.