When confronting native applications with Progressive Web Apps, I see one disadvantage on PWAs that is impossible to overcome without a dedicated server to serve as proxy.
Native applications are free to perform web requests to any domain, while PWAs are limited by Cross Origin Resource Sharing checks performed by the browser.
Although this has a security reasoning behind it, it would be good to try to produce a standard that would allow Web Applications to consume resources from other domains in the same way a native application would.
One idea would be to implement something similar to the permissions API used by Chrome Extensions, where PWAs would request permissions to access resources.
A RSS reader without a server side needs to access RSS feeds from resources that are only discovered at runtime. This resources may have incorrect CORS settings as most RSS readers are not impacted by CORS (they are either native, or consult the feeds from server side).
In this case, RSS Reader PWA suffers a strong disadvantage in comparison to native apps, in their core application
When confronting native applications with Progressive Web Apps, I see one disadvantage on PWAs that is impossible to overcome without a dedicated server to serve as proxy.
Native applications are free to perform web requests to any domain, while PWAs are limited by Cross Origin Resource Sharing checks performed by the browser.
Although this has a security reasoning behind it, it would be good to try to produce a standard that would allow Web Applications to consume resources from other domains in the same way a native application would.
One idea would be to implement something similar to the permissions API used by Chrome Extensions, where PWAs would request permissions to access resources.
Include some links here:
Example Use Cases: