For example, Twitter’s native iOS app is about 115 MB, while their PWA is a tiny fraction of that, probably not more than a few MB. This unsurprisingly reflects on performance.
I don't see how it is a terrible idea that needs to be killed. Sounds like a technological regression if support were to be removed. It's not like you're not allowed to still build native apps so please make me understand this argument.
And yes, I am advocating for a technical regression. I think the web platform has pushed things unnecessarily too far because it cared more about competing with apps then embracing what the web is good for.
If you want proof this is true, look no further than technologies such as AMP that trade away the general usage of these advanced web technologies for something the end user actually wants: a good user experience.
You could also look at the numerous native apps that have mini apps and games that are developed using web technologies. If the web platform delivered features developers needed, these mini experiences could run in embedded web controllers. Instead they are custom webviews with hooks into the native platform to bridge the gap to what developers actually need.
> FREE to install
> HTTPS is required meaning you data is secure
> Takes up less storage on your phone. No need to pay extra money for higher storage
> No in app purchases or ads. Just a clean and simple app experience
> Has an offline mode. Apps can be used in areas where this is no internet connection
All of them are either misleading or completely wrong. The comparison randomly switches from websites to phone apps whenever convenient.
It would be a lot better to provide a more objective description of what PWAs even are.