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

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.

#io18 event: Google I/O 2018; re_ty: Publish; product: Chrome - General; fullname: Jeff Posnick; event: Google I/O 2018;

[sharonx]

11:33 how to handle caching headers? 19:20 why do you bother keeping the staic part in html files and precaching them, when you could have just written them as JS template literal, like you did with the dynamic parts?

[Marco.Hochmuth]

Thanks YouTube for 1.5 playback speed. Great talk though!

[codlgaez]

31:45 cross-language templating libraries are common but.. routing? If anyone has got examples of cross-language routing, I'm interested

[lzantal]

Do your self a favor and set the playback to 2x!!! Such a good talk but boy its slow.

[rahuram]

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.

[nicolasparada]

Service workers and streams are so powerful 💪

[sharonx]

Hey, I do not want to use Firebase and you can't make me to use Firebase.

[AlexBerg]

So good to see a PWA which isn't a JS SPA.😘

[carlerikkopseng]

2024. This still is not the year of the Streaming API for the general public. We do see some adoption, such as Remix providing streamed content.