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)

Making Your Website Secure

It's surprising that no website utilizes HTTPS today. Securing a website was difficult in the past, but most barriers to security have been erased in recent years. Some of those barriers included the price, technical requirements, and performance concerns.

To qualify as a progressive web application, a website must be served via HTTPS. Service workers are gated behind HTTPS because they run in the background and are designed to perform tasks that could compromise privacy if they are not protected.

With reduced and eliminated barriers, search engines and browsers have increased HTTPS's visibility to consumers because of improved search engine rankings, visual queues in the browser, and the gating APIs behind HTTPS:

This means that every website now has incentives to migrate from HTTP to HTTPS. But there are still some issues that you will need...