DEV Community

Cover image for Combining Stack, Tab & Drawer Navigations in React Native With React Navigation 5
Ekunola Ezekiel
Ekunola Ezekiel

Posted on • Originally published at blog.ezekielekunola.com

Combining Stack, Tab & Drawer Navigations in React Native With React Navigation 5

#reactnative #react #javascript #tutorial

In this article, we'll be covering the different types of navigations and also how to combine them together in react-native using react-navigation 5.

Table Of Content

Prerequisite

To be able to follow up with this article, you must have the following setup on your local environment

Project Setup

To set up a react-native project, you can make use of the React Native CLI or the Expo CLI.

I would be making use of the Expo CLI to set up a react-native project. To do so, run the following command on your terminal.



npm install -g expo-cli
Enter fullscreen mode Exit fullscreen mode

The above command would install Expo CLI on your machine.

Note: You need to have Node v12 installed on your machine to be able to install Expo CLI using the command line.

After the above command runs successfully, run the command below to generate/create a react-native project. 



expo init project-name
Enter fullscreen mode Exit fullscreen mode

Once the above command runs successfully, open the project in your desired code editor, and run npm start on the terminal to start the application.

To set up a react-native project using the React-Native CLI, check here.

React Navigation Dependencies & Setup

The dependencies below are the core utility used by the navigators to create the navigation structure, as well as our Stack, Tab, and Drawer navigation.

In your project directory, run the command below on your terminal



npm install @react-navigation/native @react-navigation/stack @react-navigation/bottom-tabs @react-navigation/drawer
Enter fullscreen mode Exit fullscreen mode

These dependencies below are the dependency relied upon for gestures, animations, and transitions. Also, run the command below on your terminal to install the dependencies.



npm install react-native-reanimated react-native-gesture-handler react-native-screens react-native-safe-area-context @react-native-community/masked-view
Enter fullscreen mode Exit fullscreen mode

In the root file of our app, in this case, the App.js file, we would set up our react-navigation there.



// ./App.js

import React from "react";
import { NavigationContainer } from "@react-navigation/native";

 const App = () => {
  return <NavigationContainer>{/* Navigation here */}</NavigationContainer>;
}
export default App;
Enter fullscreen mode Exit fullscreen mode

Screens setup

The next step would be to set up screens that would be used in our application.

I would be setting up 3 screens for the purpose of this demo, feel free to just copy them.

So I'd set them up in a screens directory. Create a screens directory in the root of the project and add the components below

Home Screen



// ./screens/Home.js

import React from "react";
import { View, Button, Text, StyleSheet } from "react-native";

const Home = () => {
  return (
    <View style={styles.center}>
      <Text>This is the home screen</Text>
      <Button title="Go to About Screen" />
    </View>
  );
};

const styles = StyleSheet.create({
  center: {
    flex: 1,
    justifyContent: "center",
    alignItems: "center",
    textAlign: "center",
  },
});

export default Home;
Enter fullscreen mode Exit fullscreen mode

About Screen



// ./screens/About.js

import React from "react";
import { View, StyleSheet, Text } from "react-native";

const About = () => {
  return (
    <View style={styles.center}>
      <Text>This is the about screen</Text>
    </View>
  );
};

const styles = StyleSheet.create({
  center: {
    flex: 1,
    justifyContent: "center",
    alignItems: "center",
    textAlign: "center",
  },
});

export default About;
Enter fullscreen mode Exit fullscreen mode

Contact Screen



// ./screens/Contact.js

import React from "react";
import { View, StyleSheet, Text } from "react-native";

const Contact = () => {
  return (
    <View style={styles.center}>
      <Text>This is the contact screen</Text>
    </View>
  );
};

const styles = StyleSheet.create({
  center: {
    flex: 1,
    justifyContent: "center",
    alignItems: "center",
    textAlign: "center",
  },
});

export default Contact;
Enter fullscreen mode Exit fullscreen mode

Stack Navigation

Stack navigation provides a way for react-native apps to transition between screens by using a stack, which means the screens are stacked on each other.

For example, if you navigate from login to signup screen, the signup screen is stacked on top of the login screen, and if you navigate back, the signup screen is then popped off the stack.

To set up the stack navigation, I'd create a navigation directory at the root of our project. Inside our newly created directory, I'd also create a StackNavigator.js file in there, and add our stack navigation setup.

