> Because it's well-known that PWAs has been stunted by Apple and Google.
It is not well-known. It is well-believed.
I don't believe Apple has intentionally crippled Safari just to prop up their native platform. Google are the ones who invented the PWA buzzword and spend all their devrel effort on pushing. It's hard to believe they would also try and hamper that.
I have occasionally needed to advise mobile users how to use a simple web app showing phone's location on a map. Sample size is at least tens of people, selection bias to somewhat young and active people. Based on this "research",for a median iPhone user a location-aware web app is simply broken. Without external help, they are unable to change the (default/dark pattern, I do not know?) setting of not letting browser access to location data. You are welcome to come up with reasons why Apple has made it so difficult. I have difficulties to think other than intentionally crippling web apps.
Not every website I visit needs to know my location.
Not every website with a map needs access to my location.
Only websites I specifically allow to access my location should have access.
On the iPhone and specifically safari I've never had an issue or a steep learning curve to showing someone how to long press the reader view (AA) in the url then select _allow location_ or whatever.
I wonder if you sample all had something in common. Did they not regularly use this web app? Was this an event specific web app? If so it would be nice if the web app detected mobile browser by user agent and displayed instructions for activating location. Might help reduce confusion.
There must be a higher bar (making it harder to blindly click 'yes') for user consent on the web because there's so much less intentionality behind what arbitary code your device will execute. Visiting any popular news website will run untrusted JS delivered through 10 different intermediaries in advertisements.
I think any complaint directed towards Apple's development on Safari can also be directed towards their actual native platform. Terrible/non-existent documentation, frequently breaking APIs, and a completely hostile app store and bug reporting/feedback process.
It is not well-known. It is well-believed.
I don't believe Apple has intentionally crippled Safari just to prop up their native platform. Google are the ones who invented the PWA buzzword and spend all their devrel effort on pushing. It's hard to believe they would also try and hamper that.