We know that Microsoft will be the first platform maker to formally support Progressive Web Apps (PWAs) in its mobile apps store. But the software giant isn’t alone in adopting this important new technology. Both Google and Apple will formally support PWAs in their own platforms too.
As you may know, Google already supports PWAs in a basic way in Android: If you navigate to a PWA—like Twitter Lite—using the Chrome web browser, a pop-up will appear, letting you add that app to your phone. This is a nicety, for sure, but discoverability is an issue. Google doesn’t (yet) offer a way to find PWAs in its app store, Google Play.
(You can also add PWAs to your Android phone using Firefox now.)
Sign up for our new free newsletter to get three time-saving tips each Friday — and get free copies of Paul Thurrott's Windows 11 and Windows 10 Field Guides (normally $9.99) as a special welcome gift!
"*" indicates required fields
At the Chrome Dev Summit in October 2017, Google’s Owen Campbell-Moore announced how the search giant would allow PWAs to work with its desktop platform, Chrome OS. Put simply, PWAs will run on Chrome OS just as they do on Windows 10 (starting with version 1803) and Android, as native apps.
That’s a big deal because PWA was purely mobile-focused before Microsoft’s involvement. But Microsoft is also innovating on store integration: Users will be able to seamlessly find and install PWAs directly from the app store that is built right into the OS. I was told that Google would be adding similar store support at some point, and presumably to both Android and Chrome OS. (In fact, the Chrome OS app store is being phased out for the Google Play Store, so these things will become one and the same over time as well.) I am not aware of a schedule for that change.
But according to developer Kenneth Christiansen, Google is continuing to add native capabilities to PWA, and these changes will help this platform bridge the gap between its web roots and the underlying OSes on which these apps run.
“Lots of companies (think Slack or VSCode) use Electron today in order to wrap their web apps into a native container, as well as expose additional native APIs,” he writes. “There is a big problem with that approach though, because people constantly find security bugs in browsers and most of these become public, shortly after the browser vendors have fixed them, but the Electron runtime people distribute is often old and updated infrequently — resulting in a big security risk for the users. Desktop PWA support would fix this, but only if developers have access to the APIs they need to build their experiences.”
One of the next native APIs that Google will add to PWA, according to Mr. Campbell-Moore, is support for contacts. Over time, I expect more and more native features to come to PWA, eliminating all but the most specialized of barriers. More to the point, I expect this to happen very quickly.
So we know that PWA is improving rapidly, is coming to all of Google’s platforms and to Windows 10, and will support both desktop and mobile use cases, and app stores. But the big elephant in the room, of course, is Apple.
Yes, Apple is formally supporting PWAs too, and across both iOS and macOS, via Safari and its underlying technologies. I expect an announcement to this effect at WWDC this summer. But Mr. Christiansen points out that the firm has already announced it is actively working to add three of the four core features of PWAs—Service Workers, Caching, and Manifest support—to its platforms. And the fourth, Push, is under consideration. It’s happening.
Mr. Christiansen’s post has some interesting examples of PWAs, and how you can use them on Chrome OS today too. It’s worth reading, if only for further confirmation that 2018 is, indeed, the year of the Progressive Web App.
skane2600
<blockquote><a href="#247122"><em>In reply to James_Wilson:</em></a></blockquote><p>Microsoft made Java a useful tool on Windows. With Microsoft's modifications it became a great way to perform COM programming. </p><p><br></p><p>"Pure" Java was never a good tool for creating Windows programs. Windows developers weren't very interested in making their programs run on Unix and Unix developers were not very interested in developing Java programs on Windows. </p><p><br></p><p>The true value of Java at the time it was introduced was to allow a windowless program to be written that could run on the diverse (at that time) set of Unix implementations without recompiling (while windowed programs were supported by Java, they weren't the primary focus of Unix developers and Sun's implementation was weak).</p>
Bats
<p>It doesn't matter who "formally" supports it. Google has already been sorta doing this for the past few years as I've noticed this a couple of years ago via website using the Chrome browser.</p><p>This may be a "Shazaam" moment for those in the Microsoft Universe, but not really for those outside of it. </p><p>I just have one question, though. If Microsoft is going to start promoting the use of these web apps, then why in the world are they going to utilize their store for it? All one has to do is click the bookmarks/favorites button on your web browser and BANG…installed (sort of). LOL…it's the web. As a Chrome user, if I were ever to get a new computer or reset my current ones, all I would have to do is re-install Chrome and all my PWAs will be accessible in oneshot, with not time at all. </p><p>Also, PWAs gives more reason for computer users to move away from Windows than ever. The prospect of a person depending on their favorite PWA to get work done on a Linux, Android, Chrome OS, Apple without the fear of malware infecting their system, is just going to hinder Windows usage once people figures this out. </p><p>So, in other words, PWAs will hurt Microsoft.</p>