Book Image

Progressive Web Apps with React

By : Scott Domes
Book Image

Progressive Web Apps with React

By: Scott Domes

Overview of this book

For years, the speed and power of web apps has lagged behind native applications. Progressive Web Apps (PWAs) aim to solve this by bridging the gap between the web apps and native apps, delivering a host of exciting features. Simultaneously, React is fast becoming the go-to solution for building modern web UIs, combining ease of development with performance and capability. Using React alongside PWA technology will make it easy for you to build a fast, beautiful, and functional web app. After an introduction and brief overview of the goals of PWAs, the book moves on to setting up the application structure. From there, it covers the Webpack build process and the process of creating React components. You'll learn how to set up the backend database and authentication solution to communicate with Firebase and how to work with React Router. Next, you will create and configure your web app manifest, making your PWA installable on mobile devices. Then you'll get introduced to service workers and see how they work as we configure the app to send push notifications using Firebase Cloud Messaging. We'll also explore the App Shell pattern, a key concept in PWAs and look at its advantages regarding efficient performance. Finally, you'll learn how to add of?ine capabilities to the app with caching and confirm your progress by auditing your PWA with Lighthouse. Also, you'll discover helper libraries and shortcuts that will help you save time and understand the future of PWA development.
Table of Contents (21 chapters)
Title Page
Credits
About the Author
About the Reviewer
www.PacktPub.com
Customer Feedback
Preface

Managing data flow


One of the important principles of React is something called uni-directional data flow.

In the prototypical React app, data is stored in the state of the highest-level component, and passed down to lower-level components via props. When the user interacts with the application, the interaction event is passed up through the component tree via props, until it arrives at the highest-level component, which then modifies the state based on the action.

The application then forms a big circle--data goes down, events come up, and new data goes down. You can also think of it as an elevator, departing from the top floor full of data, and then coming back up full of events.

The advantage of this approach is that it's easy to follow the flow of data. You can see where it's going (to which child components), and why it's changing (in reaction to which events).

Now, this model runs into problems with a complex application with hundreds of components. It becomes unwieldy to store all your...