It sucks that that's the best option, but if we've made it to that point I personally would rather just use the website without extra steps. Not a fan of PWAs.

Most information based apps don't need to be natively integrated. Take the Voyager client for example. It behaves almost exactly like the native version of the app.

Most users wouldn't even notice a difference, if well implemented.

App developers need to abandon these proprietary platforms and switch to open ones like the web. That's the only way to end this fuckery.

Voyager is a fantastic example. I forget that it is a PWA all the time.

Question 3. Why does Google’s privacy policy allow Google to share “personal information” with any “businesses or persons”?

The Google Paradox

Voyager is a web site??????

How will they capture your data silly?

It's nice to hear from Mark Murphy on this. He's a legend in the Android space.

I don't have any hope that Google analytics is dying any time soon

Many APIs Android apps can use are unavailable to PWAs. Also PWAs typically require server infrastructure to at least load once. The author of my favourite open source unit conversion calculator shouldn't need to maintain a web server so I can use their app.

But yeah, for use cases that require a server anyways and don't need elaborate mobile APIs, PWAs are probably the way to go.

If you think about it, a PWA is an electron app without the electron wrapper.

App developers need to abandon these proprietary platforms and switch to open ones like the web. That’s the only way to end this fuckery.

The "value add" for mobile apps is mainly that they enable more analytics collection without the users having the ability to control it through ad blockers. There are vanishingly few cases where the UX is superior compared to a well-implemented web app.

Basically, yeah.