Register for this year’s #ChromeDevSummit happening on Nov. 11-12 in San Francisco to learn about the latest features and tools coming to the Web. Request an invite on the Chrome Dev Summit 2019 website

Desktop Progressive Web Apps on Windows & Linux

Once installed, they’re launched from the Start menu, and run like all other
installed apps, without an address bar or tabs.
Service workers ensure that
they’re fast, and reliably, the app window
experience makes them feel like any other installed app.

Getting started isn't any different than what you're already doing today.
All of the work you've done for your existing Progressive Web App still applies!
If your app meets the standard PWA criteria,
Chrome will fire the
beforeinstallprompt
event. Save the event; then,
add some UI
(like an install app button) to tell the user your app can be installed. Then,
when the user clicks the button, call
prompt() on the
saved event; Chrome will then show the prompt to the user. If they click add,
Chrome will add your PWA to their start menu and desktop.

Chrome 70 adds support for a third type of credential:
Public Key Credential,
which allows web applications to create and use, strong, cryptographically
attested, and application-scoped credentials to strongly authenticate users.

I'm pretty excited about it because it allows sites to use my fingerprint
for 2-factor authentication. But, it also adds support for additional types
of security keys and better security on the web.

Named workers

Workers are an easy
way to move JavaScript off the main thread and into the background. This is
critical to keeping your site interactive, because it means that the main
thread won’t lock up when it’s running an expensive or complex JavaScript
computation.

This lets you distinguish dedicated workers by name when you have multiple
workers with the same URL. You can also print the name in the DevTools
console, making it much easier to know which worker you’re debugging!

Naming workers is already available in Firefox, Edge, and Safari. See the
discussion on GitHub for more
details.

And more!

These are just a few of the changes in Chrome 70 for developers, of course,
there’s plenty more.