Your users deserve a fast and responsive web app and PWAs help you step that up a notch through notifications, offline support and more. There’s a lot that goes into that from understanding how the DOM tree works and how that plays with CSS and JavaScript to how to leverage the ServiceWorker for cashing and push notifications.

In this session, we’ll build a PWA that show cases many of the things you need to keep in mind when building a great and fast progressive web app.


Comments are closed.

Cal Evans at 10:37 on 9 Feb 2019

If you know what a PWA is, you are ahead of the pack.
If you know what a PWA is, you need to see this talk. This is not a beginner talk, this one has some serious tech chops.

Hector Reyes at 13:01 on 9 Feb 2019

Really enjoyable and necessary talk, not only for pwa but web dev in general

William Ibarra at 13:34 on 9 Feb 2019

Excellent info on making your web app faster. Since I have a web app in production it gave me good roadmap for improvements.

Peter Fisher at 20:55 on 10 Feb 2019

Very helpful and not just for PWAs. There are a lot of things I can take away from this. Thank you

Miro Svrtan at 10:04 on 11 Feb 2019

Very interesting topic and Josh did a great intro to the subject.

A really big putoff for me was a 5-10 min introduction on 'new Microsoft', 'Microsoft is great, 'Edge', 'going for Chromium', etc... as the subject at hand wasn't really related to those things. First 5 minutes should get me interested in the subject and make me wanna stay there for the rest, not used as a commercial spot for the speakers employer... Once we got to the subject, 15-20 minutes down the line my interest was gone :(

Shane jessop at 18:09 on 11 Feb 2019

Great information thank you. Could you share your slides for review? Thank you.

Ian Littman at 01:40 on 12 Feb 2019

Nicely done...and that's despite connectivity issues resulting in a backup plan rather than a live demo! The digression into why MS is hopping on the Chromium bandwagon also fits super well into the presentation topic, so please keep that in :)

I recall another attendee asking for benchmark performance differences between vanilla JS's querySelector and jQUery's, similar to the comparison you did between a bunch of frameworks on document.getElementById(). Seems like it'd be a decent addition if you can find a like-for-like test, since fewer folks know about querySelector, it has a bit wider use case than getElementById, and honestly it's relatively easier to type (though of course $('.someClass') is easier still).

One other question: I assume you'd let Babel/Gulp pull in polyfills as needed for older browser support, rather than explicitly adding in individual polyfills, hence why you didn't (or maybe I just didn't recall) include mention of the latter in your talk?