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)

Auditing the site for any HTTP:// link references

It does not matter if you have a single-page website or one that contains a million URLs, you need to audit each page for external http:// link references. This include anchor tags as well as any link tags you may have in your document's head.

All third-party hosted assets, such as CSS, JavaScript libraries, images and fonts on public CDNs, as well as third-party services, such as Google Analytics (GA), are prime targets for HTTP references. These are often overlooked because they are not "owned" by the business.

By now, any reputable third-party service offers HTTPS support. If it does not, you may need to require them to offer HTTPS or find a new provider it they refuse.

As with the preceding Microsoft example , you should also make sure that all references to assets in your site are either HTTPS or are simply...