3 ms·
I support Apple because I think they are sticking up for their users. If they had great support for PWAs a lot of companies and developers would go that route a
by criddell 5y ago
I support Apple because I think they are sticking up for their users. If they had great support for PWAs a lot of companies and developers would go that route and there would be no native app option.
You have a choice. If you want to run PWAs, get an Android phone.
- gherkinnn 5y agoI am an Apple user and they're not sticking up for me. They're sticking me. > If they had great support for PWAs a lot of companies and developers would go that route and there would be no native app option. No. Apple doesn't want to let go of the app store model and the money it gives em. Every other problem one could conceive of is solvable.
- criddell 5y ago> Every other problem one could conceive of is solvable. I think the biggest problem with PWAs is the resource usage. A well written PWA will use a lot more battery, network, CPU, and memory than a well written native app. That's not solvable. PWAs are a lowest common denominator solution. They are good for developers but bad for users.
- 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?
- gherkinnn 5y agoTrue. Battery use for long-running web apps on phones is hard to solve. I have yet to gain experience in this.
- kgin 5y agoIf they supported PWAs, 90% of apps wouldn’t need a native option. Most apps are text, images, maybe some kind of media if we’re getting crazy, and buttons. Mobile web apps suck because mobile browsers make them suck. There’s no reason I can edit complex spreadsheets in Google Sheets in my desktop web browser, but every time I go to Reddit or Quora on my mobile browser, they claim that their native apps are required to truly display text and images correctly.
- 1_player 5y agoThere's fanboyism and there's "you are wrong for wanting something Apple didn't care to implement, they know better than you". Your argument doesn't any sense, it's just partisanship and appeal to authority. You can't explain that PWAs have no place in iOS using the excuse that Apple is doing it for our sake. Sorry, that's just dumb.
- criddell 5y agoIn another comment I explain that a well written PWA will use more battery, CPU, memory, and network bandwidth than a well written native app. Web apps are lowest common denominator solutions and that’s not where Apple wants to be. They know their users are better off with native apps. If you disagree, then stick with Android which has pretty good support.