My response is by no means “more qualified”, and mostly confined in PC environment, as benefits of using PWA over native applications on mobile is much less controversial (I think).
IMO it comes down to your assessment and your preference.
I use a simple “diagram” to illustrate the key difference between native application and PWA.
PWA -(runs on )-> Web Browsers -(runs on) → OS
Native Application -(runs on)-> OS
Ride on the diagram above, here are my reasons to choose one over another, depending on your assessment.
Reasons for using PWA (click to expand)
If you use PWA, while browser itself is a prominent attack vector, it is constantly being studied and improved, it is also being confined by the OS.
Users are much less likely (if practical at all) being tricked to install malicious update of such site / PWA, unless either the dev went woke, you got DNS-jacked, or the site got hacked.
You will also most likely not being asked to install other dependencies (such as .net framework and what not) to run sites/ PWA, which is a big plus.
On the other hand, browsers with adblocking/ JS blocking features, combined with multiple user profiles, can supercharge the privacy and security protection.
Chromium based browsers can “package” many websites as “web applications” and “install” them to your PC, which is very convenient.
Reasons for using Native Apps (click to expand)
You are most likely avoiding the largest attack vector of using a computer (i.e. web browser).
There is no worries your browser will know / transmit / record what you do within a native application as web browser is not involved.
Native applications has unrivaled flexibility and functionality when compared to PWA, it is also more likely that native applications being open source and reproducible than a PWA (so you can check the code and build it yourself, if you wish).
All in all, I prefer PWA over native applications.