You still needed UI changes.
Are you really saying that it would he more performant that you have to make a round trip just to perform validation? How slow would the hardware have to be for a network round trip to be faster?
Validations always need to be done on both sides, unless one does not value security.
All of this is possible with vanilaJS, using builtin browser features, no need to kill the poor CPU with an additional bloated framework.
I used to be big in native apps, until having seen too many examples of what used to be done in VB/Acess back in the day.
So unless it is a game using OpenGL ES 3.0, Vulkan, Metal, something that requires AR/VR, real time audio, GPGPU for machine learning, or direct access to hardware sensors, it might be quite doable as PWA.
Even with CRUD apps you need to display dynamic content based on user interaction.
I used to be big in native apps, until having seen too many examples of what used to be done in VB/Acess back in the day.
So you haven’t seen the poor performance of ASP.Net Web Forms with the huge hidden field to maintain state and redrawing the screen for every interaction and a network round trip?
Apple's decision doesn't apply to PWAs as clarified on a later update.
Plus updating the browser cache every couple of days isn't a big deal, native apps get store updates almost every day.