Bird
Raised Fist0
React Nativemobile~20 mins

Custom tab bars in React Native - Practice Problems & Coding Challenges

Choose your learning style10 modes available
Challenge - 5 Problems
🎖️
Custom Tab Bar Master
Get all challenges correct to earn this badge!
Test your skills under time pressure!
❓ ui_behavior
intermediate
2:00remaining
Custom Tab Bar Button Behavior
You have a custom tab bar in React Native. Which option correctly changes the tab when a custom button is pressed?
React Native
function CustomTabBar({ state, navigation }) {
  return (
    <View style={{ flexDirection: 'row' }}>
      {state.routes.map((route, index) => (
        <TouchableOpacity
          key={route.key}
          onPress={() => {
            // What should go here?
          }}
        >
          <Text>{route.name}</Text>
        </TouchableOpacity>
      ))}
    </View>
  );
}
Anavigation.goBack(route.name)
Bnavigation.navigate(route.name)
Cnavigation.push(route.name)
Dnavigation.popToTop(route.name)
Attempts:
2 left
💡 Hint
Think about how to switch tabs by name using navigation.
📝 Syntax
intermediate
2:00remaining
Correct JSX for Custom Tab Bar
Which option correctly renders a custom tab bar with accessible buttons in React Native?
React Native
function CustomTabBar({ state, navigation }) {
  return (
    <View style={{ flexDirection: 'row' }}>
      {state.routes.map((route, index) => (
        // Fill in the correct JSX here
      ))}
    </View>
  );
}
A<Button key={route.key} title={route.name} onPress={navigation.navigate(route.name)} />
B<View key={route.key} onPress={() => navigation.navigate(route.name)}><Text>{route.name}</Text></View>
C<TouchableOpacity key={route.key} accessibilityRole="button" onPress={() => navigation.navigate(route.name)}><Text>{route.name}</Text></TouchableOpacity>
D<TouchableHighlight key={route.key} onPress={navigation.navigate(route.name)}><Text>{route.name}</Text></TouchableHighlight>
Attempts:
2 left
💡 Hint
TouchableOpacity supports onPress and accessibilityRole for buttons.
❓ lifecycle
advanced
2:00remaining
Updating Custom Tab Bar on Navigation State Change
In a custom tab bar component, which React hook ensures the tab bar updates when the navigation state changes?
React Native
function CustomTabBar({ state, navigation }) {
  // Which hook to use here?
  return <View>{/* tab buttons */}</View>;
}
AuseEffect(() => { /* update UI */ }, [state.index])
BuseRef(() => { /* update UI */ }, [state.index])
CuseCallback(() => { /* update UI */ }, [])
DuseMemo(() => { /* update UI */ }, [])
Attempts:
2 left
💡 Hint
You want to run code when the selected tab index changes.
❓ navigation
advanced
2:00remaining
Handling Tab Press with Custom Behavior
You want to run custom code before switching tabs in a custom tab bar. Which option correctly intercepts the tab press event?
React Native
function CustomTabBar({ state, navigation }) {
  return (
    <View style={{ flexDirection: 'row' }}>
      {state.routes.map((route, index) => {
        const isFocused = state.index === index;
        return (
          <TouchableOpacity
            key={route.key}
            onPress={() => {
              // Custom code here
            }}
          >
            <Text>{route.name}</Text>
          </TouchableOpacity>
        );
      })}
    </View>
  );
}
Anavigation.goBack(); navigation.emit({ type: 'tabPress', target: route.key });
Bnavigation.navigate(route.name); navigation.emit({ type: 'tabPress', target: route.key });
Cnavigation.dispatch({ type: 'tabPress', target: route.key }); navigation.navigate(route.name);
Dconst event = navigation.emit({ type: 'tabPress', target: route.key, canPreventDefault: true }); if (!event.defaultPrevented) navigation.navigate(route.name);
Attempts:
2 left
💡 Hint
Emit tabPress event and check if default was prevented before navigating.
🧠 Conceptual
expert
2:00remaining
Why Use Custom Tab Bars Instead of Default?
What is the main reason developers create custom tab bars in React Native apps?
ATo fully control the tab bar appearance and behavior beyond default styles
BBecause default tab bars do not support navigation
CTo improve app performance by avoiding built-in components
DBecause custom tab bars automatically handle accessibility without extra work
Attempts:
2 left
💡 Hint
Think about customization needs beyond what default tab bars offer.

Practice

(1/5)
1. What is the main purpose of a custom tab bar in React Native navigation?
easy
A. To replace the entire navigation stack with a new one
B. To disable navigation between screens
C. To create a personalized look and behavior for the bottom navigation tabs
D. To automatically fetch data for each tab

