Beyond single-page apps: alternative architectures for your PWA (Google I/O '18)

Beyond single-page apps: alternative architectures for your PWA (Google I/O '18)


beyond shared hosting

Building a Progressive Web App (PWA) doesn’t mean building a single page app! This session will deep-dive into alternative architectures for content-focused PWAs, and help you make the right decision for your specific use case. You’ll also get insights on how the Workbox project provides developers with an easy path towards using the web platform features that provide the foundation for these architectures.

Rate this session by signing-in on the I/O website here →

SO PWA Live Demo →
SO PWA Source Code →
Workbox →
PWA Guidance →

Watch more Chrome and Web sessions from I/O ’18 here →
See all the sessions from Google I/O ’18 here →

Subscribe to the Chrome Developers channel →

#io18

8 thoughts on “Beyond single-page apps: alternative architectures for your PWA (Google I/O '18)

  1. Hey, I am integrating workbox to my web project with the goal of making it PWA.
    In most of the tutorials, people mention how to precachHTMLml and dynamically cache JSON responses.

    My web project is server-side rendered, I use twirl templating and serve compiled template from the server on each route change. So there is no way that I can precache HTML. I have to cache HTML dynamically. I don't see anyone talking about this. So can you please let me know what I am missing here.

Leave a Reply

Your email address will not be published. Required fields are marked *