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)

Immutability with TypeScript

In this section, I want to reiterate a point on immutability. This topic is huge in JavaScript, and in some cases, TypeScript may be a much better solution than any other path to immutability.

TypeScript comes with the special readonly keyword that enforces that a certain variable is read-only. You cannot mutate such a variable. This is enforced at compile time. Hence, you have no runtime checks for immutability. If this is a huge win for you, then you may not even need any API, such as Immutable.js. Immutable.js shines when you are required to clone huge objects to avoid mutations. If you can get away with a spread operation on your own, then it means your object may not be big enough for Immutable.js.

readonly

...