5 ms·
The number one reason to choose PWA over native is performance.
by SimeVidas 7y ago
The number one reason to choose PWA over native is performance.
- sk0g 7y agoIf performance means performantly hogging resources performing the most basic of task, then sure.
- jamil7 7y agoCould you elaborate on that? Performance of what exactly?
- bryanrasmussen 7y agoIt must be performance of your developers being able to develop for one codebase.
- SimeVidas 7y agoLoading times and responsiveness. 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.
- jamil7 7y agoWow thats huge. I haven't used twitter in years, I wonder if it was always so bloated.
- deleted 6y ago[deleted]
- pssdbt 7y agoThat's the reason to choose PWA over other web technologies, not native.
- http-teapot 7y agoWhat other technologies?
- twicetwice 7y agoI'm assuming they're talking about a standard SPA (or even a conventional full-page-reload web app), or React Native or Electron on the desktop or similar. In the former case, a PWA can use service workers and caching and so on to get better network performance. In the latter case, they can leverage a preexisting Chromium/other browser instance to get most of the advantages of "write once, run everywhere" without bundling a whole browser instance with your app. I can't wait for full PWA support in Firefox, especially on desktop!
- colordrops 7y agoNo way are they more performant than native apps. Their big advantages are write once run anywhere, no vendor lock in, easier install, and more control, privacy and sandboxing since they are web apps.