4 ms·

While this is nice, to me the whole promise of PWA is that developers can escape confusing App Store rules, long approval process, and the absurd 30% commission

While this is nice, to me the whole promise of PWA is that developers can escape confusing App Store rules, long approval process, and the absurd 30% commissions. So no, thank you. I don’t want back into the App Store.

hot_gril 4y ago
The other purpose is discoverability. I doubt many people know that to install a PWA, you press the "share" button (lol) and then "add to home screen." But yes I have a few personal projects I've deliberately not put on any app stores.
- siva7 4y ago
  Even very few tech people know this, let alone the general consumer. There is also not much incentive for apple or google to market this functionality further.
brundolf 4y ago
Why not both? Making it available through both channels will help discoverability
- justeleblanc 4y ago
  Why not both? To avoid confusing App Store rules, long approval process, and the absurd 30% commissions
  - Spivak 4y ago
    If PWAs ever become a legitimate threat to Apple's revenue expect to see all that become required for your site to become installable.
Nursie 4y ago
> the whole promise of PWA is that developers can escape confusing App Store rules, long approval process As a consumer, and perhaps more importantly as someone who is frequently unofficial tech support for other consumers, this is why I don't want PWA support or PWAs in generally getting any foothold on devices. The number of notifications, icons, noises, ads, disturbances and general bullshit that an average user already has to put up with on a device is absurd. Can they be careful about what they install? In theory. Can they configure and down-regulate all these notifications? In theory. But they don't, and they won't. Having something that appears to be able to bypass app store review is a developer wet dream but a user nightmare. Because they'll go to a website and press the buttons it tells them to, and now instead of it just being spammy bullshit that did pass the app store filter, it might be absolutely anything. You might have honest intentions, but thousands won't, and users demonstrably can't handle it.

hot_gril 4y ago

The other purpose is discoverability. I doubt many people know that to install a PWA, you press the "share" button (lol) and then "add to home screen." But yes I have a few personal projects I've deliberately not put on any app stores.

siva7 4y ago
Even very few tech people know this, let alone the general consumer. There is also not much incentive for apple or google to market this functionality further.

brundolf 4y ago

Why not both? Making it available through both channels will help discoverability

justeleblanc 4y ago
Why not both? To avoid confusing App Store rules, long approval process, and the absurd 30% commissions
- Spivak 4y ago
  If PWAs ever become a legitimate threat to Apple's revenue expect to see all that become required for your site to become installable.

Nursie 4y ago

> the whole promise of PWA is that developers can escape confusing App Store rules, long approval process As a consumer, and perhaps more importantly as someone who is frequently unofficial tech support for other consumers, this is why I don't want PWA support or PWAs in generally getting any foothold on devices. The number of notifications, icons, noises, ads, disturbances and general bullshit that an average user already has to put up with on a device is absurd. Can they be careful about what they install? In theory. Can they configure and down-regulate all these notifications? In theory. But they don't, and they won't. Having something that appears to be able to bypass app store review is a developer wet dream but a user nightmare. Because they'll go to a website and press the buttons it tells them to, and now instead of it just being spammy bullshit that did pass the app store filter, it might be absolutely anything. You might have honest intentions, but thousands won't, and users demonstrably can't handle it.