Drawer Navigator in React Native - Practice Problems & Coding Challenges

Challenge - 5 Problems

❓ ui_behavior

intermediate

What happens when you tap a drawer item?

In a React Native app using Drawer Navigator, what is the expected behavior when a user taps on a drawer item?

A The app crashes because drawer items cannot be tapped.

B The app navigates to the screen linked to that drawer item and closes the drawer.

C The drawer stays open and the app reloads the current screen.

D The drawer closes but the app does not change screens.

💡 Hint

Think about what a menu in a real app does when you pick an option.

Tapping a drawer item should navigate to the linked screen and close the drawer, just like choosing a menu option in a real app.

❓ lifecycle

intermediate

When is the drawer content rendered?

In React Navigation's Drawer Navigator, when is the drawer content component rendered?

A Only when the drawer is closed.

B Only when the drawer is opened by the user.

C Every time the user navigates to a new screen.

D Once when the app starts and stays mounted in memory.

💡 Hint

Think about performance and user experience for menus.

The drawer content is mounted once and stays in memory to allow quick opening without delay.

❓ navigation

advanced

How to programmatically open the drawer?

Which code snippet correctly opens the drawer programmatically in a React Native app using Drawer Navigator?

React Native

function MyScreen({ navigation }) {
  // What code opens the drawer?
}

A navigation.openDrawer();

B navigation.showDrawer();

C navigation.toggleDrawer(true);

D navigation.navigate('DrawerOpen');

💡 Hint

Check the official React Navigation docs for drawer methods.

The method openDrawer() is the official way to open the drawer programmatically.

📝 Syntax

advanced

Identify the correct Drawer Navigator setup

Which code snippet correctly sets up a Drawer Navigator with two screens named Home and Profile?

React Native

import { createDrawerNavigator } from '@react-navigation/drawer';
import HomeScreen from './HomeScreen';
import ProfileScreen from './ProfileScreen';

const Drawer = createDrawerNavigator();

function MyDrawer() {
  return (
    // Fill in the drawer navigator
  );
}

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

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

C return (<Drawer><Screen name="Home" component={HomeScreen} /><Screen name="Profile" component={ProfileScreen} /></Drawer>);

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

💡 Hint

Remember the exact component names from the library.

Drawer.Navigator and Drawer.Screen are the correct components. Screen alone is not imported from drawer.

🔧 Debug

expert

Why does the drawer not open on swipe?

You implemented a Drawer Navigator but swiping from the screen edge does not open the drawer. What is the most likely cause?

A The drawer navigator is missing the initialRouteName prop.

B You forgot to import React in your component file.

C The gestureHandlerRootHOC wrapper is missing around the app root.

D You used Stack Navigator instead of Drawer Navigator.

💡 Hint

Swipe gestures require special setup in React Native.

React Navigation's drawer gestures need react-native-gesture-handler setup, including wrapping the app root with gestureHandlerRootHOC.

Practice

1. What is the main purpose of a Drawer Navigator in React Native?

easy

A. To create a side menu for switching between screens easily

B. To handle API requests in the app

C. To style components with CSS

D. To manage app state globally

Solution

1. Step 1: Understand Drawer Navigator role

   A Drawer Navigator provides a side menu that lets users switch screens easily.

2. Step 2: Compare with other options

   The other options relate to API requests, styling components, and global state management, not navigation menus.

3. Final Answer:

   To create a side menu for switching between screens easily -> Option A

4. Quick Check:

   Drawer Navigator = Side menu navigation [OK]

Hint: Drawer Navigator = side menu for screen switching [OK]

Common Mistakes:

• Confusing Drawer Navigator with state management
• Thinking it styles components
• Mixing it up with API handling

2. Which of the following is the correct way to add a screen named 'Home' to a Drawer Navigator?

easy

A.

B.

C.

D.

Solution

1. Step 1: Check required props for Drawer.Screen

   Drawer.Screen needs a 'name' and a 'component' prop to work correctly.

2. Step 2: Validate each option

   <Drawer.Screen name="Home" component={HomeScreen} /> correctly uses both 'name' and 'component'. The other options miss one or both props.

