[locutous]

> For example, many predict PWA development will be cheaper for them in the short-term.

It's objectively true if your requirements include multi platform support (particularly web) and don't have hard native requirements (such as device Bluetooth access).

> Others choose PWA hoping for a way to rapidly release and iterate MVPs of experimental business ideas. Again, the rationale has a greater impact on the user experience than the tech.

This isn't always true.

Expedience, familiarity, or new and shiny are very strong gravity sources in making a decision.

The design skill of the team and org will have a bigger impact on the final product than the decision. Crappy native apps are as bad as crappy web apps. And there are tons of crappy native apps. Exceptional software is a relatively rare breed of software.

That said, I will grant that some organizations will have a rushing about management style that can pretty much only build short sighted crap and if given the choice they would probably opt for a PWA. Even as I repeat this logical seeming rational I have worked at such places and they haven't built PWAs, so it's not some universal. They still fell into one of the above gravity sources.