For example, many predict PWA development will be cheaper for them in the short-term. They are first optimizing product development for short-term cost. That focus impacts the released product more than PWA’s strengths and weaknesses. 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. Some expect native stacks will let them more deeply tune and polish the user experience than PWA. Or access richer or more performant device capabilities that PWAs cannot. And, this focus on experience over cost impacts the users’ experiences more than the capabilities of native.
In short, many PWAs feel poorer because of product development goals and constraints that precede PWA. These products were always going to give a poorer experience, regardless of the choice of PWA or native.