Nested navigators in React Native - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to import the necessary navigator from React Navigation.

React Native

import { create[1]Navigator } from '@react-navigation/native-stack';

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

ADrawer

BStack

CTab

DSwitch

Attempts:

3 left

💡 Hint

Common Mistakes

Using createTabNavigator instead of createStackNavigator.

Using createDrawerNavigator which is for drawer menus.

The createStackNavigator function is used to create a stack navigator in React Navigation.

2fill in blank

medium

Complete the code to define a nested navigator inside a parent navigator.

React Native

function ParentNavigator() {
  return (
    <Stack.Navigator>
      <Stack.Screen name="Home" component={HomeScreen} />
      <Stack.Screen name="[1]" component={ChildNavigator} />
    </Stack.Navigator>
  );
}

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

ADetails

BProfile

CChildStack

DSettings

Attempts:

3 left

💡 Hint

Common Mistakes

Using a screen name that does not match the nested navigator component.

Using a screen name unrelated to the nested navigator.

The nested navigator is usually given a name like ChildStack to represent the nested stack.

3fill in blank

hard

Fix the error in the nested navigator component declaration.

React Native

const ChildNavigator = () => {
  return (
    <[1].Navigator>
      <[1].Screen name="ChildHome" component={ChildHomeScreen} />
    </[1].Navigator>
  );
};

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

ASwitch

BTab

CDrawer

DStack

Attempts:

3 left

💡 Hint

Common Mistakes

Using Tab or Drawer instead of Stack when the navigator is a stack.

Using undefined navigator object.

The nested navigator uses the Stack object created by createStackNavigator().

4fill in blank

hard

Fill both blanks to correctly nest a Tab navigator inside a Stack navigator.

React Native

const Tab = create[1]Navigator();

function ChildNavigator() {
  return (
    <Tab.[2]>
      <Tab.Screen name="TabHome" component={TabHomeScreen} />
    </Tab.[2]>
  );
}

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

ABottomTab

BNavigator

CScreen

DStack

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'Stack' instead of 'BottomTab' for the tab navigator.

Using 'Screen' instead of 'Navigator' for the wrapper.

The createBottomTabNavigator creates a tab navigator, and Tab.Navigator is the component that wraps the screens.

5fill in blank

hard

Fill all three blanks to correctly set up a nested drawer navigator inside a stack navigator.

React Native

const Drawer = create[1]Navigator();

function ChildNavigator() {
  return (
    <Drawer.[2]>
      <Drawer.[3] name="DrawerHome" component={DrawerHomeScreen} />
    </Drawer.[2]>
  );
}

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

ADrawer

BNavigator

CScreen

DStack

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'Stack' or 'Tab' instead of 'Drawer' for drawer navigator.

Mixing up 'Screen' and 'Navigator' components.

The drawer navigator is created with createDrawerNavigator, wrapped by Drawer.Navigator, and screens are added with Drawer.Screen.

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