<LEARN/>
← Frontend path

// Frontend path · Step 09 · <pwa>

PWA

Installable, offline-ready web apps.

// what you'll learn

  • →Web app manifest
  • →Service workers
  • →Offline caching strategies
  • →Installation UX

// why it matters

PWAs show you understand how the browser platform really works.

// project ideas to build

  • Installable notes app

    beginner

    Add a manifest and icons so the app can be installed.

  • Offline reader

    intermediate

    Cache articles so they can be read with no connection.

Project ideas written by LEARN. Build them on the canvas or in your own repo.

// every lesson in the course

0/25

  1. 01Welcome ↗A course that breaks down every aspect of modern progressive web app development.lesson + test
  2. 02Progressive web apps ↗Progressive Web Apps (PWAs) are web apps built and enhanced with modern APIs to deliver enhanced capabilities, reliability, and installability while reaching anlesson + test
  3. 03Getting started ↗If you want to build a Progressive Web App, you may be wondering where to start, if it's possible to upgrade a website to a PWA without starting from scratch, olesson + test
  4. 04Foundations ↗All Progressive Web Apps are, at their core, modern websites, so it's important that your website has a solid foundation in responsive design, mobile and everytlesson + test
  5. 05App design ↗One of the key differences between Progressive Web Apps and classic websites and web apps is installability. This creates a standalone experience more integratelesson + test
  6. 06Assets and data ↗A Progressive Web App is a website; all its assets are the same as on the web, but with new tools to make those assets load fast when online andavailable when olesson + test
  7. 07Service workers ↗Service workers are a fundamental part of a PWA. They enable fast loading (regardless of the network), offline access, push notifications, and other capabilitielesson + test
  8. 08Caching ↗You can use the Cache Storage API to download, store, delete or update assets on the device. Then these assets can be served on the device without needing a netlesson + test
  9. 09Serving ↗Using the service worker's fetch event, you can intercept network requests and serve a response using different techniques.lesson + test
  10. 10Workbox ↗Workbox is a set of modules that simplify common service worker interactions such as routing and caching. Each module addresses a specific aspect of service worlesson + test
  11. 11Offline data ↗To build a solid offline experience you need to implement storage management. Tools like IndexedDB, Cache, Storage Manager, Persistent Storage, and Content Indelesson + test
  12. 12Installation ↗Installed apps are easy to access and can take advantage of some deeper integrations with the OS. Learn to make your PWA installable and gain those benefits.lesson + test
  13. 13Web app manifest ↗The web app manifest is a JSON file that defines how the PWA should be treated as an installed application, including the look and feel and basic behavior withilesson + test
  14. 14Installation prompt ↗For sites that pass the PWA install criteria, the browser triggers an event to prompt the user to install it. The good news is that you can use this event to culesson + test
  15. 15Update ↗Chances are your PWA needs updating. This chapter gives you the tools to update different parts of your PWA, from assets to metadata.lesson + test
  16. 16Enhancements ↗Your user expects a good experience. In this chapter, you will see how to enhance your PWA with splash screens, app shortcuts, and how sessions work.lesson + test
  17. 17Detection ↗Identifying how your users interact with your app is useful in customizing and improving the user experience. For example, you can check whether your app is alrlesson + test
  18. 18Os integration ↗Your PWA now works outside the browser. This chapter covers how to integrate further with the operating system once users install your app.lesson + test
  19. 19Windows ↗A PWA outside of the browser manages its own window. In this chapter, you will understand the APIs and capabilities for managing a window within the operating slesson + test
  20. 20Experimental ↗There are PWA capabilities that are still under construction and you can be part of their development. In this chapter you'll learn about the Fugu project, how lesson + test
  21. 21Tools and debug ↗We will explore the tools available to develop, debug, and test your Progressive Web Apps.lesson + test
  22. 22Architecture ↗You make some decisions when developing a PWA, such as whether to create a single page application or a multi-page application, and whether you will host it in lesson + test
  23. 23Complexity ↗Keeping a web app simple can be surprisingly complicated. In this module, you will learn how web APIs work with threading and how you can use this for common PWlesson + test
  24. 24Capabilities ↗PWAs are not just tied to the screen. This chapter is about the capabilities that a PWA has today in terms of hardware, sensors, and platform usage.lesson + test
  25. 25Conclusion ↗Next steps and resources.lesson + test

Original lessons by web.dev. Course content belongs to its creators.