Book Image

React Native - Building Mobile Apps with JavaScript

By : Vladimir Novick
Book Image

React Native - Building Mobile Apps with JavaScript

By: Vladimir Novick

Overview of this book

<p>The emergence of React Native has made creating mobile apps in JavaScript easier for developers. This book introduces you to the React Native framework and the mobile apps development process. It starts with how React Native fits into the world of hybrid apps, and why it’s a popular framework. You’ll learn how React Native works under the hood--compiling JavaScript to Native code to bridge JavaScript and native apps. Also, you’ll learn how to write React Native components and use the ReactJS way of structuring your app. Understand how to use the industry standard Redux architecture as well as MobX--a newly emerging approach for state management--making your apps more robust and scalable.</p> <p>The mobile native world can be intimidating, with lots of platform-specific APIs. In this book, you’ll learn about the most important APIs with help of the real-world examples. You’ll also learn about the community packages that can help speed up your development. The book explains how to use these packages with JavaScript code, include native modules in your application, and write the modules yourself. Throughout the book, you will see examples of WhatsApp, Instagram, and YouTube apps and learn how to recreate them. You’ll also learn debugging and testing techniques, authentication, dealing with real data, and much more.</p> <p>At the end we will walk through design to production process of Twitter app clone and will explain application release process to App Store and Play Store</p>
Table of Contents (13 chapters)

What is Flux architecture?

Flux architecture didn't come from a void. There were several factors responsible for its emergence. So, it's important to understand these factors.

For years, the MV* pattern was popular among most major frameworks, such as Backbone, Angular, Knockout, Ember, and more. MV* is a popular shorthand for variations of MVC architectural pattern, which the above-mentioned frameworks tried to implement, not necessarily following the pattern strictly. The idea of all patterns was to separate Model, and View behind the Controller. Since it wasn't always the controller, but sometimes the Presenter or View model, the pattern is called MV*.

Even though MVC architectural pattern is common and widely used, it introduces several problems.

MVC problem

...