>My iOS device has never once shown me "this website requires Chrome."
Why would any PWA say that, if Safari had proper support for PWA?
>Instead it's web developers, who are just annoyed that they have to actually respect the conventions of the platform they're building for.
Say the developer is from a village in India or Nigeria who has just a Raspberry Pi to develop apps -
•What if the developer didn't have thousands of dollars to invest in new equipments just to develop for iOS?
•What if the developer wasn't able pay $99 every year for the Apple developer license?
•What if the just didn't want to give 30% cut to Apple from the revenue each time?
For all the times Apple uses 'Equality' in its marketing, the Apple platform & ecosystem restrictions clearly seems to be aimed at the privileged, pushing the agenda that 'Privileged is good' and 'Everyone should aim at being privileged'.
Less empathetic would respond, 'Well that's not Apple's fault that they aren't privileged'; Well then, we have to go back into colonial imperialism & American capitalism to prove why they aren't privileged in the first place and why Apple holds a responsibility every time it uses 'Equality, Human etc.' in it's marketing; which would be digressing from the topic.
> Why would any PWA say that, if Safari had proper support for PWA?
For the same reason that far too many desktop websites say that today.
> Say the developer is from a village in India or Nigeria who has just a Raspberry Pi to develop apps
Apple is not catering to this developer demographic.
> For all the times Apple uses 'Equality' in its marketing, the Apple platform & ecosystem restrictions clearly seems to be aimed at the privileged
You're conflating developers with users. What fraction of iPhone users are writing apps? If you wanted to prioritize users, there's much tougher questions you could ask.
Ha. Using Foundation, Swift and SwiftUI I can write an app that doesn't require a trip to GitHub or Node.js in order to work properly. I can prototype my UI right there in Xcode, and if there's something I need that hasn't made it into SwiftUI yet I can bring in things from UIKit without very much effort. Best of all, I can build for macOS as well as iOS from the same codebase now. It's really hard to get more developer-friendly than that, unless you mean "web-developer-who-doesn't-want-to-learn-iOS-friendly".
Why would any PWA say that, if Safari had proper support for PWA?
>Instead it's web developers, who are just annoyed that they have to actually respect the conventions of the platform they're building for.
Say the developer is from a village in India or Nigeria who has just a Raspberry Pi to develop apps -
•What if the developer didn't have thousands of dollars to invest in new equipments just to develop for iOS?
•What if the developer wasn't able pay $99 every year for the Apple developer license?
•What if the just didn't want to give 30% cut to Apple from the revenue each time?
For all the times Apple uses 'Equality' in its marketing, the Apple platform & ecosystem restrictions clearly seems to be aimed at the privileged, pushing the agenda that 'Privileged is good' and 'Everyone should aim at being privileged'.
Less empathetic would respond, 'Well that's not Apple's fault that they aren't privileged'; Well then, we have to go back into colonial imperialism & American capitalism to prove why they aren't privileged in the first place and why Apple holds a responsibility every time it uses 'Equality, Human etc.' in it's marketing; which would be digressing from the topic.