Nested navigators in React Native - Mini App: Build & Ship

Build: Nested Navigators Example

This screen demonstrates how to use nested navigators in a React Native app using React Navigation. The main navigator is a bottom tab navigator with two tabs. The first tab contains a stack navigator with two screens. The second tab is a simple screen.

Target UI

┌─────────────────────────────┐
│ Bottom Tabs: [Home] [Settings] │
├─────────────────────────────┤
│ Home Stack Navigator         │
│ ┌───────────────┐           │
│ │ Home Screen   │           │
│ │ [Go to Details]           │
│ └───────────────┘           │
└─────────────────────────────┘

Use React Navigation with a bottom tab navigator as the main navigator.

The first tab should have a stack navigator with two screens: Home and Details.

The Home screen should have a button to navigate to the Details screen.

The second tab should be a simple Settings screen.

Each screen should display a title and a simple message.

Use functional components and hooks.

Starter Code

React Native

import React from 'react';
import { Button, Text, View } from 'react-native';
import { NavigationContainer } from '@react-navigation/native';
import { createBottomTabNavigator } from '@react-navigation/bottom-tabs';
import { createNativeStackNavigator } from '@react-navigation/native-stack';

const Tab = createBottomTabNavigator();
const Stack = createNativeStackNavigator();

function HomeScreen({ navigation }) {
  return (
    <View style={{ flex: 1, justifyContent: 'center', alignItems: 'center' }}>
      <Text>Home Screen</Text>
      {/* TODO: Add button to navigate to Details screen */}
    </View>
  );
}

function DetailsScreen() {
  return (
    <View style={{ flex: 1, justifyContent: 'center', alignItems: 'center' }}>
      <Text>Details Screen</Text>
    </View>
  );
}

function SettingsScreen() {
  return (
    <View style={{ flex: 1, justifyContent: 'center', alignItems: 'center' }}>
      <Text>Settings Screen</Text>
    </View>
  );
}

function HomeStack() {
  return (
    <Stack.Navigator>
      {/* TODO: Add Home and Details screens here */}
    </Stack.Navigator>
  );
}

export default function App() {
  return (
    <NavigationContainer>
      <Tab.Navigator>
        {/* TODO: Add HomeStack and SettingsScreen as tabs */}
      </Tab.Navigator>
    </NavigationContainer>
  );
}

Task 1

Task 2

Task 3

Solution

React Native

import React from 'react';
import { Button, Text, View } from 'react-native';
import { NavigationContainer } from '@react-navigation/native';
import { createBottomTabNavigator } from '@react-navigation/bottom-tabs';
import { createNativeStackNavigator } from '@react-navigation/native-stack';

const Tab = createBottomTabNavigator();
const Stack = createNativeStackNavigator();

function HomeScreen({ navigation }) {
  return (
    <View style={{ flex: 1, justifyContent: 'center', alignItems: 'center' }}>
      <Text>Home Screen</Text>
      <Button title="Go to Details" onPress={() => navigation.navigate('Details')} />
    </View>
  );
}

function DetailsScreen() {
  return (
    <View style={{ flex: 1, justifyContent: 'center', alignItems: 'center' }}>
      <Text>Details Screen</Text>
    </View>
  );
}

function SettingsScreen() {
  return (
    <View style={{ flex: 1, justifyContent: 'center', alignItems: 'center' }}>
      <Text>Settings Screen</Text>
    </View>
  );
}

function HomeStack() {
  return (
    <Stack.Navigator>
      <Stack.Screen name="Home" component={HomeScreen} />
      <Stack.Screen name="Details" component={DetailsScreen} />
    </Stack.Navigator>
  );
}

export default function App() {
  return (
    <NavigationContainer>
      <Tab.Navigator>
        <Tab.Screen name="HomeTab" component={HomeStack} options={{ title: 'Home' }} />
        <Tab.Screen name="Settings" component={SettingsScreen} />
      </Tab.Navigator>
    </NavigationContainer>
  );
}

We created a bottom tab navigator with two tabs: Home and Settings.

The Home tab contains a stack navigator with two screens: Home and Details.

On the Home screen, we added a button that navigates to the Details screen when pressed.

This setup shows how to nest a stack navigator inside a tab navigator, allowing independent navigation inside the Home tab.

We used functional components and React Navigation hooks for clean and modern code.

Final Result

Completed Screen

┌─────────────────────────────┐
│ Bottom Tabs: [Home] [Settings] │
├─────────────────────────────┤
│ Home Screen                 │
│                             │
│ Home Screen                 │
│ [Go to Details]             │
└─────────────────────────────┘

Tapping 'Go to Details' button navigates to the Details screen inside the Home tab.

Tapping the Settings tab switches to the Settings screen.

Back navigation from Details returns to Home screen.

Stretch Goal

Add icons to the bottom tab navigator using react-native-vector-icons.

💡 Hint

Use the screenOptions prop on Tab.Navigator and the tabBarIcon option to add icons.

Practice

1. What is the main purpose of using nested navigators in a React Native app?

easy

A. To speed up the app's loading time

B. To reduce the app's file size

C. To organize screens into groups for easier navigation management

D. To disable navigation gestures

Solution

1. Step 1: Understand navigator roles

   Nested navigators group related screens inside one navigator to keep navigation organized.

2. Step 2: Identify main benefit

   This grouping makes managing navigation easier and improves user experience.

3. Final Answer:

   To organize screens into groups for easier navigation management -> Option C

4. Quick Check:

   Nested navigators = organize screens [OK]

Hint: Think of nested navigators as folders for screens [OK]

Common Mistakes:

