I totally get the push (pun intended) to make that happen. There is an omnipresent sentiment that we want the web to win, as there should be in this industry. Losing on the web means losing to native apps on all the … Read article
One of the sessions from the Chrome Dev Summit, hosted by Das Surma and Daniel Walmsley. It's not so much about WordPress as it is about CMS powered sites that aren't really "apps", if there is such a thing, and the possibility of turning that site into a Progressive Web App
I find the CMS + PWA combo interesting because:
If you aren't stoked about AMP, and let's face it, a lot of people are not stoked
It lists a whole bunch of PWAs out there and you can filter them by Lighthouse metrics – that’s the auditing tool from Google that scores a web app and gives us developers the ability to improve them.… Read article
I hadn't considered the fact that if you're fingerprinting your assets (e.g. style.987987090897.css) to take advantage of browser cache, you'll need to update your Service Worker every time you do that. But I guess you've got a build step anyway, so it can be updated in both places:
... we used a NodeJS module called Stacify to automatically create new version numbers in all the places when a file is changed.
Progressive Web Apps (sometimes referred to as PWAs, because everything in tech needs an acronym) is the encapsulating term for websites following a certain approach, that meet particular technical criteria. The "app" involvement in the name isn’t an accident – these creations share much of the functionality that you’ll find in native experiences – but really, they're just websites.
It's like if you build a website that is so damn good, you get to have a home … Read article