Why Bottom navigation bar in Android Kotlin? - Purpose & Use Cases

The Big Idea

What if your app's navigation could be as easy as tapping icons at the bottom of the screen?

The Scenario

Imagine you have an app with many sections, and you want users to switch between them easily. Without a bottom navigation bar, you might add buttons scattered around or use complicated menus that confuse users.

The Problem

Manually managing navigation with separate buttons or menus can be slow to build and hard to keep consistent. Users might get lost, and developers spend too much time handling navigation logic and UI updates.

The Solution

The Bottom navigation bar provides a simple, consistent way to let users switch between main sections of your app with just one tap. It handles the UI and navigation smoothly, making your app easier to use and develop.

Before vs After

✗ Before

button1.setOnClickListener { showSection1() }
button2.setOnClickListener { showSection2() }

✓ After

bottomNavigationView.setOnItemSelectedListener { item ->
  when(item.itemId) {
    R.id.home -> showHome()
    R.id.profile -> showProfile()
  }
  true
}

What It Enables

It enables fast, intuitive switching between app sections with a clean, familiar interface at the bottom of the screen.

Real Life Example

Think of apps like Instagram or YouTube, where the bottom navigation bar lets you quickly jump between Home, Search, and Profile without confusion.

Key Takeaways

Manual navigation can be confusing and hard to maintain.

Bottom navigation bar offers a simple, consistent way to switch sections.

It improves user experience and speeds up development.

Practice

1. What is the main purpose of a BottomNavigationView in an Android app?

easy

A. To let users switch between main sections of the app easily

B. To display a list of notifications

C. To show a full-screen image gallery

D. To handle background tasks

Solution

1. Step 1: Understand BottomNavigationView role

   The BottomNavigationView is designed to provide quick navigation between top-level views in an app.

2. Step 2: Compare options with its purpose

   Options B, C, and D describe unrelated features like notifications, image galleries, or background tasks.

3. Final Answer:

   To let users switch between main sections of the app easily -> Option A

4. Quick Check:

   BottomNavigationView = Easy app section switching [OK]

Hint: BottomNavigationView is for main app section navigation [OK]

Common Mistakes:

• Confusing BottomNavigationView with notification or image display
• Thinking it handles background processes
• Assuming it is a full-screen component

2. Which of the following is the correct way to set a listener for item selection on a BottomNavigationView in Kotlin?

easy

A. bottomNav.setOnClickListener { item -> true }

B. bottomNav.setOnItemSelectedListener { item -> true }

C. bottomNav.setOnItemClickListener { item -> true }

D. bottomNav.setOnItemSelected { item -> true }

Solution

1. Step 1: Recall BottomNavigationView listener method

   The correct method to listen for item selection is setOnItemSelectedListener.

2. Step 2: Check method names in options

   Options A, C, and D use incorrect method names not defined for BottomNavigationView.

3. Final Answer:

   bottomNav.setOnItemSelectedListener { item -> true } -> Option B

4. Quick Check:

   Listener method = setOnItemSelectedListener [OK]

Hint: Use setOnItemSelectedListener for BottomNavigationView [OK]

Common Mistakes:

• Using setOnClickListener instead of setOnItemSelectedListener
• Confusing with setOnItemClickListener (not valid here)
• Misspelling the listener method name

3. Given this Kotlin code snippet for a BottomNavigationView listener:

bottomNav.setOnItemSelectedListener { item ->
  when(item.itemId) {
    R.id.home -> { showHome(); true }
    R.id.search -> { showSearch(); true }
    else -> false
  }
}

What happens when the user taps the "search" item?

medium

A. The app crashes due to missing case

B. The showHome() function is called instead

C. Nothing happens because the listener returns false

D. The showSearch() function is called and the tap is handled

Solution

1. Step 1: Analyze the when block for itemId

   When the itemId is R.id.search, the code calls showSearch() and returns true.

2. Step 2: Understand return value meaning

   Returning true means the tap event is handled properly, so showSearch() runs.

3. Final Answer:

   The showSearch() function is called and the tap is handled -> Option D

4. Quick Check:

   ItemId search triggers showSearch() [OK]

Hint: Return true after handling item to confirm tap handled [OK]

Common Mistakes:

• Assuming else case runs for known items
• Thinking returning false still triggers action
• Confusing itemId values

4. What is wrong with this Kotlin code for BottomNavigationView listener?

bottomNav.setOnItemSelectedListener { item ->
  when(item.itemId) {
    R.id.home -> showHome()
    R.id.profile -> showProfile()
  }
}

medium

A. The listener should be set with setOnClickListener instead

B. Using when instead of if-else is incorrect here

C. Missing return value for the lambda, causing a type mismatch error

D. The itemId values are invalid identifiers

Solution

1. Step 1: Check lambda return type requirement

   The listener expects a Boolean return indicating if the tap was handled.

2. Step 2: Identify missing return statements

   The when cases call functions but do not return true or false, causing a type mismatch.

3. Final Answer:

   Missing return value for the lambda, causing a type mismatch error -> Option C

4. Quick Check:

   Listener lambda must return Boolean [OK]

Hint: Always return true or false in setOnItemSelectedListener lambda [OK]

Common Mistakes:

• Forgetting to return true after handling item
• Using setOnClickListener instead of setOnItemSelectedListener
• Ignoring compiler errors about return type

5. You want to create a BottomNavigationView with 4 items: Home, Search, Profile, and Settings. Which practice should you follow to ensure best usability?

hard

A. Use exactly 4 items and provide clear icons and labels for each

B. Add 6 items to show more options at once

C. Use only icons without labels to save space

D. Place the BottomNavigationView at the top of the screen

Solution

1. Step 1: Recall BottomNavigationView usability guidelines

   Best practice is to have between 3 and 5 items with clear icons and labels.

2. Step 2: Evaluate options against guidelines

   Add 6 items to show more options at once exceeds recommended items; C removes labels which hurts clarity; D places it incorrectly at top.

3. Final Answer:

   Use exactly 4 items and provide clear icons and labels for each -> Option A

4. Quick Check:

   3-5 items with icons and labels = best practice [OK]

Hint: Keep 3-5 items with icons and labels for BottomNavigationView [OK]

Common Mistakes:

• Adding too many items causing clutter
• Removing labels making navigation unclear
• Placing BottomNavigationView at top instead of bottom