From a88678d47a626664eb21e4dc93808067742a4644 Mon Sep 17 00:00:00 2001 From: Tac Tacelosky Date: Tue, 19 Mar 2024 16:32:05 -0600 Subject: [PATCH] tweak PWA definition PWA don't require all pages to be preloaded. They do require a service worker. This tweak clarifies that. --- src/documents_en/v2/guide/pwa/intro.html | 8 ++++++-- 1 file changed, 6 insertions(+), 2 deletions(-) diff --git a/src/documents_en/v2/guide/pwa/intro.html b/src/documents_en/v2/guide/pwa/intro.html index ae126227a..3bca230fd 100644 --- a/src/documents_en/v2/guide/pwa/intro.html +++ b/src/documents_en/v2/guide/pwa/intro.html @@ -32,11 +32,15 @@ #### Requirements For a site to be classified as a PWA, and to prompt the user to add it to their home screen (on Chrome), it must: - - Load all URLs while offline - - Be served over *https* + - Be served over *https* (or localhost, for testing) - Have a manifest file + - Register a service worker - Have an icon +#### Suggestions + - Implement a [caching strategy](https://developer.mozilla.org/en-US/docs/Web/Progressive_web_apps/Guides/Caching) for css, javascript, json, etc. + - Pre-caching every page url and assets allows the app to run offline + These are the most basic requirements, but there are many more things you can and should do to improve the user's experience. #### Platform Support