Note: You can decide to name the folders and files however you want



// ./navigation/StackNavigator.js

import React from "react";
import { createStackNavigator } from "@react-navigation/stack";

import Home from "../screens/Home";
import About from "../screens/About";

const Stack = createStackNavigator();

const MainStackNavigator = () => {
  return (
    <Stack.Navigator>
      <Stack.Screen name="Home" component={Home} />
      <Stack.Screen name="About" component={About} />
    </Stack.Navigator>
  );
}

export { MainStackNavigator };
Enter fullscreen mode Exit fullscreen mode

You can also customize and style the stack navigation by adding screenOptions prop style, see basic example below



// ./navigation/StackNavigator.js

const MainStackNavigator = () => {
  return (
    <Stack.Navigator
      screenOptions={{
        headerStyle: {
          backgroundColor: "#9AC4F8",
        },
        headerTintColor: "white",
        headerBackTitle: "Back",
      }}
    >
      <Stack.Screen name="Home" component={Home} />
      <Stack.Screen name="About" component={About} />
    </Stack.Navigator>
  );
}
Enter fullscreen mode Exit fullscreen mode

Back in our App.js file, we can import and add our newly created Stack Navigator. So our App.js file would look like the code below



// ./App.js

import React from "react";
import { NavigationContainer } from "@react-navigation/native";

import { MainStackNavigator } from "./navigation/StackNavigator";

 const App = () => {
  return (
    <NavigationContainer>
      <MainStackNavigator />
    </NavigationContainer>
  );
}
export default App
Enter fullscreen mode Exit fullscreen mode

Now if we run the code on our emulator, We should now see our Home screen rendering on our Stack screens.

Stack Screen

Remember in our ./screens/Home.js file, we had a button that did nothing, but since we have our stack navigation setup, we can now have access to navigation prop injected by the stack navigation which can help us perform many operations, one of which is redirecting.

So navigate to ./screens/Home.js and add the code below.



// ./screens/Home.js

import React from "react";
import { View, Button, Text, StyleSheet } from "react-native";

const Home = ({ navigation }) => {
  return (
    <View style={styles.center}>
      <Text>This is the home screen</Text>
      <Button
        title="Go to About Screen"
        onPress={() => navigation.navigate("About")} // We added an onPress event which would navigate to the About screen
      />
    </View>
  );
};

const styles = StyleSheet.create({
  center: {
    flex: 1,
    justifyContent: "center",
    alignItems: "center",
    textAlign: "center",
  },
});

export default Home;
Enter fullscreen mode Exit fullscreen mode

In the code above, we get the navigation prop, which is an object that has a navigate function which we then call passing in the name of the screen we want to navigate to after the button is pressed.

Stack Navigation

And there we have it, we can now navigate between screens using our stack navigation.

Tab Navigation

Tab navigation is a navigation that is tabbed at either the bottom or top of a screen and can be used to switch between different screens.

Tab navigation can take in either the screen as a component or a Stack as the component.

In our StackNavigator.js file, let's create another stack for our contact screen. So our StackNavigator.js will look like below



// ./navigation/StackNavigator.js

import React from "react";
import { createStackNavigator } from "@react-navigation/stack";

import Home from "../screens/Home";
import About from "../screens/About";
import Contact from "../screens/Contact";

const Stack = createStackNavigator();

const screenOptionStyle = {
  headerStyle: {
    backgroundColor: "#9AC4F8",
  },
  headerTintColor: "white",
  headerBackTitle: "Back",
};

const MainStackNavigator = () => {
  return (
    <Stack.Navigator screenOptions={screenOptionStyle}>
      <Stack.Screen name="Home" component={Home} />
      <Stack.Screen name="About" component={About} />
    </Stack.Navigator>
  );
}

const ContactStackNavigator = () => {
  return (
    <Stack.Navigator screenOptions={screenOptionStyle}>
      <Stack.Screen name="Contact" component={Contact} />
    </Stack.Navigator>
  );
}

export { MainStackNavigator, ContactStackNavigator };
Enter fullscreen mode Exit fullscreen mode

We can then create another file TabNavigator.js in the navigations directory and add the markup for our TabNavigator



// ./navigation/TabNavigator.js

