Building offline React Native apps with AsyncStorage

Published on Aug 18, 2019

34 min read



Originally published at Heartbeat

As developers, we love exploring concepts and mechanisms while working with a new framework. React Native as a cross-platform development framework has come quite far in terms of a mature framework since I started playing around with it and then using it for its purpose. Understanding the fundamentals when learning it is something very helpful, and I consider, important.

Thus, applying basic fundamentals of React Native knowledge, in this tutorial, I am going to walk you through how to build a todo list application using an offline storage functionality. This storage functionality is provided by a native module in React Native, called AsyncStorage.

In the journey of building this application, you are going to use a UI component library known as Native Base, which is one of the most popular libraries to build user interfaces among React Native developers. Out of the box, this library speeds up the development process by providing pre-defined UI components that can either be used as they are available or customize them according to our needs.

What are we building?


The outcome from following this tutorial is going to be a complete React Native application that works with realtime offline data from the storage of the device.

Table of Contents

  • Prerequisites
  • Create an Expo app
  • Exploring AsyncStorage
  • Utilizing AsyncStorage API
  • Adding Navigation
  • Creating a Floating Action Button (FAB)
  • Navigating between Two Screens
  • Customize the Header Component
  • Rendering a list of items using FlatList
  • Reading Data using AsyncStorage API
  • Adding a Todolist Item
  • Deleting a Todolist Item
  • Mark an Item Check or Uncheck on completion
  • Passing Data between different screens using the navigation
  • Display each todo list item
  • Bonus Section: Adding a Segment
  • Conclusion



To follow this tutorial, please make sure you have the following installed on your local development environment and have access to the services mentioned below:

  • Node.js (>=8.x.x) with npm/yarn installed.
  • expo-cli (>=3.0.4), previously known as create-react-native-app.

It will be best if you use the same exact versions or higher of each utility tool described above. To run and test the React Native application, all you need is an Expo client installed either on your device or an iOS simulator or an Android emulator. Please note that, throughout this tutorial, I will be using an iOS simulator to demonstrate the application.

Create an Expo app


To get started, all you require is to generate a new Expo project. This could be done by opening a terminal window, navigating to a suitable location where you develop projects and running the following commands in the order they are described.

expo init offline-todolist-app
# navigate inside the app folder
cd offline-todolist-app
# install the following dependencies
yarn add react-navigation native-base
expo-font@5.0.1 lodash.values uuid

The last command, as described in the above snippet installs five dependencies that the application is going to use. yarn is currently being used as the package manager. You can also use npm instead of yarn. The use of each dependency will be made clear as throughout this tutorial as they are used. If this is your first time building a React Native application, try not to get overwhelmed by them.

Exploring AsyncStorage


AsyncStorage is a simple, asynchronous key-value pair used in React Native applications. It is used for a variety of scenarios but mainly to store data when your app is not using any cloud services, or you want to implement some features in your app that require data storage.

It operates globally in a React Native and comes with its own limitations. As a React Native developer, you have to know what these limitations. The first limitation of an AsyncStorage API is that the size of the database is set to 6MB limit. Also, AsyncStorage storage is based on SQLite. Thus, it is important to keep SQLite limitations in mind too. Also, it is hard to store complex and nested data structures in form of key-value pairs. Knowing about these limitations, only help you to opt for the persistent solution when developing a mobile app.

According to the React Native's official documentation:

On iOS, AsyncStorage is backed by native code that stores small values in a serialized dictionary and larger values in separate files. On Android, AsyncStorage will use either RocksDB or SQLite based on what is available.

Utilizing AsyncStorage API


Before you dive deep in building the Todolist app, in this section, let us build a small app that saves a value to the AsyncStorage, fetches the value from the storage in the client-side React Native app. This will help you how to write basic operations using the storage API. Lastly, you will learn about how to clear the storage completely.

Open App.js file and add the following snippet. Start by importing the necessary components from React Native API. The most important one here is AsyncStorage. After that, define a variable named STORAGE_KEY. This variable will be used to store and retrieve the stored data using the AsyncStorage API. Think of it as an identifier for the value being stored or name of the key in the key-value pair. Since you are going to store only one value at the moment, there is only the requirement for one key.

1import React from 'react';
2import {
3 StyleSheet,
4 Text,
5 View,
6 TextInput,
7 AsyncStorage,
8 TouchableOpacity
9} from 'react-native';
11const STORAGE_KEY = '@save_name';

Next, let us define an initial state with two empty strings. They are going to be used to save the value of the user input and then retrieve the value to display it on the app screen. After defining the initial state, there is going to be a lifecycle method that is going to load the data when the application starts for the first time or the App component renders.

