We can keep this conversation going forever, no worries, I enjoy these types of discussions.
Funny you should mention banks, the last project I was a part of before founding PragmaFlow was https://play.google.com/store/apps/details?id=ca.bnc.android
Besides biometric login, everything could be done via the web/pwa.
PWA is becoming the new norm for apps that do not need an
engine. So things that are not video games, conferencing apps, or heavy multi-threaded apps are all fine in PWA, with the exception of needing biometrics, phone contacts, iaps (arguable better in PWA because you can use anything, not 30% to Apple to make in-app purchases), and some other items. Someone else on the forum asked about App Badges for PWA. The ability to do this is only 2 years old, most of the PWA technologies that really make them work is just before the pandemic started. Offline support for PWAs is maybe 7 years depending on how you look at it, probably closer to 5.
For the cash.app example, and your website vs your app is the wrong angle to look at. A website is used to inform, a web app is something people can use. Is there anything in cash.app that cannot be built using the Adalo previewer? If the answer is no, then it does not need to be a native app. If yes, well, that might be an Adalo limitation. PWAs support deep linking.
Final thought before passing the talking stick back to someone else, for those who remember, Netscape Navigator was released in December 1994, the internet and web browsers are about 30 years old. In those 30 years, computing and the internet has revolutionized itself time and time again getting bigger and faster.
PWAs are becoming the new norm, but all that might change in 2 years.