I mean, sure, I have some ideas that would work as a PWA, but this feature is hardly global to every phone, and depending on your app, totally undoable as a PWA. Some phones don't even support the drawer, and it's just as strange to ask someone to download a special browser to use one. Lastly, there is bound to be something that won't work even on Chrome.
It seems to me that all apps are either a pure app or really silly basic and would be equally useful as a responsive website. For example, I once used a HN app, but it really wasn't any different than just using the website because it was completely worthless without the internet. I'd just say make things a responsive website until you run into features that absolutely don't work on a browser, then go native. I could be wrong, but I don't think there is much necessary overlap.
I'd just say make things a responsive website until you run into features that absolutely don't work on a browser
My impression is that those extra requirements are more often than not related to data collection and user tracking via broad spectrum app permission requests. It is simply more convenient, robust and profitable to sit on a device and phone home than relying on the user to frequent a site.
Imo most apps would have been called (mal|spy|ad)ware a couple of years ago.
It seems to me that all apps are either a pure app or really silly basic and would be equally useful as a responsive website. For example, I once used a HN app, but it really wasn't any different than just using the website because it was completely worthless without the internet. I'd just say make things a responsive website until you run into features that absolutely don't work on a browser, then go native. I could be wrong, but I don't think there is much necessary overlap.