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)

Service worker clients

I have mentioned the service worker clients several times in this chapter. The obvious definition is a browser tab with a site's page open. While this will be the case in most situations, it is not the only client type.

Because service workers execute in a separate context from a browser tab's UI thread, they can service multiple clients. This includes multiple tabs, push notifications, and background sync events. The latter two are clients without a traditional user interface.

The service worker specification says (

"A service worker client is an environment."

It goes on to define a series of potential client types. The concept of a service worker client is designed not to account for the obvious browser tab, but any process that might trigger a service worker event...