Why Microsoft and Google love progressive web apps | Computerworld

This content originally appeared on Modern Web Development with Chrome and was authored by Paul Kinlan

<p>A nice post about PWA from <a href="https://elgan.com/">Mike Elgan</a>. I am not sure about Microsoft's goal with PWA, but I think our's is pretty simple: we want users to have access to content and functionality instantly and in a way they expect to be able to interact with it on their devices. The web should reach everyone across every connected device and a user should be able to access in their preferred modality, as an app if that's how they expect it (mobile, maybe), or voice on an assistant etc.</p> <p>We're still a <a href="https://paul.kinlan.me/the-headless-web/">long way from the headless web</a>, however, one thing really struck me in the article:</p> <blockquote> <p>Another downside is that PWAs are highly isolated. So it’s hard and unlikely for different PWAs to share resources or data directly.</p> </blockquote> <p><a href="https://www.computerworld.com/article/3314746/mobile-apps/why-microsoft-and-google-love-progressive-web-apps.html">Read full post</a>.</p> <p>Sites and apps on the web are not supposed to be isolated, the web is <a href="https://paul.kinlan.me/slice-the-web/">linkable, indexable, ephemeral</a>, but we are getting more siloed with each site we build. We are <a href="https://paul.kinlan.me/unintended-silos/">creating unintended silos</a> because the platform doesn't easily allow users to get <em>their</em> data in and out off sites easily. I'm not talking about RDF or anything like that, basic operations such as copy and paste, drag and drop, share to site and share from site are broken on the web of today, and that's before we get to IPC between frames, workers and windows.</p>

This content originally appeared on Modern Web Development with Chrome and was authored by Paul Kinlan