<story><title>Turn your website into a Progressive Web App</title><url>https://mxb.at/blog/how-to-turn-your-website-into-a-pwa/</url></story><parent_chain></parent_chain><comment><author>finchisko</author><text>Please don&amp;#x27;t convert your website to PWA before thinking if it really adds an value to your visitors first. Some sites are just great as they&amp;#x27;re now. I understand you spent time &amp;quot;pimping up&amp;quot; your website, but No I don&amp;#x27;t want to receive push notification from your site, or ability to visit your website offline. Maybe I&amp;#x27;m visiting your website for just single article and you&amp;#x27;ll never see me again. It reminds me AMP situation. Those who stepped into hype train, are now those whose starting to realise that maybe it wasn&amp;#x27;t such a great idea at first place.</text></comment>
<story><title>Turn your website into a Progressive Web App</title><url>https://mxb.at/blog/how-to-turn-your-website-into-a-pwa/</url></story><parent_chain></parent_chain><comment><author>codedokode</author><text>This is clearly overengineering if one has to write and maintain a service worker just to be able to display a static site offline. How to debug it? How to see if any of your visitors cannot load site because of error in a service worker? How to decide which pages to preload for offline reading?&lt;p&gt;Also a service worker would add additional process in Chrome and require 30-40 Mb of RAM. I don&amp;#x27;t want service workers in my browser.&lt;p&gt;Well, web standards have always been this broken and illogical as long as I rememeber.</text></comment>