PWAs all share the same system webview. Three PWAs are essentially no different to having three tabs open in Safari/Chrome. The load they place on the phone is significantly less than most native apps.
I've noticed when having this debate that people seem to compare the worst possible web experience with the best possible native one. Yes, there are bloated and slow web sites, but don't try to tell me there aren't also native apps bloated to the point of absurdity, with multi-second load times even on a top of class device. And there are plenty of fast, small web sites too!
We can agree on UI, though. The web could do with a lot more native-level UI primitives (UITableView, please lord). As an added bonus this would help remove a lot of the bloat and performance issues as people try to replicate native behaviours in JS.
PWAs all share the same system webview. Three PWAs are essentially no different to having three tabs open in Safari/Chrome. The load they place on the phone is significantly less than most native apps.
I've noticed when having this debate that people seem to compare the worst possible web experience with the best possible native one. Yes, there are bloated and slow web sites, but don't try to tell me there aren't also native apps bloated to the point of absurdity, with multi-second load times even on a top of class device. And there are plenty of fast, small web sites too!
We can agree on UI, though. The web could do with a lot more native-level UI primitives (UITableView, please lord). As an added bonus this would help remove a lot of the bloat and performance issues as people try to replicate native behaviours in JS.