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)

Summary

I have always been a fan of tooling and automation to make my applications faster to code with more maintainability and hopefully fewer bugs, but it is important you have a firm understanding of what any generate code or component is doing. This is why even when you are using the progressive web application tools I highlighted in this chapter that you need to be able recognize their strengths and limitations.

You also need to have a firm understanding of how complex features like service workers function before you start using a tool like Workbox. Without this fundamental knowledge, you can quickly make a service worker that does not work as you expect. You also need to have a strong knowledge foundation to help you debug issues when these tools break.

I chose four tools I think add the most value for the developers to review in this chapter. This by no means that all...