With React Native, the most important thing is to understand the ecosystem and how it comes together to create an app. By understanding the overall architecture, we will be able to take the full of advantage the platform.

The course will start by covering the fundamentals like setting up the navigation, setting up the screens, styles, and the UI elements, before moving on to more advanced topics such as state management, crash/error reporting, setting up analytics and middlewares, debugging, and performance optimizations. We will also learn how to avoid/fix frame drops - possibly the most watched parameter of any UI application.

We will also build a Design System and will follow the [Atomic Design Pattern](https://atomicdesign.bradfrost.com/chapter-2/) of building layouts. A Design System primarily consists of three parts:
- UI Inventory and Patterns
- Typography
- Spacing and Styles

We will cover these in detail through the modules of the course. We will also learn about the React Native best practices, how to avoid rabbit holes, and focus on building a performant app.

**This is an opinionated way of building apps with React Native**. The fundamentals discussed in the course, like Atomic Design Pattern and Design System, can be applied to building any UI application, not just ones using React Native.

## One Complete App

The course comes with one complete eCommerce sample app that is discussed through the modules of the course.

## Up-to-date

The course builds on an open-source boilerplate template and is kept up to date with React, React Native and dependent library versions. It is also updated with the latest APIs and libraries that are introduced, like Hooks, hermes, flipper etc.

## Why this course

React Native for JavaScript Developers using TypeScript is based on years of experience in building React Native apps on production. The open-source boilerplate code discussed in the course is the platform for multiple apps on App Store and Play Store today. One of them being a Unicorn.

We will take a **Product** based development approach to building apps. React Native abstracts out a lot of platform specific nuances, so wouldn't focusing on building the app as an experience make the most sense. The design pattern will help us exactly with that, and we will put together a structure that is both scalable and extensible. This architecture also helps keep the design separate from the development.

At the end of this course, you will not only be able to build real-world apps with React Native, but also have the fundamentals of building any enterprise UI application.

Discord [channel](https://discord.gg/fz43pNnh)

Code along, and learn to build scalable and performant apps with React Native, from a Product perspective.

The newline Guide to React Native for JavaScript Developers using TypeScript

---
title: Intro to Managing React Application State With Flux and Redux
slug: redux
privateVideoUrl: https://fullstack.wistia.com/medias/2ztpdpnooe
isPublicLesson: false
playerCode: #1D5C72
role: LESSON
description: Let's learn about Flux and Redux.
---

## Flux

:::note
Images and examples in this lesson are from the official Facebook Flux [overview](https://facebook.github.io/flux/docs/.in-depth-overview) page and official Redux [getting started guide](https://redux.js.org/introduction/getting-started).
:::

Flux applications have three major parts: the dispatcher, the stores, and the views (React components). Data in a Flux application flows in a single direction:

![](https://d2uusema5elisf.cloudfront.net/courses/the-newline-guide-to-react-native-for-javascript-developers/module_04/lesson_01.02/public/assets/flux-simple.png)

_ source: <https://facebook.github.io/flux/docs/in-depth-overview> _

> A unidirectional data flow is central to the Flux pattern, and the above diagram should be the primary **mental model for the Flux programmer**.

What this means is that data always flows from the parent component to the child component. Unlike Angular and other frameworks where updating a property in the child component would update it for the parent too (i.e. globally), this is not the case with Flux.

![](https://d2uusema5elisf.cloudfront.net/courses/the-newline-guide-to-react-native-for-javascript-developers/module_04/lesson_01.02/public/assets/flux-action.png)

_ source: <https://facebook.github.io/flux/docs/in-depth-overview> _

A Flux application, from the component's points of view, is a set of actions that it can perform, and these actions are predefined. These actions are assigned a type and passed to stores by dispatchers. Stores contain the application state and logic, which then update the application's state. This change in state is then reflected in views by controller-views which are listening for change.

## Redux

Redux is an open-source JavaScript library for managing the application state. It was created by Dan Abramov and Andrew Clark, who also authored Facebook's Flux architecture. It is the de facto choice for managing state in React applications.

The core concepts of Redux are: