3 ms·
> A well written PWA will use a lot more battery, network, CPU, and memory than a well written native app. That's not solvable. What complete nonsense. It's ha
by blowski 5y ago
> A well written PWA will use a lot more battery, network, CPU, and memory than a well written native app. That's not solvable.
What complete nonsense. It's hardly baked into the rules of the universe. Of course Apple could figure this out at a technical level, it just doesn't work for their profit margins. Besides, it should be my choice and not Apple's whether I want to install an app that uses more CPU.
> They are good for developers but bad for users.
There are entirely valid use cases where the expense and hassle of making native apps prevents any app existing at all. Small businesses building apps for their staff, individuals building apps for themselves or families, small groups of friends.
- criddell 5y ago> Apple could figure this out at a technical level Probably not. Running an app in the browser is essentially running on a virtual machine. That's not going to be as efficient as a native app.
- blowski 5y agoIt depends on what the app is doing. If it's something I load once a day to read HTML content that's already been downloaded, how's that going to be less efficient?