1class App extends React.Component {
2 state = {
3 text: '',
4 name: ''
5 };
7 componentDidMount() {
8 this.retrieveData();
9 }
11 // ...

In the above snippet, do note that the App component is actually a class component and not the default functional component that comes with boilerplate Expo app. Now, there are going to be three methods that will help to store the data, retrieve the data, and clear the app data that is stored. This is going to be done by creating three asynchronous methods. Each of the methods is going to utilize the appropriate API method from AsyncStorage API. Every method in the AsyncStorage API is a promise-based, hence, let us use async/await syntax to follow good practice.

1retrieveData = async () => {
2 try {
3 const name = await AsyncStorage.getItem(STORAGE_KEY);
5 if (name !== null) {
6 this.setState({ name });
7 }
8 } catch (e) {
9 alert('Failed to load name.');
10 }

In the above snippet, the name of the method implies what they are going to do in the app. The retrieveData method is what fetches the data from the storage if it exists. It uses the same identifier that you defined previously, outside the class function component. It utilises the parameter in the state object name. Later in the app, you are going to use this parameter to display its stored value. Note that, there is an if condition inside this method. This condition says that to fetch the data only when there is a value for the name variable exists. This method also uses try/catch as they are part and parcel of writing functions with modern async/await syntax. Lastly, this method is being invoked inside the lifecycle method.

The next function is going to save the data. In the below snippet, you will find that it uses a parameter name which on success, is the value that is stored. An alert message will be shown when the input data is saved.

1save = async name => {
2 try {
3 await AsyncStorage.setItem(STORAGE_KEY, name);
4 alert('Data successfully saved!');
5 this.setState({ name });
6 } catch (e) {
7 alert('Failed to save name.');
8 }

The last method that you are going to utilize from the AsyncStorage API is called clear(). This deletes everything that is previously saved. It is not recommended to use this method directly if you want to delete only a specific item from the storage. For that, there are methods like removeItem or multiRemove available by the API. You can read more about them in the official documentation here or later when building the Todolist application.

1removeEverything = async () => {
2 try {
3 await AsyncStorage.clear();
4 alert('Storage successfully cleared!');
5 } catch (e) {
6 alert('Failed to clear the async storage.');
7 }

This snippet will throw an Alert box on the device screen when everything is cleared from the storage.

The last two methods are going to be used to create a controlled input.

1onChangeText = text => this.setState({ text });
3onSubmitEditing = () => {
4 const onSave =;
5 const { text } = this.state;
7 if (!text) return;
9 onSave(text);
10 this.setState({ text: '' });

After that, add the code snippet for the render method, followed by the styles for each UI component. Lastly, do not forget to export App component for it to run on the simulator or the real device.

1render() {
2 const { text, name } = this.state
3 return (
4 <View style={styles.container}>
5 <TextInput
6 style={styles.input}
7 value={text}
8 placeholder='Type your name, hit enter, and refresh'
9 onChangeText={this.onChangeText}
10 onSubmitEditing={this.onSubmitEditing}
11 />
12 <Text style={styles.text}>Hello {name}!</Text>
13 <TouchableOpacity onPress={this.removeEverything} style={styles.button}>
14 <Text style={styles.buttonText}>Clear Storage</Text>
15 </TouchableOpacity>
16 </View>
17 )
18 }
19} // class component App ends here
21const styles = StyleSheet.create({
22 container: {
23 flex: 1,
24 backgroundColor: '#fff',
25 alignItems: 'center',
26 justifyContent: 'center'
27 },
28 text: {
29 fontSize: 20,
30 padding: 10,
31 backgroundColor: '#00ADCF'
32 },
33 input: {
34 padding: 15,
35 height: 50,
36 borderBottomWidth: 1,
37 borderBottomColor: '#333',
38 margin: 10
39 },
40 button: {
41 margin: 10,
42 padding: 10,
43 backgroundColor: '#FF851B'
44 },
45 buttonText: {
46 fontSize: 14,
47 color: '#fff'
48 }
51export default App

Now to run the application, go to the terminal window and execute the command expo start. After that, you will see the following screen on the simulator.

Since there is no data stored right now, the text after the word Hello is empty. Use the input field to save a string or a name or anything and then press the enter key. You will get the following output. Whatever input you entered, it will be displayed next to the word Hello.

Even if you refresh the Expo client, the value stored does not go away. Only when pressing the button below Hello statement that says Clear Storage is the way to delete the stored value.

Refresh the Expo client after you clear the storage to get the following output.

This complete the section where you learned about how to utilize AsyncStorage API to save and fetch the data. From the next section onwards, you will be building the Todolist application.

Organizing the application


Since a React Native application was already generated in the previous step, you can continue to utilize that app by modifying everything inside the App.js file. Or create a new one if it serves you well.

You have already installed the necessary npm modules. This is the time to start utilizing them in order to build the offline todo list app. Before beginning with the development of the app, create the following folders and files inside them. This will give a structure to manage the app later or if you want to extend by adding new features to it.

From the structure, notice that there are three new folders being created. This structure is the separation of concerns between the different aspect of a mobile app. Such as files or configuration related to navigation should be separated from the screens. The above structure is also a common pattern that many React Native developers have started to follow in their work.

Adding Navigation


Inside the navigation folder, there is an index.js file that is going to hold all the configuration there is to be defined. The reason react-navigation module is used is to create a stack navigator that allows the user to visit the two screens the following application has. The navigation mode is going to be modal. Yes, you can utilize pre-defined navigation modes or animation patterns.

Let us start by importing the necessary components inside the index.js file.

1import React from 'react';
2import { createStackNavigator, createAppContainer } from 'react-navigation';
3import HomeScreen from '../screens/HomeScreen';
4import AddTaskScreen from '../screens/AddTaskScreen';

From the above snippet, notice that the createStackNavigator is a function that returns a React component. It takes a route configuration object. The createAppContainer is responsible for linking the current React Native app while maintaining the navigation state from the top-level component. The top-level component in your app is App.

With the help of createAppContainer, you are going to create a provider and wrap the App component inside it. This will benefit the entire application as every screen or component defined is going to have a navigation state. You will learn some of the many benefits provided by the navigation state later.

Lastly, in the above snippet, there are going to be a screen component. These screen components are going to hold the business logic necessary to run the todo list app. You can think of them as containers.

Right now, the route configuration object is going to be as the following snippet.

1const StackNav = createStackNavigator(
2 {
3 Home: {
4 screen: HomeScreen
5 },
6 AddTask: {
7 screen: AddTaskScreen
8 }
9 },
10 {
11 mode: 'modal'
12 }

The mode is important to specify here. It defines the style for rendering the next screen component. In the above case, it is AddTask screen. In an iOS or Android app, the default transition is always a card. You are changing this default transition by specifying the mode property and setting its value to modal.

The modal pattern Make the screens slide in from the bottom, which is a common iOS pattern. Only works on iOS but has no effect on Android.

Lastly, you have to export the app container that utilizes the StackNav. Here is the code for that.

1const RootNavigator = createAppContainer(StackNav);
3export default RootNavigator;

Now, open App.js file and add the following content.

1import React from 'react';
2import RootNavigator from './navigation';
4export default function App() {
5 return <RootNavigator />;

Before running the app, make sure there is a mock component to render inside the files HomeScreen.js and AddTaskScreen.js. Otherwise, it will throw an error. You can add the dummy component for now.

1// HomeScreen.js
2import React, { Component } from 'react';
3import { Text, View } from 'react-native';
5export class HomeScreen extends Component {
6 render() {
7 return (
8 <View>
9 <Text> Offline Todolist App</Text>
10 </View>
11 );
12 }
15export default HomeScreen;
17// AddTaskScreen.js
18import React, { Component } from 'react';
19import { Text, View } from 'react-native';
21export class AddTaskScreen extends Component {
22 render() {
23 return (
24 <View>
25 <Text>Add Task Screen</Text>
26 </View>
27 );
28 }
31export default AddTaskScreen;

Now run the app using expo start command, and you will get the following result.

This completes the navigation section.

Create a Floating button


Inside the components/FloatingButton.js file, you are going to create a floating action button or in mobile development, commonly known as FABs. These type of buttons are often distinguished by a circled icon floating above the UI in a fixed position. If you are an Android user or have seen a mobile app following any material design specification, you might have noticed them.

In the current app, this FloatingButton is going to be responsible for navigating from the HomeScreen to the AddTaskScreen. Since it is going to be a presentation component, you should define it as a functional component that accepts only one prop. This prop actionOnPress is going to be a method defined inside the HomeScreen.js file that will contain the logic of navigating between the two screens later.

One important thing to notice in the snippet below is that the component library native-base is being used to create the FAB button. It saves a good amount of time and lines of code to create and style a component like below.

1import React from 'react';
2import { StyleSheet } from 'react-native';
3import { Icon, Fab } from 'native-base';
5const FloatingButton = ({ actionOnPress }) => (
6 <Fab
7 direction="up"
8 style={styles.button}
9 position="bottomRight"
10 onPress={actionOnPress}
11 >
12 <Icon name="ios-add" />
13 </Fab>
16const styles = StyleSheet.create({
17 button: {
18 backgroundColor: '#5859f2'
19 }
22export default FloatingButton;

Navigating Between Two Screens


Once you have defined it, go to the file HomeScreen.js and the following snippet of code.

1import React, { Component } from 'react';
2import { View, Text, StyleSheet } from 'react-native';
3import { AppLoading } from 'expo';
4import * as Font from 'expo-font';
5import FloatingButton from '../components/FloatingButton';
7export class HomeScreen extends Component {
8 state = {
9 isDataReady: false
10 };
11 componentDidMount = () => {
12 this.loadFonts();
13 };
15 loadFonts = async () => {
16 try {
17 await Font.loadAsync({
18 Roboto: require('../node_modules/native-base/Fonts/Roboto.ttf'),
19 Roboto_medium: require('../node_modules/native-base/Fonts/Roboto_medium.ttf'),
20 Ionicons: require('../node_modules/native-base/Fonts/Ionicons.ttf')
21 });
22 this.setState({ isDataReady: true });
23 } catch (err) {
24 alert('Application Error. Cannot load fonts.');
25 }
26 };
28 onPressFab = () => {
29 this.props.navigation.navigate('AddTask');
30 };
32 render() {
33 const { isDataReady } = this.state;
35 if (!isDataReady) {
36 return <AppLoading />;
37 }
38 return (
39 <View style={styles.container}>
40 <Text>Home Screen</Text>
41 <FloatingButton actionOnPress={this.onPressFab} />
42 </View>
43 );
44 }
47const styles = StyleSheet.create({
48 container: {
49 flex: 1
50 }
53export default HomeScreen;

In the above snippet, the first and important thing to notice is the loadFonts method. This asynchronous method is a requirement to make Native Base UI library to work in any React Native, and Expo generated application. NativeBase use some custom fonts that are loaded using Font.loadAsync function. This function is provided by the expo module expo-font which allows you to use any fonts or icons in React Native components.

The AppLoading method is a React component that tells Expo to keep the app loading screen visible until Font.loadAsync() the method has run successfully. In general, this a useful method to utilize when your app is using custom fonts, logos, icons, and so on. In the current application, you are going to utilize this React component again when fetching data from AsyncStorage API (that you will see in action later in this tutorial). The AppLoading will only stop running when the boolean value for the state variable isDataReady is set to true. This boolean value is only set to true when Font.loadAsync() has finished running.

Once the application has loaded all necessary fonts and icons, you will get the following result.

From the above snippet, take a look at the method onPressFab which is being passed to the FloatingButton component as the prop actionOnPress. This function utilizes a navigation method provided called navigation.navigate() with the value of the screen being passed as the argument: AddTask. Do note that, the value of the argument being passed should be the exact name of the screen defined earlier when configuring StackNavigator. Click on the button, and you will be directed to the next screen.

Did you notice the back button on the AddTaskScreen? This is again where react-navigation comes in handy. While working on a real-time React Native application, you often want to use the react-navigation library if it suits your requirements. It provides simple solutions out of the box.

Customize the Header Component


With Native Base components library, it is easy to customize a header component in few lines of code. Inside the file Header.js add the following snippet. Again, this is a functional component since it is going to enhance the UI and is not running business logic.

1import React from 'react';
2import { Header as NBHeader, Body, Title } from 'native-base';
4const Header = () => {
5 return (
6 <NBHeader style={{ backgroundColor: '#5859f2' }}>
7 <Body>
8 <Title style={{ color: '#ffffff' }}>Header</Title>
9 </Body>
10 </NBHeader>
11 );
14export default Header;

The Header component from the native-base library takes a Body as an input. The body can further contain the rendering logic to modify the existing default Header component from the native base library itself. You can use inline styles or even StyleSheet object from react-native to customize the Header component as above, or any other native base UI component in general. Take a look at the backgroundColor and the color to the Title. Title is where the text to be displayed on this component goes.

Import this component inside the HomeScreen.js file. Also, import the StatusBar component from the react-native. Since the background of the Header component is going to be a customize blue color, it is better to change the default dark StatusBar style into something pleasing and light.

1import { View, Text, StyleSheet, StatusBar } from 'react-native';
2import Header from '../components/Header';

Inside the class component, the first thing you have to do is hide the header that is being provided by the stack navigator from react-navigation library. The object navigationOptions is how to customize the default navigators that react-navigation renders.

1 static navigationOptions = {
2 header: null
3 }

Next, inside the render() method add the following before the omnipresent Text component.

1<Header />
2<StatusBar barStyle='light-content' />
3<Text>Home Screen</Text>

The rest of the code inside the HomeScreen.js file remains unchanged. The StatusBar is modified by defining the a value using its pre-defined prop barStyle. When using a Header component from Native Base UI library, the StatusBar from React Native comes after you define the JSX code for the header. Notice this in the above snippet. This is how it works with Native Base library. The following screen is what you get as the result of the above snippets.

Rendering a list of items using FlatList


In this section, you are going to set up a List component that accepts mock or dummy data from an array defined as a property to the initial state. Open HomeScreen.js file and modify the state for now.

1state = {
2 isDataReady: false,
3 mockItems: ['First Item', 'Second Item', 'Third Item']

Why dummy data? Later when you are going to hook AsyncStorage API to save and fetch the data from the database, in other words, playing around with real-time data operations, there are going to be separate methods that are going to handle each of the data operations. For now, let us hook up the business logic to display a list of items as well as the ability to add a new item using the modal screen you have set up in the previous steps.

The FlatList component is the ideal way to display a list of items in a React Native application. It is a cross-platform component, and by default a vertical way to display a list of data items. It requires two props: data and renderItem. The data is the source of information for the list in the form of an array. The renderItem takes one item from the source, iterates over them, and returns a formatted component to render those items.

Styles that can be applied to a FlatList component is done by the prop contentContainerStyle that accepts the value of Stylesheet object. The reason to use FlatList is that it is performance effective. Of course, you can use ScrollView but it renders items from memory, which is not a very performant effective way to display a lengthy list of items. ScrollView is a wrapper on the View component that provides the user interface for scrollable lists inside a React Native app.

In the file HomeScreen.js replace the Text component with following FlatList and do not forget to import it and custom presentational component Item that is going to display each item in the list.

1// import statements
2import { View, FlatList, StyleSheet, StatusBar } from 'react-native';
3import Item from '../components/Item';
5// in render method, replace <Text> with the following
7 data={this.state.mockItems}
8 contentContainerStyle={styles.content}
9 renderItem={row => {
10 return <Item text={row.item} />;
11 }}
12 keyExtractor={item =>}

Now open the file components/Item.js and add the following snippet.

1import React from 'react';
2import {
3 View,
4 Text,
5 StyleSheet,
6 TouchableOpacity,
7 Dimensions
8} from 'react-native';
10const { width } = Dimensions.get('window');
12const Item = ({ text }) => {
13 return (
14 <View style={styles.container}>
15 <View style={styles.rowContainer}>
16 <Text style={styles.text}>{text}</Text>
17 </View>
18 </View>
19 );
22const styles = StyleSheet.create({
23 container: {
24 borderBottomColor: '#5859f2',
25 borderBottomWidth: StyleSheet.hairlineWidth,
26 flexDirection: 'row',
27 alignItems: 'center',
28 justifyContent: 'space-between'
29 },
30 rowContainer: {
31 flexDirection: 'row',
32 width: width / 2,
33 alignItems: 'center'
34 },
35 text: {
36 color: '#4F50DC',
37 fontSize: 18,
38 marginVertical: 20,
39 paddingLeft: 10
40 }
43export default Item;

Another new React Native component to notice in the above snippet is Dimensions. It helps to set the initial width and height of a component before the application runs. We are using its get() method to acquire the current device's width and height.

In the simulator, you will get the following result.

Reading Data using AsyncStorage API


In this section, you are going to add all methods that will contain business logic to save and fetch the data from the AsyncStorage. This logic will be composed of three operations:

  • add a todolist item
  • fetch all items to display
  • delete an item from the list
  • also, check the state of each list item whether it is marked as completed or not

These operations are going to communicate with the realtime data on the device. You are going to use objects instead of an array to store these items. AsyncStorage operates on key-value pairs and not arrays. Each object is going to be identified through a unique ID. In order to generate unique IDs, you are going to use a module called uuid which was installed earlier.

The structure of each todo item is going to be like this:

145745c60-7b1a-11e8-9c9c-2d42b21b1a3e: {
2 id: 45745c60-7b1a-11e8-9c9c-2d42b21b1a3e, // same id as the object
3 textValue: 'New item', // name of the ToDo item
4 isCompleted: false, // by default, mark the item unchecked
5 createdAt:

But if you are going to use Objects instead of an array, how are you going to iterate over each item in the object? FlatList component only takes an array to iterate. Well, do you remember installing a utility package called lodash.values? That package is going to be really helpful in converting the object into an array.

First, let us start by importing all components and custom components required in order to build the application inside HomeScreen.js file.

1import React, { Component } from 'react';
2import {
3 FlatList,
4 View,
5 StatusBar,
6 StyleSheet,
7 AsyncStorage
8} from 'react-native';
9import uuidv1 from 'uuid/v1';
10import _values from 'lodash.values';
11import { Button, Text as NBText } from 'native-base';
12import { AppLoading } from 'expo';
13import * as Font from 'expo-font';
14import Header from '../components/Header';
15import Item from '../components/Item';
16import FloatingButton from '../components/FloatingButton';

After writing these import statements, let us modify the initial state.

1state = {
2 todos: {},
3 isDataReady: false

From the above snippet, do take a note that the dummy array of data is replaced by the object todos. Next, you are going to write an asynchronous method to load the todos items from the object that is stored using AsyncStorage API. Also, let us merge the previous asynchronous method to load all the fonts with this method, such as the value of the initial state isDataReady is set to the boolean true only once. You will also have to modify the contents of the lifecycle method.

1componentDidMount = () => {
2 this.loadTodos();
5loadTodos = async () => {
6 try {
7 await Font.loadAsync({
8 Roboto: require('../node_modules/native-base/Fonts/Roboto.ttf'),
9 Roboto_medium: require('../node_modules/native-base/Fonts/Roboto_medium.ttf')
10 });
12 const getTodos = await AsyncStorage.getItem('todos');
13 const parsedTodos = JSON.parse(getTodos);
14 this.setState({ isDataReady: true, todos: parsedTodos || {} });
15 } catch (err) {
16 alert('Application Error. Cannot load data.');
17 }

AsyncStorage.getItem() reads anything saved on the device database. It is essential to parse the data incoming from the storage into JSON. If you are not parsing the data, the application is going to crash. When setting the state in the above snippet, the todos object is getting the default value of an empty object is there is no data from the storage. This is also an essential step to perform and keep in mind for other use cases with similar scenarios.

Adding a Todolist Item


Now, let us add the second method addTodo that is actually going to add the new item in the storage. The method defines before addTodo is actually storing the items in the storage. Again, you are using JSON.stringify() since AsyncStorage requires the data to be a string inside the single object. So when saving the item if you are not using JSON.stringify() your app is going to crash.

The AsyncStorage.setItem()is the function from the API that is similar to any key-value paired database. It takes the first argument, todos in the snippet below. This argument value is going to be the name of the store.

The parameter newTask passed to the addTodo function is going to be the object. Using if statement, there is a check whether the todo item being entered is not empty. this.setState uses a callback method that has access to prevState object. It gives any todo item that has been previously added to the list.

Inside the callback, you are first creating a new ID using uuidv1 method. Then create an object called newTodoObject which uses the ID as a variable for the name. This object represents each item in the todo list.

Further, create a new object called newState which uses the prevState object, and finally adds newTodoObject object in todoliist of items. It might sound overwhelming since a lot is going on but try implementing the code, you will understand it better.

1saveTodos = newToDos => {
2 const saveTodos = AsyncStorage.setItem('todos', JSON.stringify(newToDos));
5addTodo = newTask => {
6 const newTodoItem = newTask;
8 if (newTodoItem !== '') {
9 this.setState(prevState => {
10 const ID = uuidv1();
11 const newToDoObject = {
12 [ID]: {
13 id: ID,
14 isCompleted: false,
15 textValue: newTodoItem,
16 createdAt:
17 }
18 };
19 const newState = {
20 ...prevState,
21 todos: {
22 ...prevState.todos,
23 ...newToDoObject
24 }
25 };
26 this.saveTodos(newState.todos);
27 return { ...newState };
28 });
29 }

Deleting a Todolist Item


Similar to the addTodo method, you are going to add another method called deleteTodo. This will take care of removing an individual item from the list on the basis of id of that item object. Since you are using the id of the object both to identify the object inside the bigger object todos and assign each individual object the same id, the following code saves a lot of time. At last, using the saveTodos method, the storage is being updated with a remaining number of items.

1deleteTodo = id => {
2 this.setState(prevState => {
3 const todos = prevState.todos;
4 delete todos[id];
5 const newState = {
6 ...prevState,
7 ...todos
8 };
9 this.saveTodos(newState.todos);
10 return { ...newState };
11 });

Mark a Todo Item Check or Uncheck on completion


The last two methods that are going to take care of whether each individual item is checked or not are going to be represented by inCompleteTodo and completeTodo methods. Both of these methods are going track which items in the to-do list have been marked completed by the user or have been unmarked.

They are going to act as a toggle and only update the value of isCompleted instead rather updating the whole todo list item object. This is again, possible because of a unique id for each object. Again in the last, before each of the methods returns the new state, using the saveTodos method, the storage gets an update.

1inCompleteTodo = id => {
2 this.setState(prevState => {
3 const newState = {
4 ...prevState,
5 todos: {
6 ...prevState.todos,
7 [id]: {
8 ...prevState.todos[id],
9 isCompleted: false
10 }
11 }
12 };
13 this.saveTodos(newState.todos);
14 return { ...newState };
15 });
18completeTodo = id => {
19 this.setState(prevState => {
20 const newState = {
21 ...prevState,
22 todos: {
23 ...prevState.todos,
24 [id]: {
25 ...prevState.todos[id],
26 isCompleted: true
27 }
28 }
29 };
30 this.saveTodos(newState.todos);
31 return { ...newState };
32 });

Passing Data between different screens using the navigation


In this section, you are going to edit each render method that is responsible for displaying the interface for the operations you defined in the previous sections, to happen in realtime. Let us start by editing onPressFab method inside the HomeScreen.js.

This method right navigates to the AddTaskScreen. By passing an object with to add a new item to the list (hence, pass the method addTodo) you are going to utilize another advantage that a sleek library react-navigation provides. That is, to pass data between different screens.

First, edit the onPressFab method like the below snippet.

1onPressFab = () => {
2 this.props.navigation.navigate('AddTask', {
3 saveItem: this.addTodo
4 });

Next, open AddTaskScreen.js and add the following snippet.

1import React, { Component } from 'react';
2import { View } from 'react-native';
3import { Form, Item, Input, Button, Text as NBText } from 'native-base';
5export class AddTaskScreen extends Component {
6 state = {
7 text: ''
8 };
10 onChangeText = event => {
11 this.setState({ task: event.nativeEvent.text });
12 };
14 onAddTask = () => {
15 this.props.navigation.state.params.saveItem(this.state.task);
16 this.props.navigation.goBack();
17 };
19 render() {
20 return (
21 <View>
22 <View style={{ marginRight: 10 }}>
23 <Form>
24 <Item>
25 <Input
26 value={this.state.task}
27 placeholder="Enter a new task..."
28 autoFocus
29 clearButtonMode="always"
30 autoCorrect={false}
31 onChange={this.onChangeText}
32 onSubmitEditing={this.onAddTask}
33 returnKeyType={'done'}
34 />
35 </Item>
36 </Form>
37 </View>
38 <View style={{ marginTop: 20 }}>
39 <Button
40 style={{
41 backgroundColor: '#5067FF',
42 margin: 25,
43 justifyContent: 'center'
44 }}
45 onPress={this.onAddTask}
46 >
47 <NBText style={{ fontWeight: 'bold' }}>Add Task</NBText>
48 </Button>
49 </View>
50 </View>
51 );
52 }
55export default AddTaskScreen;

The snippet above uses the native base library to create a controlled input form to let the user add a new item to the todo list. Next, it has a button to add the item. Since the Input component from Native Base is based on the React Native's TextInput, you can use all the props that are available to TextInput.

Also, take a note that, to create an input field when using Native base as the UI library, the Input component has to be wrapped by an Item which is further wrapped inside Form element.

Here is a brief overview of the props used in the above snippet.

  • value: the value of the text input. By default, it will be an empty string since we are using the local state to set it. As the state updates, the value of the text input updates.
  • placeholder: just like in HTML, a placeholder is to define a default message in the input field indicating as if what is expected.
  • onChange: is a callback that is called when the text input's text changes. Changed text is passed as an argument to the callback handler onChangeText. This handler accepts the text value from event.nativeEvent.
  • clearButtonMode: a clear button should appear on the right side of the text view. The default value is never that you are modifying to always in the above component.
  • returnKeyType: determines how the return key on the device's keyboard should look. You can find more values or platform-specific values here. Some of the values are specific to each platform.
  • autoCorrect: this prop let us decide whether to show the autocorrect bar along with keyboard or not. In the current case, you have set it to false.
  • onSubmitEditing: contains the business the logic in the form of a callback as to what to do when the return key or input's submit button is pressed. We will be defining this callback in Main.js.

Lastly, take a look at the method onAddTask which uses navigation state to save the text value of the todo item. After use presses the button or the handler onSubmitEditing triggers, it is going to further run the method addTodo from HomeScreen and navigate back to the HomeScreen itself, using the navigation props method goBack().

On Clicking the Fab button, you get the following screen.

Display each todo list item


To display each todo list item, you will have first to pass the props as shown below using the renderItem in the FlatList.

2 isCompleted={row.item.isCompleted}
3 textValue={row.item.textValue}
4 id={}
5 deleteTodo={this.deleteTodo}
6 completeTodo={this.completeTodo}
7 inCompleteTodo={this.inCompleteTodo}

Next, go to Item.js file and add the following snippet.

1import React from 'react';
2import {
3 View,
4 Text,
5 StyleSheet,
6 TouchableOpacity,
7 Dimensions
8} from 'react-native';
9import { Icon } from 'native-base';
11const { width } = Dimensions.get('window');
13const Item = ({
14 inCompleteTodo,
15 completeTodo,
16 textValue,
17 id,
18 deleteTodo,
19 isCompleted
20}) => {
21 toggleItem = () => {
22 if (isCompleted) {
23 inCompleteTodo(id);
24 } else {
25 completeTodo(id);
26 }
27 };
29 return (
30 <View style={styles.container}>
31 <View style={styles.rowContainer}>
32 <TouchableOpacity onPress={this.toggleItem}>
33 <Icon
34 name={isCompleted ? 'checkmark-circle' : 'radio-button-off'}
35 style={{ paddingLeft: 10, color: '#7A7AF6' }}
36 />
37 </TouchableOpacity>
39 <Text
40 style={[
41 styles.text,
42 {
43 opacity: isCompleted ? 0.5 : 1.0,
44 textDecorationLine: isCompleted ? 'line-through' : 'none',
45 color: isCompleted ? '#7A7AF6' : '#4F50DC'
46 }
47 ]}
48 >
49 {textValue}
50 </Text>
51 </View>
52 <TouchableOpacity onPressOut={() => deleteTodo(id)}>
53 <Icon name="md-trash" style={{ color: '#ABADF9', paddingRight: 10 }} />
54 </TouchableOpacity>
55 </View>
56 );
59const styles = StyleSheet.create({
60 container: {
61 borderBottomColor: '#5859f2',
62 borderBottomWidth: StyleSheet.hairlineWidth,
63 flexDirection: 'row',
64 alignItems: 'center',
65 justifyContent: 'space-between'
66 },
67 text: {
68 color: '#4F50DC',
69 fontSize: 18,
70 marginVertical: 20,
71 paddingLeft: 10
72 },
74 rowContainer: {
75 flexDirection: 'row',
76 width: width / 2,
77 alignItems: 'center'
78 }
81export default Item;

In the above snippet, the key points to note are, using Native Base, you can use the Icon component (since you are already loading the Ionicons library in the parent component asynchronously). Next, the props Item components receive are to toggle an item's state of whether it is complete or not, display the text value of the item and lastly, a button to delete the item itself.

Save the component file, hop back on the simulator file, and try adding one or many items in this list.

See everything works. Even on refreshing the app, and the items do not disappear.

Bonus Section: Adding a Segment


In this section, you are going to separate the UI for managing the completed list of items and items that are pending to be done. To provide this feature, you are going to use Native Base library solely.

Keeping the data source same from the storage API, let modify the state by adding one more property. Open HomeScreen.js file and add the following.

1// add "filter" to existing the state
2state = {
3 todos: {},
4 isDataReady: false,
5 filter: 'Todo'

The value of the filter is going to be Todo by default. This means it is going to show the pending todo list items as the home screen to the user.

Next, you are going to add another handler function called filteredItems. This method will evaluate the value of the state and filter the values from the todos to match the state. Again, to use JavaScript filter method, you are going to convert todos object using lodash method _values.

1filteredItems = () => {
2 if (this.state.filter === 'Todo') {
3 return _values(this.state.todos).filter(i => {
4 return !i.isCompleted;
5 });
6 }
7 if (this.state.filter === 'Complete') {
8 return _values(this.state.todos).filter(i => {
9 return i.isCompleted;
10 });
11 }
12 return this.state.todos;

Next, let us modify the render method to achieve the desired result. Inside the render method, you are going to add a new UI element from Native base called Segment. This is going to display two buttons, each of which can be activated when pressed. The activation of each this button depends on the value of the state property filter.

1// import Segment from Native Base
2import { Button, Text as NBText, Segment } from 'native-base'
4// inside the render method...
6const { isDataReady, filter } = this.state
8// just before flatlist add a new view
10 <View style={styles.contentHeader}>
11 <Segment style={{ backgroundColor: '#ffffff' }}>
12 <Button active={filter === 'Todo'} onPress={() => this.setState({ filter: 'Todo' })}>
13 <NBText>Todo</NBText>
14 </Button>
15 <Button
16 last
17 active={filter === 'Complete'}
18 onPress={() => this.setState({ filter: 'Complete' })}
19 >
20 <NBText>Complete</NBText>
21 </Button>
22 </Segment>
23 </View>
25// styles corresponding to the new View element
27contentHeader: {
28 alignItems: 'center',
29 justifyContent: 'center'

Lastly, change the value of the data prop on FlatList and set it to the item returned from the method filteredItems().

2 data={_values(this.filteredItems())}
3 // rest remains same

You will get the following result.



Congratulations! You have just learned how to build an offline mobile application using latest tech stack and libraries like React Native, Expo, and Native Base component UI. You have learned many key points in this tutorial, and I hope you enjoyed following it, and reading it. Use the knowledge you have gained in this tutorial in a realtime application and show it to your peers. The possibilities to enhance this application or the use the knowledge is endless.

More Posts

Browse all posts

Aman Mittal author

I'm a software developer and a technical writer. On this blog, I write about my learnings in software development and technical writing.

Currently, working maintaining docs at 𝝠 Expo. Read more about me on the About page.

Copyright ©  2019-2024 Aman Mittal · All Rights Reserved.