Book Image

Hands-On Design Patterns with React Native

By : Mateusz Grzesiukiewicz
Book Image

Hands-On Design Patterns with React Native

By: Mateusz Grzesiukiewicz

Overview of this book

React Native helps developers reuse code across different mobile platforms like iOS and Android. This book will show you effective design patterns in the React Native world and will make you ready for professional development in big teams. The book will focus only on the patterns that are relevant to JavaScript, ECMAScript, React and React Native. However, you can successfully transfer a lot of the skills and techniques to other languages. I call them “Idea patterns”. This book will start with the most standard development patterns in React like component building patterns, styling patterns in React Native and then extend these patterns to your mobile application using real world practical examples. Each chapter comes with full, separate source code of applications that you can build and run on your phone. The book is also diving into architectural patterns. Especially how to adapt MVC to React environment. You will learn Flux architecture and how Redux is implementing it. Each approach will be presented with its pros and cons. You will learn how to work with external data sources using libraries like Redux thunk and Redux Saga. The end goal is the ability to recognize the best solution for a given problem for your next mobile application.
Table of Contents (13 chapters)

Mutable and immutable objects

This concept surprised me in one of my coding interviews. At the beginning of my career, I had little knowledge of mutable and immutable objects and it backfired without me even realizing the root cause.

In Chapter 5, Store Patterns, I explained the basics of mutability and immutability. We even used the Immutable.js library. That part of the book was heavily focused on the store. Now let's look at the bigger picture. Why do we even need mutable or immutable objects?

Usually, the main reason is the ability to quickly reason about our application's behavior. For instance, React wants to quickly check whether it should re-render components. If you create object A and you are guaranteed that it won't ever change, then to reassure yourself that nothing changed, the only thing you need to do is compare the reference to the object. If it...