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)

Migrating a website to HTTPS

Regardless of whether you have a new or existing site, you should have a system to ensure that your site is implementing HTTPS correctly. Installing a certificate is just the start of the process. You must make sure that different aspects of your site are referencing HTTPS correctly.

This includes the links in your pages, handling links to your site, and your analytics and search engine profiles.

Even if your site uses HTTPS, the HTTP portion of any page that includes HTTP content can be read or modified by attackers. When an HTTPS page has HTTP content, it's called mixed content. You might think the page is secure, but it isn't because of the mixed content.

When a page has mixed content, browsers have visual queues to alert the user to the insecure state. You cannot rely on seeing https in the address bar—look for the green lock....