Progressive Web Application Development by Example

Lazy-loading non-critical and dynamic routes

Not every page in every website can or should be cached ahead of time. As you saw in  Chapter 5, The Service Worker Life Cycle, you should also have cache invalidation logic in place to ensure that you supply the freshest content.

Dynamic content, like the available ticket events or even an updated list of podcast episodes, is difficult to cache long-term. But you can provide a better experience than just waiting to download all of the page's resources.

This is where employing one or more of the common caching strategies is helpful. You can also combine your rendering strategy with the app shell concept and build the page as assets are loaded or updated.

You can also pre-cache and update common ...