Why navigation manages app flow in Android Kotlin - Test Your Understanding

Practice - 5 Tasks

1fill in blank

easy

Complete the code to navigate from one screen to another using Navigation Component.

Android Kotlin

findNavController().navigate([1])

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

AR.id.action_home_to_detail

BstartActivity(Intent(this, DetailActivity::class.java))

CsetContentView(R.layout.detail)

Dfinish()

Attempts:

3 left

💡 Hint

Common Mistakes

Using startActivity instead of Navigation Component navigation.

Passing layout resource instead of action ID.

Calling finish() which closes the current screen.

Using Navigation Component, you navigate by calling findNavController().navigate() with the action ID defined in navigation graph.

2fill in blank

medium

Complete the code to define a navigation action in the navigation graph XML.

Android Kotlin

<action android:id="@+id/[1]" app:destination="@id/detailFragment" />

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

Ago_detail

Bopen_detail

Cnavigate_to_detail

Daction_home_to_detail

Attempts:

3 left

💡 Hint

Common Mistakes

Using arbitrary names that don't match code references.

Missing the 'action_' prefix.

The action ID must match the one used in code for navigation. It usually follows the pattern action_source_to_destination.

3fill in blank

hard

Fix the error in the code to correctly navigate with arguments.

Android Kotlin

val action = HomeFragmentDirections.[1](userId)
findNavController().navigate(action)

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

AactionHomeToDetail

BnavigateToDetail

CgoToDetail

DopenDetail

Attempts:

3 left

💡 Hint

Common Mistakes

Using incorrect method names that don't exist in directions class.

Not passing required arguments.

When using Safe Args, the generated directions class uses camelCase action names matching the navigation graph action ID.

4fill in blank

hard

Fill both blanks to check if the current destination is the home screen before navigating.

Android Kotlin

if (findNavController().currentDestination?.id == [1]) {
  findNavController().navigate([2])
}

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

AR.id.homeFragment

BR.id.action_home_to_detail

CR.id.detailFragment

DR.id.action_detail_to_home

Attempts:

3 left

💡 Hint

Common Mistakes

Comparing with action IDs instead of fragment IDs.

Using wrong action IDs for navigation.

Check if the current screen is homeFragment by comparing IDs, then navigate using the correct action ID.

5fill in blank

hard

Fill all three blanks to create a navigation graph XML snippet with a start destination and two fragments.

Android Kotlin

<navigation xmlns:android="http://schemas.android.com/apk/res/android"
  xmlns:app="http://schemas.android.com/apk/res-auto"
  app:startDestination="@id/[1]">
  <fragment android:id="@+id/[2]" android:name="com.example.HomeFragment" />
  <fragment android:id="@+id/[3]" android:name="com.example.DetailFragment" />
</navigation>

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

AhomeFragment

CdetailFragment

DmainFragment

Attempts:

3 left

💡 Hint

Common Mistakes

Using the same ID for both fragments.

Setting startDestination to a non-existent fragment.

The start destination is the homeFragment. The two fragments must have unique IDs matching their names.

Practice

1. Why is navigation important in an Android app?
Navigation helps users move between screens smoothly. What is its main purpose?

easy

A. To store user data securely

B. To change the app's color scheme automatically

C. To speed up the app's loading time

D. To control how users move between different screens

Solution

1. Step 1: Understand navigation role

   Navigation manages the flow between screens in an app, guiding users.

2. Step 2: Identify main purpose

   Its main purpose is to control user movement between screens, not visual or data tasks.

3. Final Answer:

   To control how users move between different screens -> Option D

4. Quick Check:

   Navigation = control user movement [OK]

Hint: Navigation controls screen flow, not colors or data [OK]

Common Mistakes:

• Confusing navigation with UI styling
• Thinking navigation speeds up loading
• Mixing navigation with data storage

2. Which Kotlin code snippet correctly starts navigation to a new screen called DetailsFragment using Navigation Component?

easy

A. navigateTo(DetailsFragment())

B. findNavController().navigate(R.id.action_to_detailsFragment)

C. startActivity(Intent(this, DetailsFragment::class.java))

D. openScreen("DetailsFragment")

Solution

1. Step 1: Identify Navigation Component syntax

   Using Navigation Component, navigation is done with findNavController().navigate() and action ID.

2. Step 2: Match correct code

   findNavController().navigate(R.id.action_to_detailsFragment) uses correct method and action ID format for navigation.

3. Final Answer:

   findNavController().navigate(R.id.action_to_detailsFragment) -> Option B

4. Quick Check:

   Navigation Component uses findNavController().navigate() [OK]

Hint: Navigation Component uses findNavController().navigate() [OK]

Common Mistakes:

• Using startActivity instead of Navigation Component
• Calling non-existent navigateTo() method
• Passing string instead of action ID

3. Given this code snippet inside a Fragment:

view.findNavController().navigate(R.id.action_home_to_profile)

What happens when this code runs?

medium

A. The app navigates from Home screen to Profile screen

B. The app crashes due to missing navigation controller

C. Nothing happens because the code is incomplete

D. The app opens a new activity instead of fragment

Solution

1. Step 1: Understand navigate() call

   Calling navigate() with action ID triggers navigation between fragments.

2. Step 2: Identify action meaning

   Action ID 'action_home_to_profile' means moving from Home to Profile screen.

3. Final Answer:

   The app navigates from Home screen to Profile screen -> Option A

4. Quick Check:

   navigate() with action ID changes screen [OK]

Hint: navigate() with action ID moves between screens [OK]

Common Mistakes:

• Assuming code crashes without NavController
• Thinking code does nothing without extra setup
• Confusing fragment navigation with activity launch

4. This code tries to navigate but causes a crash:

view.findNavController().navigate(R.id.action_invalid)

What is the likely cause?

medium

A. The app lacks internet permission

B. The view is null when calling findNavController()

C. The action ID does not exist in navigation graph

D. The fragment is not attached to activity

Solution

1. Step 1: Analyze navigation action ID

   Using an invalid action ID not defined in navigation graph causes crash.

2. Step 2: Rule out other causes

   Null view or fragment issues cause different errors; internet permission unrelated.

3. Final Answer:

   The action ID does not exist in navigation graph -> Option C

4. Quick Check:

   Invalid action ID crashes navigation [OK]

Hint: Check action IDs exist in navigation graph [OK]

Common Mistakes:

• Assuming null view causes this specific crash
• Blaming fragment attachment without evidence
• Confusing permissions with navigation errors

5. You want to ensure users cannot go back to the login screen after successful login using navigation. Which approach manages this app flow correctly?

hard

A. Use popUpTo with inclusive=true to remove login from back stack

B. Call finish() on login fragment after navigation

C. Disable back button in the app globally

D. Navigate to login screen again after logout

Solution

1. Step 1: Understand back stack behavior

   Navigation back stack keeps screens; to prevent back to login, remove it from stack.

2. Step 2: Use popUpTo with inclusive=true

   This removes login screen from back stack, so back button skips it.

3. Step 3: Rule out other options

   finish() is for activities, disabling back globally is bad UX, navigating again doesn't prevent back.

4. Final Answer:

   Use popUpTo with inclusive=true to remove login from back stack -> Option A

5. Quick Check:

   popUpTo inclusive=true manages back stack correctly [OK]

Hint: Use popUpTo inclusive=true to clear unwanted back screens [OK]

Common Mistakes:

• Trying to finish fragments instead of managing back stack
• Disabling back button breaks user experience
• Navigating again doesn't remove previous screens