• Confusing nested navigators with performance optimization
• Thinking nested navigators reduce app size
• Assuming nested navigators disable gestures

2. Which of the following is the correct way to include a nested navigator inside a parent navigator in React Native?

easy

A. Wrap the nested navigator inside a View component without adding to parent

B. Use the nested navigator as a screen component inside the parent navigator

C. Call the nested navigator inside a useEffect hook

D. Import the nested navigator but do not add it to the parent navigator

Solution

1. Step 1: Understand navigator nesting

   To nest navigators, you add the nested navigator as a screen inside the parent navigator.

2. Step 2: Check other options

   The other options do not properly register the nested navigator for navigation.

3. Final Answer:

   Use the nested navigator as a screen component inside the parent navigator -> Option B

4. Quick Check:

   Nested navigator = screen in parent [OK]

Hint: Add nested navigator as a screen, not just import it [OK]

Common Mistakes:

• Importing nested navigator but forgetting to add as screen
• Trying to call navigator inside hooks
• Wrapping navigator in View without registering

3. Given this nested navigator setup, what screen will be shown when navigating to 'Profile' from the root navigator?

const RootStack = createStackNavigator();
const HomeStack = createStackNavigator();

function HomeStackScreen() {
  return (
    <HomeStack.Navigator>
      <HomeStack.Screen name="Feed" component={FeedScreen} />
      <HomeStack.Screen name="Profile" component={ProfileScreen} />
    </HomeStack.Navigator>
  );
}

function App() {
  return (
    <NavigationContainer>
      <RootStack.Navigator>
        <RootStack.Screen name="Home" component={HomeStackScreen} />
        <RootStack.Screen name="Settings" component={SettingsScreen} />
      </RootStack.Navigator>
    </NavigationContainer>
  );
}

medium

A. The ProfileScreen inside the HomeStack navigator

B. The SettingsScreen from the RootStack navigator

C. An error because Profile is not a direct screen of RootStack

D. The FeedScreen inside the HomeStack navigator

Solution

1. Step 1: Identify where 'Profile' screen is defined

   'Profile' is a screen inside the HomeStack nested navigator, not directly in RootStack.

2. Step 2: Understand navigation to nested screens

   To navigate to 'Profile', you navigate through 'Home' stack, which contains 'Profile'. So 'ProfileScreen' will show.

3. Final Answer:

   The ProfileScreen inside the HomeStack navigator -> Option A

4. Quick Check:

   Nested screen 'Profile' = HomeStack.ProfileScreen [OK]

Hint: Nested screens show inside their own navigator [OK]

Common Mistakes:

• Assuming nested screens are direct children of root navigator
• Confusing SettingsScreen with ProfileScreen
• Expecting error when navigating nested screens

4. What is wrong with this nested navigator code snippet?

const RootStack = createStackNavigator();
const Tab = createBottomTabNavigator();

function TabNavigator() {
  return (
    <Tab.Navigator>
      <Tab.Screen name="Home" component={HomeScreen} />
      <Tab.Screen name="Profile" component={ProfileScreen} />
    </Tab.Navigator>
  );
}

function App() {
  return (
    <NavigationContainer>
      <RootStack.Navigator>
        <RootStack.Screen name="Tabs" component={TabNavigator} />
        <RootStack.Screen name="Settings" component={SettingsScreen} />
      </RootStack.Navigator>
    </NavigationContainer>
  );
}

// Navigation call:
navigation.navigate('Profile');

medium

A. NavigationContainer is missing

B. TabNavigator should be inside SettingsScreen

C. RootStack.Navigator cannot have TabNavigator as a screen

D. Cannot navigate directly to 'Profile' because it's inside the nested TabNavigator

Solution

1. Step 1: Analyze navigation call

   Calling navigation.navigate('Profile') tries to navigate directly in RootStack, but 'Profile' is inside TabNavigator nested navigator.

2. Step 2: Understand nested navigation rules

   You must navigate to 'Tabs' first, then inside TabNavigator navigate to 'Profile'. Direct navigation to nested screens by name won't work.

3. Final Answer:

   Cannot navigate directly to 'Profile' because it's inside the nested TabNavigator -> Option D

4. Quick Check:

   Nested screen navigation requires parent route [OK]

Hint: Navigate nested screens via parent navigator first [OK]

Common Mistakes:

• Trying to navigate nested screen directly by name
• Placing TabNavigator inside unrelated screen
• Forgetting NavigationContainer

5. You want to create a nested navigator structure where the root navigator is a drawer, and inside one drawer screen you want a stack navigator with multiple screens. Which of the following code snippets correctly nests the stack navigator inside the drawer navigator?

hard

A. Add the stack navigator as a screen component inside the drawer navigator's screens

B. Wrap the drawer navigator inside the stack navigator component

C. Use two separate NavigationContainers for drawer and stack navigators

D. Place the stack navigator outside the NavigationContainer

Solution

1. Step 1: Understand nesting structure

   The drawer navigator is the root, so the stack navigator must be a screen inside the drawer to nest properly.

2. Step 2: Evaluate options

   Add the stack navigator as a screen component inside the drawer navigator's screens correctly nests stack inside drawer by adding it as a screen. The other options break navigation rules or cause errors.

3. Final Answer:

   Add the stack navigator as a screen component inside the drawer navigator's screens -> Option A

4. Quick Check:

   Nested navigator = screen inside parent navigator [OK]

Hint: Put nested navigator as a screen inside parent navigator [OK]

Common Mistakes:

• Wrapping drawer inside stack instead of nesting stack inside drawer
• Using multiple NavigationContainers
• Placing navigators outside NavigationContainer