Drawer and Tabs Navigation using react-navigation

in Programming

In this tutorial, we'll add Drawer and Tabs Navigation using react-navigation.

In case you haven’t followed the first part of the series, you can clone the tutorial series and checkout the first part by running these commands:

git clone https://github.com/qaiser110/ReactNative-Bookstore-App-Tutorial.git bookstore-app
cd bookstore-app
git checkout 1-prettier-eslint-airbnb-styleguide-setup

Our Bookstore app will contain a navigation drawer with two menu options. The first menu item for the AuthorsScreen, containing the list of authors. The second menu item for the BooksScreen, containing the list of books. Tapping on a book will take the user to the BookDetail Screen For navigation between the different views, we’ll use React Navigation to add navigation to our app. So let’s install it first:

npm install --save react-navigation


Our ReactNative app will contain two modules, an Author module allowing the users to browse list of authors, and a Books module, containing the list of books. Author and Book module will be implemented using the StackNavigator from React Navigation. Think of StackNavigator as the history stack in a web browser. When the user clicks on a link, the URL is pushed to the browser history stack, and removed from the top of the history stack when the user presses the back button.

export const BookStack = createStackNavigator({
  Books: {
    screen: BooksScreen,

export const AuthorStack = createStackNavigator({
  Authors: {
    screen: AuthorsScreen,

For BooksScreen and AuthorsScreen, we’ll simply add two stateless react components for now, with some buttons to test our screen navigation and drawer functionality:

const BooksScreen = ({ navigation }) => (
      onPress={() => navigation.navigate('Authors')}
      title="Go to Authors"
    <Button onPress={() => navigation.openDrawer()} title="Open Drawer" />

const AuthorsScreen = ({ navigation }) => (
    onPress={() => navigation.navigate('Books')}
    title="Go back to Books"

navigation.openDrawer() will trigger the drawer to open. navigation.navigate() allows the app to navigate to different screens.

In our application, we’ll add a Drawer which will maintain the menu for our Author and Book modules. The drawer will be implemented using React Navigation’s createDrawerNavigator. The first menu in the drawer will be for the Author module, and the second for the Book module. Author and Book Stack Navigators will both be inside the main DrawerStack. Here’s the code for the drawer implementation:

const App = createDrawerNavigator({
  Books: {
    screen: BookStack,
  Authors: {
    screen: AuthorStack,

Here’s a diff of our latest changes.

In the file App.js, we’ve made the following changes:

  1. We renamed the default export to App
  2. We added two stateless components for our screens, BooksScreen and AuthorsScreen.
  3. We added the StackNavigator from React Navigation to implement navigation for our app.
  4. We used createDrawerNavigator() from react-navigation to implement the Drawer Navigation. This renders the Drawer content, along with the menu options for Books and Authors.

And after making the above changes, here’s what our UI looks like when we click on the “Open Drawer” button and navigate between screens.


Directory Structure

It’s important to think about your application and how you’ll structure of your files and resources in the beginning of the project. While there could be several ways of structuring your application code, I prefer co-locating files and tests using a feature-based architecture. Co-locating files related to a particular feature or module has several benefits.

Let’s create a src directory, where we’ll keep all our source files, and inside it, create two directories, one for the book view, named “book”, and the other for the author view, named “author”.

Create index.js files within each of the two directories we just added. These files will export the components for each of our views. Move the code from App.js for the BookView and AuthorView components into these files, and import them instead.

It’s important to note that refactoring should be a big part of the development workflow. We should continuously refactor our code to prepare ourselves for future changes and challenges. This has a big impact on productivity and change management in the long run.

Our app should still work as it was before the refactor. Here’s the file diff of our recent changes.

Each of the screen will have a title, which means that we’d be duplicating the same code along with the styles. To keep our code DRY, let’s move the title to a separate file src/components/Title.js, and reuse it where needed. We’ll also move the main views into a new parent directory src/views to keep them separate from other components.

Tab Navigation

The business requirement for our app is to have three tabs in the books view, to show all books by default, and additional tabs to show filtered books for the fiction and non-fiction books. Let’s use the createBottomTabNavigator from react-navigation to implement the Tab Navigation.

import { createBottomTabNavigator } from 'react-navigation'

import { AllBooksTab, FictionBooksTab, NonfictionBooksTab } from ' components/book-type-tabs'

export default createBottomTabNavigator({
  'All Books': AllBooksTab,
  Fiction: FictionBooksTab,
  Nonfiction: NonfictionBooksTab,

We should also add a title on every screen to identify the currently selected screen. Let’s create a separate directory src/components for all the common components, and create a file for our Title component inside this new directory.

// src/components/Title.js
import React from 'react'
import { StyleSheet, Text } from 'react-native'

const styles = StyleSheet.create({
  header: {
    textAlign: 'center',
    padding: 20,
    marginTop: 20,
    fontSize: 20,
    color: '#fff',
    backgroundColor: '#434343',

export default ({ text }) => <Text style={styles.header}>{text}</Text>

Note that we’ve also added style to the <Text> component, importing both StyleSheet and Text from react-native.

We’ll add the Title to each view component, providing the title text in the props. Also, since Authors view just contains a list of authors, we don’t need a StackNavigator for it, so we’ll change it to a plain React component. Here’s what our src/views/author/index.js file looks like now:

// src/views/author/index.js

import Title from '../../components/Title'

export default ({ navigation }) => (
    <Title text="Authors List" />
    <Button onPress={() => navigation.openDrawer()} title="Open Drawer" />
    <Button onPress={() => navigation.navigate('Books')} title="Go to Books" />

Now, when we open the Books menu from the drawer, we’re able to switch tabs by clicking on the tabs at the bottom.

With those changes we have our apps navigations all done. Here’s the diff for our recent changes.

React Native Elements

There are several UI component libraries for adding React Native components with style. Some of the more poular ones are React Native Elements NativeBase, and Ignite. We’ll be using React Native Elements for our Bookstore app. So let’s first install react-native-elements:

npm install --save react-native-elements

Authors List using react-native-elements

Let’s use the ListItem component from React Native Elements to add a list of authors in our Author screen.

For Author List, we’ll use the data and code from the ListItem demo. We’ll revisit ListItem into more detail when we implement the Book List screen.

Here’s the diff for our recent changes.