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 Fetch API

Way back in 1996, Internet Explorer introduced the iframe element as a way to load web content asynchronously in a web page. Over the next two years, the concept evolved into the first implementation of what we now know as the XMLHttpReqest object.

Back then, it was known as XMLHTTP and was first shipped in Internet Explorer 5.0. Soon after, Mozilla, Safari, and Opera all shipped implementations of what we now call XMLHttpRequest.

Up to this point, web pages were static and required an entire reload when a user navigated from one page to another inside the same site.

In 2004, Google started making wide use of what we now call AJAX in Gmail and Google Maps. They showed us how to leverage in-browser requests to the server and how to manipulate the DOM in response to the server's payload. This is typically done by calling an API that returns JSON data.

As with...