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)

The singleton pattern

The singleton pattern is a class that can have only one instance. By its design, whenever we attempt to create a new instance, it will either create an instance for the first time or return the one that was created previously.

How is this pattern useful? If we want to have a single manager for certain things, this comes in handy, whether it be an API manager or cache manager. For instance, if you need to authorize the API to get the token, you will only want to do this once. The first instance will initiate whatever work is necessary and then any other instance will reuse the work that has already been done. This use case was abused mostly by server-side applications, but more and more people have come to realize that there are better alternatives.

Such use cases can nowadays be easily countered by better patterns. Instead of creating a singleton pattern...