Well that just sent me down a rabbit hole.
My first foray into PWAs was this year but it was a short lived endeavor when I found out I had no hopes of feature parity across devices for core functionality and decided to switch to React Native instead. I didn’t know android did that with PWAs.
Thanks for the explanation.
which does this by generating an APK on google servers and installing it
I’m sorry but that not at all how PWAs work at all. PWAs are just websites. There is no APK. At its core it is a bookmark to a website without the browser UI.
Chrome definitely offers a lot more APIs than other browsers to allow a website to interface with a phone a lot better. Often outside of the standards the web has set. That can make browsers that follow the standards feel behind (Firefox) and really emphasizes browsers that purposely hinder their browser to incentivize native apps (IOS Safari).
You can set up websites to run as standalone apps by adding them to your Home Screen from the browser.
How native an experience you will get with that is dependent on the developer and the work they put in when it comes to caching, implementation of web workers, push notifications, meta data, etc.
Tailwind is my go-to these days