import React from "react";
import { createBottomTabNavigator } from "@react-navigation/bottom-tabs";

import { MainStackNavigator, ContactStackNavigator } from "./StackNavigator";

const Tab = createBottomTabNavigator();

const BottomTabNavigator = () => {
  return (
    <Tab.Navigator>
      <Tab.Screen name="Home" component={MainStackNavigator} />
      <Tab.Screen name="Contact" component={ContactStackNavigator} />
    </Tab.Navigator>
  );
};

export default BottomTabNavigator;
Enter fullscreen mode Exit fullscreen mode

And then back in our App.js file, we can now import our newly created TabNavigator and use it there.



//  ./App.js

import React from "react";
import { NavigationContainer } from "@react-navigation/native";

import BottomTabNavigator from "./navigation/TabNavigator";

 const App = () => {
  return (
    <NavigationContainer>
      <BottomTabNavigator />
    </NavigationContainer>
  );
}
export default App
Enter fullscreen mode Exit fullscreen mode

Tab Navigation

Drawer Navigation

Drawer navigation is a slide-out and slide-in drawer that contains links to various screens. The Drawer navigation opens when a menu icon is clicked or when a user swipes their finger from the left or right edge of the app.

In order to create drawer navigation, we would create another file in our navigations directory called DrawerNavigator.js

In that file, we would add our drawer navigator markup



// ./navigation/DrawerNavigator.js

import React from "react";

import { createDrawerNavigator } from "@react-navigation/drawer";

import { ContactStackNavigator } from "./StackNavigator";
import TabNavigator from "./TabNavigator";

const Drawer = createDrawerNavigator();

const DrawerNavigator = () => {
  return (
    <Drawer.Navigator>
      <Drawer.Screen name="Home" component={TabNavigator} />
      <Drawer.Screen name="Contact" component={ContactStackNavigator} />
    </Drawer.Navigator>
  );
}

export default DrawerNavigator;
Enter fullscreen mode Exit fullscreen mode

And then back in our App.js file, we can now import our newly created DrawerNavigtor.js file and use it as our navigator.



// ./App.js

import React from "react";
import { NavigationContainer } from "@react-navigation/native";

import DrawerNavigator from "./navigation/DrawerNavigator";

 const App = () => {
  return (
    <NavigationContainer>
      <DrawerNavigator />
    </NavigationContainer>
  );
}
export default App;
Enter fullscreen mode Exit fullscreen mode

Drawer Navigation

There are also configuration options and header icons you can add to customize your drawer navigation. Find out more here.

Conclusion

In this article, we've been able to look at how to set up and combine the Stack, Tab, and Drawer navigation for our react-native app using react-navigation 5.

The source code used in demonstrating this article can be found here.

If you have any questions or feedback about this article, feel free to leave a comment.

Thanks for reading.

Top comments (43)

Collapse
 
gauravmahendru profile image
Gaurav Mahendru •

I have made a Tab Navigator for my React Native App and I want to call this tab navigator with a click of a button. Currently, I have a SignUpScreen and SignInScreen and the button I want to call is inside SignInScreen with the props called { navigation } with the function but the button is throwing an error of undefined 'navigation.navigate' object. My Tab Navigator works perfectly fine but I am not able to call it on this Login button, is there something to do with Stack Navigator here? I am calling Tab Navigator to my HomeScreen and this HomeScreen inside the Login Button. Any help will be appreciated.

Collapse
 
easybuoy profile image
Ekunola Ezekiel •

So I'm guessing the way your navigation is set up is that your Tab navigation is calling the Stack navigation, and the Tab navigation is being used in the App.js entry point to the app right?

Collapse
 
gauravmahendru profile image
Gaurav Mahendru •

Actually, Tab Navigation (I am using this inside return function of a HomeScreen) should be called on a button but it’s not working.

For the App.js, right now I have made SignInScreen as my entry point which comes from AppTextInput file and this AppTextInput.js file has a button to call Tab Navigation, but unluckily, I am getting an error of undefined navigation.navigate even though I am using the navigation props with the function.

Thread Thread
 
easybuoy profile image
Ekunola Ezekiel •

I think the issue is you need to return a navigation (tab navigation which contains the stack screens) in the app.js file, just like it's shown in this article. You can set the default screen to show up on the first app load.

Thread Thread
 
