This is what really, really pissed me off about the iPhone. When it launched and they gave it a desktop-class web browser engine and told people they were going all-in in PWAs (though I don't think the term existed at the time). Then v2 came out and they went sike! native apps, must be developed on our PCs, must be distributed by us, you must pay us to be allowed to develop, we take a cut of your income, and we're going to cripple the PWA engine to make universal, open apps all but unusable.
Dicks.
Can PWAs perform just like native apps when it comes to smoothness and optimization?
Yes, if the underlying engine is designed to support it. There are standard web APIs for accelerated graphics, compute, offline storage, Bluetooth, push notification, environmental sensors, phone book access, camera, local storage access, and so on... A decent PWA is indistinguishable from a native app.
This is what really, really pissed me off about the iPhone. When it launched and they gave it a desktop-class web browser engine and told people they were going all-in in PWAs (though I don't think the term existed at the time). Then v2 came out and they went sike! native apps, must be developed on our PCs, must be distributed by us, you must pay us to be allowed to develop, we take a cut of your income, and we're going to cripple the PWA engine to make universal, open apps all but unusable.
Dicks.
Can PWAs perform just like native apps when it comes to smoothness and optimization?
Yes, if the underlying engine is designed to support it. There are standard web APIs for accelerated graphics, compute, offline storage, Bluetooth, push notification, environmental sensors, phone book access, camera, local storage access, and so on... A decent PWA is indistinguishable from a native app.