AMP to PWA
In this approach, the AMP page bootstraps or warms up the PWA. The AMP page installs a service worker on the device and the service worker caches resources that will be used by the PWA. When the user subsequently visits the main PWA website, most of the resources are already loaded and the PWA can be rendered quickly.
This type of deployment thus capitalizes initially on the speed, efficient loading, and performance of the lightweight AMP page, and subsequently on the richness of the PWA page. It differs from the previous approach in that the PWA pages don't explicitly use the AMP library--they're not AMP pages and can include whatever technologies and features you like, such as JavaScript or anything else you might fancy.
So the ...
Become an O’Reilly member and get unlimited access to this title plus top books and audiobooks from O’Reilly and nearly 200 top publishers, thousands of courses curated by job role, 150+ live events each month,
and much more.
Read now
Unlock full access