Solution

  1. Step 1: Understand what a tab bar does

    A tab bar shows navigation options at the bottom of the screen for switching between views.
  2. Step 2: Identify the role of a custom tab bar

    A custom tab bar lets you change how these tabs look and behave, instead of using the default style.
  3. Final Answer:

    To create a personalized look and behavior for the bottom navigation tabs -> Option C
  4. Quick Check:

    Custom tab bar = personalized navigation UI [OK]
Hint: Custom tab bars change appearance and interaction of bottom tabs [OK]
Common Mistakes:
  • Thinking it replaces navigation logic entirely
  • Assuming it disables navigation
  • Confusing it with data fetching
2. Which React Native component is commonly used to make a tab clickable in a custom tab bar?
easy
A. View
B. TouchableOpacity
C. TextInput
D. ScrollView

Solution

  1. Step 1: Identify clickable components

    TouchableOpacity is designed to respond to touch events and provide feedback.
  2. Step 2: Match with tab interaction needs

    Tabs need to be clickable to switch screens, so TouchableOpacity is the right choice.
  3. Final Answer:

    TouchableOpacity -> Option B
  4. Quick Check:

    Clickable tab = TouchableOpacity [OK]
Hint: Use TouchableOpacity for clickable tabs in React Native [OK]
Common Mistakes:
  • Using View which is not clickable by default
  • Choosing TextInput which is for text input
  • Using ScrollView which is for scrolling content
3. Given this snippet inside a custom tab bar component:
state.index === 1 ? 'blue' : 'gray'
What does this expression do?
medium
A. Causes a syntax error because of missing parentheses
B. Always sets the tab color to gray
C. Changes the tab color to blue when the app starts
D. Sets the tab color to blue if it is the active tab, otherwise gray

Solution

  1. Step 1: Understand the ternary expression

    The expression checks if state.index equals 1; if true, it returns 'blue', else 'gray'.
  2. Step 2: Relate to tab color logic

    This means the tab at index 1 is highlighted blue when active, others are gray.
  3. Final Answer:

    Sets the tab color to blue if it is the active tab, otherwise gray -> Option D
  4. Quick Check:

    state.index === 1 ? 'blue' : 'gray' = active tab color logic [OK]
Hint: Ternary ? : chooses color based on active tab index [OK]
Common Mistakes:
  • Thinking it always returns gray
  • Assuming it causes syntax error
  • Confusing the condition with app start
4. Identify the error in this custom tab bar code snippet:
const CustomTabBar = ({ state, navigation }) => {
  return (
    <View>
      {state.routes.map((route, index) => (
        <TouchableOpacity
          key={index}
          onPress={() => navigation.navigate(route.name)}
        >
          <Text>{route.name}</Text>
        </TouchableOpacity>
      ))}
    </View>
  );
};
medium
A. Missing accessibility props for TouchableOpacity
B. Using index as key causes navigation errors
C. Incorrect use of navigation.navigate inside onPress
D. No error, code works correctly

Solution

  1. Step 1: Review accessibility best practices

    TouchableOpacity should have accessibilityRole and accessibilityState for screen readers.
  2. Step 2: Check other parts of code

    Using index as key is not ideal but won't cause navigation errors; navigation.navigate usage is correct.
  3. Final Answer:

    Missing accessibility props for TouchableOpacity -> Option A
  4. Quick Check:

    Accessibility props missing = error [OK]
Hint: Always add accessibilityRole and accessibilityState to touchables [OK]
Common Mistakes:
  • Ignoring accessibility props
  • Thinking index key breaks navigation
  • Assuming navigation.navigate is wrong here
5. You want to create a custom tab bar that highlights the active tab with a bold label and changes the icon color. Which approach correctly uses state and navigation to achieve this?
hard
A. Use state.index to check active tab, and navigation.navigate(route.name) on press; style label bold if active
B. Use navigation.state.index to check active tab, and state.navigate(route.name) on press; style label bold if active
C. Use state.activeTab to check active tab, and navigation.goBack() on press; style label bold if active
D. Use state.index to check active tab, and navigation.push(route.key) on press; style label bold if active

Solution

  1. Step 1: Identify correct state usage

    The active tab index is in state.index, not navigation.state or state.activeTab.
  2. Step 2: Identify correct navigation method

    navigation.navigate(route.name) is used to switch tabs; goBack or push are not appropriate here.
  3. Step 3: Apply styling based on active tab

    Compare current index with tab index to apply bold style and change icon color.
  4. Final Answer:

    Use state.index to check active tab, and navigation.navigate(route.name) on press; style label bold if active -> Option A
  5. Quick Check:

    state.index + navigation.navigate = correct tab control [OK]
Hint: Use state.index for active tab and navigation.navigate for switching [OK]
Common Mistakes:
  • Using wrong property like navigation.state.index
  • Using navigation.goBack instead of navigate
  • Using state.activeTab which doesn't exist
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