{"id":1551,"date":"2023-01-17T12:06:19","date_gmt":"2023-01-17T12:06:19","guid":{"rendered":"https:\/\/www.workfall.com\/learning\/blog\/?p=1551"},"modified":"2025-09-23T03:55:50","modified_gmt":"2025-09-23T03:55:50","slug":"how-to-manage-state-in-a-react-application-using-redux","status":"publish","type":"post","link":"https:\/\/learning.workfall.com\/learning\/blog\/how-to-manage-state-in-a-react-application-using-redux\/","title":{"rendered":"How to Manage State in a React Application Using Redux?"},"content":{"rendered":"Reading Time: <\/span> 6<\/span> minutes<\/span><\/span>\n
\"Manage<\/figure>\n\n\n\n

The rise of JavaScript frameworks such as React opened a new possibility in the world of Single Page Applications (SPAs). It became a lot easier to develop reusable components and create robust applications with JavaScript. However, as the applications grew, there arose a complexity \u2013 state management. That’s why we’ll discuss about how to Manage State in a React Application Using Redux. <\/p>\n\n\n\n

Developers ran into issues of having to pass state as props through components that are not even using the props, which is referred to as prop drilling. The mentioned scenario would come to the rescue if we the said components had a parent-child relationship. What about components that are not in any way in the same hierarchy but need to share the same state? Another fix would have been to raise the state to a shared parent component and then apply prop drilling.<\/p>\n\n\n\n

What Is State Management?<\/h2>\n\n\n\n

State management offers a much cleaner and more organized way of handling component states by managing the state of the whole application from one central place. State management ranges from simple solutions such as Context API to more complex solutions such as Redux. Sometimes using a solution such as Redux might be overkill for small applications but is very beneficial for large applications.<\/p>\n\n\n\n

What Is Redux?<\/h2>\n\n\n\n

Redux is a state management library that treats the data of JavaScript applications as immutable and only creates shallow copies hence preventing re-rendering of the application as a performance boost. Redux boasts of a large ecosystem and also a robust Redux Toolkit that helps in simplification of tasks such as initial setup and addition of new elements.<\/p>\n\n\n\n

Hands-On<\/h2>\n\n\n\n

In this blog, we are going to use a simple stepper form which consists of four lazy-loaded forms. These forms all together constitute one data object even though they are rendered separately. Typically these are four components or steps mentioned below share the same state yet not in the same hierarchy.<\/p>\n\n\n\n

Step One:<\/strong><\/p>\n\n\n\n

\"Manage<\/figure>\n\n\n\n

Step two:<\/strong><\/p>\n\n\n\n

\"Manage<\/figure>\n\n\n\n

Step three:<\/strong><\/p>\n\n\n\n

\"Manage<\/figure>\n\n\n\n

Step four:<\/strong><\/p>\n\n\n\n

\"Manage<\/figure>\n\n\n\n

The typical behavior of the above stepper form is that, once you fill in the first step and navigate to the second step, you will lose all the input in the first step. We shall solve this using Redux state management. When the save button is clicked, it will call the dispatch hook to save the form to the state so that if you navigate back to a previous tab, you will find the information.<\/p>\n\n\n\n

Let us begin with the coding then. Refer to the folder structure shown below to get started:<\/p>\n\n\n\n

\"Manage<\/figure>\n\n\n\n

Installations<\/h3>\n\n\n\n

For this project, we will be using Tailwind CSS. To install and configure Tailwind CSS kindly follow the guide written here: https:\/\/tailwindcss.com\/docs\/installation<\/a>. One more tailwind plugin for the forms is needed which can be installed with the yarn add -D @tailwindcss\/forms<\/strong> command and then add it to the plugins in the tailwind.config.js<\/strong> file.<\/p>\n\n\n\n

tailwind.config.js:<\/strong><\/p>\n\n\n\n

\"\"\/<\/figure>\n\n\n\n

To install Redux, we shall use the yarn add react-redux @reduxjs\/toolkit<\/strong> command.<\/p>\n\n\n\n

We shall also use the useForm<\/strong> library to manage all our form inputs and data. Use the yarn add react-hook-form<\/strong> to install the package.<\/p>\n\n\n\n

Data Modelling<\/h3>\n\n\n\n

We shall start by writing type definitions for the models and the state. In the src<\/strong> folder create a folder and name it @types<\/strong> inside it add two files model.d.ts<\/strong> and state.d.ts<\/strong>.<\/p>\n\n\n\n

model.d.ts:<\/strong><\/p>\n\n\n\n

\"\"\/<\/figure>\n\n\n\n

state.d.ts:<\/strong><\/p>\n\n\n\n

\"\"\/<\/figure>\n\n\n\n

Configuring the store<\/h3>\n\n\n\n

Start by creating a folder named redux<\/strong> in the src<\/strong> folder. Note that this naming is just by convention. Inside the redux<\/strong> folder we shall have a reducers<\/strong> folder and actions.json<\/strong>, hooks.ts<\/strong> and store.ts<\/strong> files.<\/p>\n\n\n\n

store.ts:<\/strong><\/p>\n\n\n\n

We configure the store by bootstrapping all the reducers. Since we are using TypeScript, we are inferring the types so that we do not have to manually update the types every time we add a new reducer.<\/p>\n\n\n\n

\"\"\/<\/figure>\n\n\n\n

hooks.ts:<\/strong><\/p>\n\n\n\n

To prevent circular import dependency, we define all our Redux hooks in one file.<\/p>\n\n\n\n

\"\"\/<\/figure>\n\n\n\n

reducers\/stepper.reducer.ts:<\/strong><\/p>\n\n\n\n

The reducer is where all the data processing takes place to create the new state from the previous. Each time an action is dispatched, the reducer receives the event and produces the desired output.<\/p>\n\n\n\n

\"\"\/<\/figure>\n\n\n\n

actions.json:<\/strong><\/p>\n\n\n\n

\"\"\/<\/figure>\n\n\n\n

index.tsx:<\/strong><\/p>\n\n\n\n

\"Manage<\/figure>\n\n\n\n

Using the store as the source of truth<\/h3>\n\n\n\n

In our stepper components, we shall write our forms using the useForm<\/strong> library. When the component is initialized we shall fetch the form data from the store using the useAppSelector<\/strong> hook and use them as default values just in case the user had made some entries.<\/p>\n\n\n\n

When the user clicks save we shall dispatch the SAVE_FORM<\/strong> action to enable the reducer to update the state.<\/p>\n\n\n\n

PersonalInfo.tsx:<\/strong><\/p>\n\n\n\n

\"\"\/<\/figure>\n\n\n\n

ContactInfo.tsx:<\/strong><\/p>\n\n\n\n

\"\"\/<\/figure>\n\n\n\n

AddressInfo.tsx:<\/strong><\/p>\n\n\n\n

\"Manage<\/figure>\n\n\n\n

ConfirmInfo.tsx:<\/strong><\/p>\n\n\n\n

\"Manage<\/figure>\n\n\n\n

Conclusion<\/h2>\n\n\n\n

In this blog, we have demonstrated how to use Redux to manage the state of a simple stepper form which consists of four lazy-loaded forms. This is just one of the scenarios where you would want to use a state management library like Redux i.e. when you have several components that share the same data and you want to avoid unnecessary prop drilling. Whereby prop drilling refers to passing the state as props through a common parent component in a component hierarchy, which just makes your code bloated and unoptimized.<\/p>\n\n\n\n

Another consideration to make when choosing to use Redux is when you are making too many API calls for the same data in different components. Especially if you are incurring charges per API call. You would want to manage those costs by making a single API call and sharing that data throughout your application using Redux.<\/p>\n\n\n\n

Lastly, the code used in this blog is found at https:\/\/github.com\/workfall\/workfall-redux<\/a>.<\/p>\n\n\n\n

We will come up with more such use cases in our upcoming blogs.<\/p>\n\n\n\n

Meanwhile\u2026<\/strong><\/p>\n\n\n\n

If you are an aspiring React Developer and want to explore more about the above topics, here are a few of our blogs for your reference:<\/p>\n\n\n\n

Stay tuned to get all the updates about our upcoming blogs on the cloud and the latest technologies.<\/p>\n\n\n\n