3. Final Answer:

   <Drawer.Screen name="Home" component={HomeScreen} /> -> Option C

4. Quick Check:

   Drawer.Screen requires name and component [OK]

Hint: Drawer.Screen needs both name and component props [OK]

Common Mistakes:

• Omitting the 'name' prop
• Omitting the 'component' prop
• Using incorrect JSX syntax

3. Given this code snippet, what will happen when the app runs?

import { NavigationContainer } from '@react-navigation/native';
import { createDrawerNavigator } from '@react-navigation/drawer';
import HomeScreen from './HomeScreen';
import ProfileScreen from './ProfileScreen';

const Drawer = createDrawerNavigator();

export default function App() {
  return (
    
      
        
        
      
    
  );
}

medium

A. The app crashes because NavigationContainer is missing

B. The app shows a side menu with Home and Profile screens to switch between

C. Only the Home screen is shown without a menu

D. The drawer menu appears but screens are not accessible

Solution

1. Step 1: Check NavigationContainer usage

   The code wraps Drawer.Navigator inside NavigationContainer, which manages navigation state properly.

2. Step 2: Verify Drawer.Screen setup

   Two screens, Home and Profile, are added correctly to the drawer.

3. Final Answer:

   The app shows a side menu with Home and Profile screens to switch between -> Option B

4. Quick Check:

   NavigationContainer + Drawer.Screen = working drawer menu [OK]

Hint: NavigationContainer wraps Drawer.Navigator for working menu [OK]

Common Mistakes:

• Forgetting NavigationContainer causes errors
• Adding screens outside Drawer.Navigator
• Not providing component prop to Drawer.Screen

4. Identify the error in this Drawer Navigator setup:

const Drawer = createDrawerNavigator();

export default function App() {
  return (
    
      
      
    
  );
}

medium

A. Drawer.Navigator should be inside a View component

B. Drawer.Screen components are missing the 'name' prop

C. HomeScreen and SettingsScreen components are not imported

D. Missing NavigationContainer wrapping the Drawer.Navigator

Solution

1. Step 1: Check for NavigationContainer presence

   The code does not wrap Drawer.Navigator inside NavigationContainer, which is required to manage navigation state.

2. Step 2: Verify other props and imports

   Drawer.Screen components have 'name' and 'component' props, so no issue there. The question does not show imports, but the main error is missing NavigationContainer.

3. Final Answer:

   Missing NavigationContainer wrapping the Drawer.Navigator -> Option D

4. Quick Check:

   NavigationContainer is required to wrap navigators [OK]

Hint: Always wrap Drawer.Navigator in NavigationContainer [OK]

Common Mistakes:

• Forgetting NavigationContainer causes navigation errors
• Assuming Drawer.Navigator works alone
• Ignoring import statements (not shown here)

5. You want to customize the drawer menu to show a custom header and add a logout button at the bottom. Which approach correctly applies this customization in a Drawer Navigator?

hard

A. Use the drawerContent prop on Drawer.Navigator to provide a custom component with header and logout button

B. Add a Drawer.Screen named 'Logout' with a button component

C. Wrap each screen component with a header and logout button manually

D. Use screenOptions to add header and logout button globally

Solution

1. Step 1: Understand drawer customization options

   The drawerContent prop lets you replace the default drawer menu with a custom component where you can add headers and buttons.

2. Step 2: Evaluate other options

   Add a Drawer.Screen named 'Logout' with a button component adds a screen, not a menu button. Wrap each screen component with a header and logout button manually duplicates UI in each screen, not efficient. Use screenOptions to add header and logout button globally controls screen headers, not drawer content.

3. Final Answer:

   Use the drawerContent prop on Drawer.Navigator to provide a custom component with header and logout button -> Option A

4. Quick Check:

   drawerContent prop customizes drawer UI [OK]

Hint: Use drawerContent prop for custom drawer UI [OK]

Common Mistakes:

• Adding logout as a screen instead of drawer content
• Trying to add buttons via screenOptions
• Manually adding UI inside each screen