Fair question. Certainly Microsoft wants Duo to succeed. But PWABuilder been pushing for PWAs in App Stores for years -- we also support MacOS, Samsung Galaxy Store, Microsoft Store, and others. (We're talking with Apple now to enable PWAs in iOS app store as well.)
This collaboration with Google took place because Google revamped their "PWAs in the Store" story. It used to be a very basic story: a native app wrapping a web view that loads your PWA. Those worked, but didn't support some modern APIs (e.g. service worker, IIRC), didn't share cookies and login information with the browser, and other problems.
Google revamped the story here to a more first-class approach for PWAs in their Store. It's called "Trusted Web Activities."
And earlier this year, Google created Bubblewrap, a command line tool to generate a proper Trusted Web Activity for publishing in their Store. So we wanted to take advantage of that new and better approach. That's really our reason for collaboration here.
This collaboration with Google took place because Google revamped their "PWAs in the Store" story. It used to be a very basic story: a native app wrapping a web view that loads your PWA. Those worked, but didn't support some modern APIs (e.g. service worker, IIRC), didn't share cookies and login information with the browser, and other problems.
Google revamped the story here to a more first-class approach for PWAs in their Store. It's called "Trusted Web Activities."
And earlier this year, Google created Bubblewrap, a command line tool to generate a proper Trusted Web Activity for publishing in their Store. So we wanted to take advantage of that new and better approach. That's really our reason for collaboration here.