Navigation component setup in Android Kotlin - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to set up the NavController in an Activity.

Android Kotlin

val navController = findNavController([1])

Drag options to blanks, or click blank then click option'

Athis

BR.layout.activity_main

CsupportFragmentManager

DR.id.nav_host_fragment

Attempts:

3 left

💡 Hint

Common Mistakes

Using layout resource ID instead of fragment ID.

Passing the Activity context instead of fragment ID.

The NavController is obtained by calling findNavController with the ID of the NavHostFragment, which is R.id.nav_host_fragment.

2fill in blank

medium

Complete the code to navigate to the destination fragment using NavController.

Android Kotlin

navController.[1](R.id.destinationFragment)

Drag options to blanks, or click blank then click option'

Anavigate

BpopBackStack

CsetGraph

DaddOnDestinationChangedListener

Attempts:

3 left

💡 Hint

Common Mistakes

Using popBackStack to go forward.

Trying to set the graph instead of navigating.

To move to another fragment, use navigate with the destination ID.

3fill in blank

hard

Fix the error in the code to correctly set up the NavHostFragment in the Activity's layout.

Android Kotlin

<fragment
    android:id="@+id/nav_host_fragment"
    android:name="[1]"
    android:layout_width="match_parent"
    android:layout_height="match_parent"
    app:navGraph="@navigation/nav_graph"
    app:defaultNavHost="true" />

Drag options to blanks, or click blank then click option'

Aandroidx.navigation.NavController

Bandroidx.fragment.app.Fragment

Candroidx.navigation.fragment.NavHostFragment

Dandroidx.navigation.NavGraph

Attempts:

3 left

💡 Hint

Common Mistakes

Using Fragment or NavController instead of NavHostFragment.

Omitting the android:name attribute.

The android:name attribute must specify androidx.navigation.fragment.NavHostFragment to host the navigation graph.

4fill in blank

hard

Fill both blanks to create a NavOptions object that animates navigation transitions.

Android Kotlin

val options = NavOptions.Builder()
    .setEnterAnim([1])
    .setExitAnim([2])
    .build()

Drag options to blanks, or click blank then click option'

AR.anim.slide_in_right

BR.anim.fade_out

CR.anim.slide_out_left

DR.anim.fade_in

Attempts:

3 left

💡 Hint

Common Mistakes

Mixing fade and slide animations incorrectly.

Using the same animation for enter and exit.

Use slide_in_right for entering and slide_out_left for exiting animations to create smooth transitions.

5fill in blank

hard

Fill all three blanks to create a safe args bundle and navigate with arguments.

Android Kotlin

val action = NavGraphDirections.actionToDetailFragment([1] = userId)
navController.[2](action, [3])

Drag options to blanks, or click blank then click option'

AuserId

Bnavigate

Cnull

DbundleOf()

Attempts:

3 left

💡 Hint

Common Mistakes

Passing the wrong argument name.

Using bundleOf() instead of null when no options are needed.

Pass the userId as argument, use navigate to move, and null for NavOptions if none are needed.

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