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 RAIL pattern

The RAIL pattern is an acronym used by the Google Chrome team to define one of the many WPO patterns you should try to follow. Its goal is to ensure your user experience is responsive:

  • Response: How quickly there is a response when there is any input
  • Animation: Includes visual animation, scrolling, and dragging
  • Idle: Background work
  • Load: How quickly a page can achieve the first meaningful paint

Where the PRPL pattern is concerned with resource loading, RAIL is about the runtime user experience or what happens once the resources are loaded.

The pattern is designed to be user centric, focusing on performance first. The four aspects that make up the acronym are distinct areas of a web application and page's life cycle, or what happens once the bytes are loaded.

Consider the different areas where performance is important: loading, rendering and responding...