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)

The PWA ticket JavaScript architecture

Similar to the Podstr application, the PWA ticket app utilizes a combination of third-party libraries and application-specific JavaScript.

The following screenshot shows how the JavaScript files are organized in the source code:

The custom service worker logic or workflow utilizes different libraries to render content on the client. The two third-party libraries are localForage for IndexedDB interactions and Mustache to render markup.

localForage ( is another IndexedDB wrapper. It provides a simple interface that mimics localStorage. The main difference is that localForage supports promises, making it asynchronous.

There are three polyfils, and these are Object.assign, Promise, and Fetch.

Each page uses a few application-specific libraries: api and push-mgr, and common application modules. Each...