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
About the Author
About the Reviewer
Customer Feedback

What is caching?

Caching is the act of reducing network requests or computation. Backend caching may consist of saving the result of a rigorous computation (say, generating statistics) so that when the client requests it a second time, we don't have to crunch the numbers again. Client-side caching usually consists of saving the response of a network request so that we don’t have to make that call again.

As we said before, service workers are bits of code that sit between our application and the network. This means they are perfect for caching, as they can intercept a network request and respond with the requested file, grabbing it from the cache instead of the server; time is saved.

From a broader perspective, you can think of caching as not having to do the same thing more than once, using memory to store the result.

The upside of caching with Progressive Web Apps is that since the cache is stored in device memory, it's available regardless of network connectivity. This means everything stored...