Bird
Raised Fist0
Android Kotlinmobile~20 mins

Navigation component setup in Android Kotlin - Mini App: Build & Ship

Choose your learning style10 modes available
Build: Main Navigation Screen
This screen demonstrates setting up Android Navigation Component with two simple fragments and navigation between them using a button.
Target UI
---------------------
|    Main Screen     |
|                    |
|  [Go to Second]    |
---------------------

---------------------
|   Second Screen    |
|                    |
|  [Back to Main]    |
---------------------
Create two fragments: MainFragment and SecondFragment.
Set up Navigation Component with a NavHostFragment in the activity layout.
Add navigation graph XML with two destinations: MainFragment and SecondFragment.
Add a button in MainFragment to navigate to SecondFragment.
Add a button in SecondFragment to navigate back to MainFragment.
Starter Code
Android Kotlin
package com.example.navigationdemo

import android.os.Bundle
import androidx.appcompat.app.AppCompatActivity

class MainActivity : AppCompatActivity() {
    override fun onCreate(savedInstanceState: Bundle?) {
        super.onCreate(savedInstanceState)
        setContentView(R.layout.activity_main)
        // TODO: Setup NavHostFragment in activity_main.xml
    }
}

// TODO: Create MainFragment.kt and SecondFragment.kt with basic layouts and buttons
Task 1
Task 2
Task 3
Task 4
Solution
Android Kotlin
package com.example.navigationdemo

import android.os.Bundle
import androidx.appcompat.app.AppCompatActivity

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

// MainFragment.kt
package com.example.navigationdemo

import android.os.Bundle
import android.view.LayoutInflater
import android.view.View
import android.view.ViewGroup
import androidx.fragment.app.Fragment
import androidx.navigation.fragment.findNavController
import com.example.navigationdemo.databinding.FragmentMainBinding

class MainFragment : Fragment() {
    private var _binding: FragmentMainBinding? = null
    private val binding get() = _binding!!

    override fun onCreateView(inflater: LayoutInflater, container: ViewGroup?, savedInstanceState: Bundle?): View {
        _binding = FragmentMainBinding.inflate(inflater, container, false)
        return binding.root
    }

    override fun onViewCreated(view: View, savedInstanceState: Bundle?) {
        super.onViewCreated(view, savedInstanceState)
        binding.buttonGoSecond.setOnClickListener {
            findNavController().navigate(R.id.action_mainFragment_to_secondFragment)
        }
    }

    override fun onDestroyView() {
        super.onDestroyView()
        _binding = null
    }
}

// SecondFragment.kt
package com.example.navigationdemo

import android.os.Bundle
import android.view.LayoutInflater
import android.view.View
import android.view.ViewGroup
import androidx.fragment.app.Fragment
import androidx.navigation.fragment.findNavController
import com.example.navigationdemo.databinding.FragmentSecondBinding

class SecondFragment : Fragment() {
    private var _binding: FragmentSecondBinding? = null
    private val binding get() = _binding!!

    override fun onCreateView(inflater: LayoutInflater, container: ViewGroup?, savedInstanceState: Bundle?): View {
        _binding = FragmentSecondBinding.inflate(inflater, container, false)
        return binding.root
    }

    override fun onViewCreated(view: View, savedInstanceState: Bundle?) {
        super.onViewCreated(view, savedInstanceState)
        binding.buttonBackMain.setOnClickListener {
            findNavController().navigate(R.id.action_secondFragment_to_mainFragment)
        }
    }

    override fun onDestroyView() {
        super.onDestroyView()
        _binding = null
    }
}

// activity_main.xml
<?xml version="1.0" encoding="utf-8"?>
<androidx.constraintlayout.widget.ConstraintLayout xmlns:android="http://schemas.android.com/apk/res/android"
    xmlns:app="http://schemas.android.com/apk/res-auto"
    xmlns:tools="http://schemas.android.com/tools"
    android:layout_width="match_parent"
    android:layout_height="match_parent"
    tools:context=".MainActivity">

    <fragment
        android:id="@+id/nav_host_fragment"
        android:name="androidx.navigation.fragment.NavHostFragment"
        android:layout_width="0dp"
        android:layout_height="0dp"
        app:defaultNavHost="true"
        app:navGraph="@navigation/nav_graph"
        app:layout_constraintTop_toTopOf="parent"
        app:layout_constraintBottom_toBottomOf="parent"
        app:layout_constraintStart_toStartOf="parent"
        app:layout_constraintEnd_toEndOf="parent" />

</androidx.constraintlayout.widget.ConstraintLayout>

// nav_graph.xml
<?xml version="1.0" encoding="utf-8"?>
<navigation xmlns:android="http://schemas.android.com/apk/res/android"
    xmlns:app="http://schemas.android.com/apk/res-auto"
    android:id="@+id/nav_graph"
    app:startDestination="@id/mainFragment">

    <fragment
        android:id="@+id/mainFragment"
        android:name="com.example.navigationdemo.MainFragment"
        android:label="Main Screen">
        <action
            android:id="@+id/action_mainFragment_to_secondFragment"
            app:destination="@id/secondFragment" />
    </fragment>

    <fragment
        android:id="@+id/secondFragment"
        android:name="com.example.navigationdemo.SecondFragment"
        android:label="Second Screen">
        <action
            android:id="@+id/action_secondFragment_to_mainFragment"
            app:destination="@id/mainFragment" />
    </fragment>

</navigation>

// fragment_main.xml
<?xml version="1.0" encoding="utf-8"?>
<FrameLayout xmlns:android="http://schemas.android.com/apk/res/android"
    android:layout_width="match_parent"
    android:layout_height="match_parent"
    android:padding="16dp">

    <Button
        android:id="@+id/buttonGoSecond"
        android:layout_width="wrap_content"
        android:layout_height="wrap_content"
        android:text="Go to Second" />

</FrameLayout>

// fragment_second.xml
<?xml version="1.0" encoding="utf-8"?>
<FrameLayout xmlns:android="http://schemas.android.com/apk/res/android"
    android:layout_width="match_parent"
    android:layout_height="match_parent"
    android:padding="16dp">

    <Button
        android:id="@+id/buttonBackMain"
        android:layout_width="wrap_content"
        android:layout_height="wrap_content"
        android:text="Back to Main" />

</FrameLayout>

This solution sets up the Android Navigation Component with two fragments: MainFragment and SecondFragment.

The activity_main.xml contains a NavHostFragment which hosts the navigation graph defined in nav_graph.xml. This graph defines the two fragments and the actions to navigate between them.

Each fragment has a simple layout with a button. In MainFragment, the button navigates to SecondFragment using findNavController().navigate(). In SecondFragment, the button navigates back to MainFragment.

View binding is used for safe and easy access to views.

This setup follows Android best practices for navigation and keeps UI and navigation logic clean and simple.

Final Result
Completed Screen
---------------------
|    Main Screen     |
|                    |
|  [Go to Second]    |
---------------------

User taps 'Go to Second' button

---------------------
|   Second Screen    |
|                    |
|  [Back to Main]    |
---------------------

User taps 'Back to Main' button

Back to Main Screen
Tap 'Go to Second' button navigates to Second Screen.
Tap 'Back to Main' button navigates back to Main Screen.
Stretch Goal
Add a toolbar with a title that updates based on the current fragment.
💡 Hint
Use NavigationUI.setupActionBarWithNavController() in MainActivity and override onSupportNavigateUp() to handle back navigation.

Practice

(1/5)
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
Recommended

Ready to prove it?

Pass the test and this pattern moves unknown strong while earning +1 Grip toward your certificate.

10 questions~5 mineasy hard