Navigation component setup in Android Kotlin - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is the Navigation Component in Android?

The Navigation Component is a part of Android Jetpack that helps you manage app navigation easily and consistently, handling fragment transactions and back stack automatically.

beginner

Which XML file defines the navigation graph?

The navigation graph is defined in an XML file located in the res/navigation folder, usually named nav_graph.xml. It describes all destinations and actions.

beginner

How do you add the Navigation Component dependencies in your Android project?

Add these dependencies in your app's build.gradle file: implementation "androidx.navigation:navigation-fragment-ktx:2.5.3" implementation "androidx.navigation:navigation-ui-ktx:2.5.3"

beginner

What is the purpose of NavHostFragment?

NavHostFragment is a container that hosts navigation destinations (fragments). It swaps fragments as you navigate through the app.

beginner

How do you trigger navigation to another fragment in Kotlin code?

Use the NavController to navigate, for example: findNavController().navigate(R.id.destinationFragment) This moves to the destination defined in the navigation graph.

Where do you define the navigation graph XML file?

A res/navigation folder

B res/layout folder

C res/values folder

D res/drawable folder

The navigation graph XML file is placed inside the res/navigation folder.

Which class hosts the navigation destinations in your layout?

A ViewPager

B FragmentManager

C Activity

D NavHostFragment

NavHostFragment is the container that hosts navigation destinations (fragments).

How do you navigate to another fragment in Kotlin using Navigation Component?

A findNavController().navigate(R.id.destination)

B startActivity(Intent(this, Destination::class.java))

C fragmentManager.beginTransaction()

D setContentView(R.layout.destination)

You use findNavController().navigate() with the destination ID to navigate between fragments.

Which dependencies are needed for Navigation Component in Kotlin?

A recyclerview and cardview

B appcompat and constraintlayout

C navigation-fragment-ktx and navigation-ui-ktx

D material and lifecycle-extensions

The Navigation Component requires navigation-fragment-ktx and navigation-ui-ktx dependencies.

What does the Navigation Component automatically handle for you?

A Database queries

B Fragment transactions and back stack

C Network requests

D UI animations

Navigation Component manages fragment transactions and back stack automatically.

Explain how to set up the Navigation Component in an Android Kotlin project from scratch.

Think about the files and code needed to make navigation work.

Describe the role of NavHostFragment and NavController in app navigation.

One is a container, the other is a controller.

Practice

1. What is the main purpose of the Navigation component in Android development?

easy

A. To manage screen transitions and navigation paths easily

B. To handle database operations

C. To style UI components

D. To manage network requests

Solution

1. Step 1: Understand Navigation component role

   The Navigation component is designed to simplify moving between screens in an app.

2. Step 2: Compare with other options

   Database, styling, and network are unrelated to navigation tasks.

3. Final Answer:

   To manage screen transitions and navigation paths easily -> Option A

4. Quick Check:

   Navigation component = screen transitions [OK]

Hint: Navigation component = screen changes manager [OK]

Common Mistakes:

• Confusing navigation with database handling
• Thinking it styles UI elements
• Assuming it manages network calls

2. Which XML element is used to define the navigation graph in Android?

easy

A. <navGraph>

B. <navigation>

C. <navHost>

D. <navController>

Solution

1. Step 1: Identify the navigation graph element

   The navigation graph XML uses the <navigation> root element to define screens and paths.

2. Step 2: Check other elements

   <navHost> and <navController> are not XML tags; <navGraph> is incorrect.

3. Final Answer:

   <navigation> -> Option B

4. Quick Check:

   Navigation graph XML uses <navigation> [OK]

Hint: Navigation graph XML root is <navigation> tag [OK]

Common Mistakes:

• Using <navGraph> which is invalid
• Confusing NavHostFragment with XML tag
• Mistaking NavController for XML element

3. Given this code snippet, what screen will be displayed first?

<navigation xmlns:android="http://schemas.android.com/apk/res/android"
    android:id="@+id/nav_graph"
    app:startDestination="@id/homeFragment">

    <fragment
        android:id="@+id/homeFragment"
        android:name="com.example.HomeFragment" />

    <fragment
        android:id="@+id/detailFragment"
        android:name="com.example.DetailFragment" />

</navigation>

medium

A. No screen shown

B. DetailFragment

C. HomeFragment

D. Error due to missing NavHostFragment

Solution

1. Step 1: Identify startDestination attribute

   The navigation graph sets startDestination="@id/homeFragment", so HomeFragment is the first screen.

2. Step 2: Confirm fragment IDs

   HomeFragment and DetailFragment are defined; startDestination points to HomeFragment.

3. Final Answer:

   HomeFragment -> Option C

4. Quick Check:

   startDestination = HomeFragment [OK]

Hint: Look for startDestination attribute in navigation XML [OK]

Common Mistakes:

• Choosing DetailFragment by mistake
• Assuming no screen shows without NavHostFragment
• Confusing fragment IDs

4. You wrote this code to navigate but get a crash:

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

What is the most likely cause?

medium

A. All of the above

B. Incorrect action ID in navigation graph

C. Using findNavController() outside a Fragment or Activity

D. Missing NavHostFragment in layout

Solution

1. Step 1: Check NavHostFragment presence

   Without NavHostFragment in layout, navigation cannot work and causes crash.

2. Step 2: Verify action ID and context

   If action ID is wrong or findNavController() is called outside proper context, app crashes.

3. Final Answer:

   All of the above -> Option A

4. Quick Check:

   Missing NavHost, wrong ID, or wrong context cause crash [OK]

Hint: Check NavHost, action ID, and context if navigation crashes [OK]

Common Mistakes:

• Ignoring NavHostFragment setup
• Using wrong action ID
• Calling findNavController() in wrong place

5. You want to navigate from HomeFragment to DetailFragment using the Navigation component. Which steps are required to set this up correctly?

hard

A. Only add NavHostFragment in layout and call navigate() in code

B. Add action in nav_graph.xml and call navigate() without defining fragments

C. Define fragments in nav_graph.xml and call navigate() without NavHostFragment

D. Define fragments and action in nav_graph.xml, add NavHostFragment in layout, call findNavController().navigate(actionId)

Solution

1. Step 1: Define fragments and action in navigation graph

   Both fragments and the action connecting them must be declared in nav_graph.xml.

2. Step 2: Add NavHostFragment in activity layout

   NavHostFragment hosts the navigation and displays fragments.

3. Step 3: Use findNavController().navigate(actionId) in code

   This triggers navigation along the defined action.

4. Final Answer:

   Define fragments and action in nav_graph.xml, add NavHostFragment in layout, call findNavController().navigate(actionId) -> Option D

5. Quick Check:

   Fragments + action + NavHost + navigate() = correct setup [OK]

Hint: All three: graph, NavHost, and navigate() needed [OK]

Common Mistakes:

• Skipping NavHostFragment in layout
• Not defining action in nav_graph.xml
• Calling navigate() without proper setup