Book Image

Progressive Web Application Development by Example

By : Chris Love
Book Image

Progressive Web Application Development by Example

By: Chris Love

Overview of this book

Are you a developer that wants to create truly cross-platform user experiences with a minimal footprint, free of store restrictions and features customers want? Then you need to get to grips with Progressive Web Applications (PWAs), a perfect amalgamation of web and mobile applications with a blazing-fast response time. Progressive Web Application Development by Example helps you explore concepts of the PWA development by enabling you to develop three projects, starting with a 2048 game. In this game, you will review parts of a web manifest file and understand how a browser uses properties to define the home screen experience. You will then move on to learning how to develop and use a podcast client and be introduced to service workers. The application will demonstrate how service workers are registered and updated. In addition to this, you will review a caching API so that you have a firm understanding of how to use the cache within a service worker, and you'll discover core caching strategies and how to code them within a service worker. Finally, you will study how to build a tickets application, wherein you’ll apply advanced service worker techniques, such as cache invalidation. Also, you'll learn about tools you can use to validate your applications and scaffold them for quality and consistency. By the end of the book, you will have walked through browser developer tools, node modules, and online tools for creating high-quality PWAs.
Table of Contents (12 chapters)

Mastering the Cache API - Managing Web Assets in a Podcast Application

The most important service worker superpower is the ability to use a local response cache, making the network optional. Service workers can do this because they can intercept network requests and check if a response has previously been cached before passing the request to the network. They can also be programmed to cache any network response for future use. This allows the website to possibly load instantly and regardless of the network state, which is another way of saying your web apps can work offline.

This super power relies on two newer platform features, Fetch and the Cache APIs. Before adding caching to the Podstr application, we need to learn the details of the APIs.

You first saw fetch in Chapter 4, Service Workers – Notification, Synchronization, and Our Podcast App, but it was only a simple...