gauravmahendru profile image
Gaurav Mahendru •

My default screen is SignInScreen and this screen has a button to it. On a click of this, I want to go to Tab Navigation which I created.

It's giving me navigation error even though I am using navigation as a props with the SignInScreen return function. Normally, I have tested my Tab Navigation by straight calling it into App.js. This works but I want this to be called on Button. It's not working for me.

Collapse
 
mirko1075 profile image
Mirko •

Hi, thanks for the great article. My question is, what if I need to have the 2 navigation together? Drawer + bottom tab navigation? Where should I import and put the bottom tab navigator? In App.js? How can I nest them? Thank you in advance

Collapse
 
masoud94 profile image
Masoud-94 •

Thanks a lot for putting time and effort into writing this.
This article was very helpful, but I have a small issue.

In drawer navigation, when I go forth and back in my screens, the screen freezes.
In the beginning, I search all of my code but didn't find anything,
finally, I came across one example in Reac Navigation Documentation, and I ran it in my Expo and saw similar behaviour.

I was wondering that have you ever experience this? What causes this issue?
Any suggestion will be helpful.

Collapse
 
easybuoy profile image
Ekunola Ezekiel •

I haven't had that error, unfortunately. Maybe try google that particular error to see if other people have faced that issue.

Collapse
 
monir_ullah_e6c710c737119 profile image
Monir Ullah •

Great article, Ekunola! Your guide on combining Stack, Tab, and Drawer navigation in React Native is super clear and helpful. Thanks for the step-by-step instructions. I got my project working! Just one question: How can I add custom icons to the Tab Navigator items? Thanks!

Collapse
 
seankang profile image
Seankang(he, him, dude, guy) •

How about doing this with classes? For example, if Home was defined as :

Anyone written a sample or template like this?

class Home extends React.Component{
render() {

This is the home screen

}
}

Collapse
 
ivanbarbai profile image
Iván Barba • • Edited

Hey thank you very much for this tutorial, i'm making an app based on this, but the header its being duplicated, i've searched trough youtube and the official documentation but i didn't find anything, any help'll be appreciated 🙏. dev-to-uploads.s3.amazonaws.com/i/...

Collapse
 
pyaehphyoe profile image
Pyaeh Phyoe Ko Ko • 
<Tab.Navigator screenOptions={{headerShown: false}}>
    <Stack.Navigator screenOptions={{headerShown: false}}>
Enter fullscreen mode Exit fullscreen mode
Collapse
 
scribbletons profile image
ScribbleTons •

Thanks for the article. How do I make the tabpress fast enough when switching from one route to another. I'm using expo and it's almost unresponsive when tapped.

I even turned off my debugger and it's still the same.

The JS thread falls to almost -2 to 0.

It's really frustrating.

Collapse
 
lucasmichailian profile image
Lucas Michailian •

Hi! Great Article, Can I hide tab bar on nested About ?

Collapse
 
easybuoy profile image
Ekunola Ezekiel •

Yes, you should be able to hide the tab bar on specific screens by passing tabBarVisible as a prop to the navigation options I think

Collapse
 
niranjan2210 profile image
Niranjan Nagaraja •

I have a Drawer with several screens to navigate to.
I have a bottom tab navigator with 5 entries.
Now when I open the drawer and select a screen that is not in Bottom tab navigator, I can navigate to that screen but the Bottom Tab Navigator dissappears.
How do I retain the Bottom Tab when I navigate to a screen from the drawer which is not part of the Bottom Tab?

Collapse
 
deepugupta899 profile image
Deepanshu •

i have a major issue if define a screen inside drawer.navigation with Drawer.Screen .....then between those pages i dont get sliding animation when i navigate from one page to another page....it happpens with only those pages which are defined as Drawer.Screen....please help someone

View full discussion (43 comments)

Read next

adrian_zuplo profile image

What is JSON Merge Patch?

Adrian Machado -

sebastienlorber profile image

This Week In React #214 : Base UI, Custom Elements, Next.js, React Router, Android XR, iOS targets, Nitro, RNTL...

Sebastien Lorber -

midhunkrishnan profile image

To access terminal profile of VS Code and add commands to be run initially

Midhun Krishnan R -

hasunnilupul profile image

Exploring React Router v7's New Framework: A Modern Take on Routing

Nilupul Perera -