Live data from Hacker News

Apple's intentional crippling of Mobile Safari

pwa.gripe

311–320 of 343 posts

Re: Apple's intentional crippling of Mobile Safari

#311

Earlier quoted context omitted.

Let Google dominate the web. If that’s a problem we can sort that out. But two wrongs don’t make a right.

Do you remember Internet Explorer before Edge? Jeez I never want to go back to that. And that’s what we’d end up with in a browser monoculture.

Fix their dominant position through legislation, not with more monopolies and anticompetitive behavior.

Re: Apple's intentional crippling of Mobile Safari

#312
post #25

Worth noting that Apple doesn't just cripple iOS Safari, it cripples all iOS browsers because it also forces them to use WebKit, the crippled browser engine underneath Safari. It would be fine if they just made Safari bad, that's their choice. But they don't stop there: they make the entire web bad on iOS purposely to promote the native apps they can tax.

This is clearly for reasons of security. I don't think Apple is terribly interested in market share for Safari. What they are interested is preserving their competitive advantage in privacy.

If it's about security and privacy, why push more people away from the Web to native apps that they know is less secure [1][2]?

> WebKit’s sandbox profile on iOS is orders of magnitude more stringent than the sandbox for native iOS apps.

[1] https://assets.publishing.service.gov.uk/media/62277271d3bf7... [2] https://open-web-advocacy.org/apple-dma-review

Re: Apple's intentional crippling of Mobile Safari

#313

I built https://pwascore.com/ several months ago. Where pwa.gripe cherry-picks and has an axe to grind, pwascore.com is intended to be a more thorough and dispassionate evaluation. I will add desktop browsers soon. Click "Expand All" for a complete and detailed list. Click "How Scores Work" to understand the scoring heuristics.

How did you determine the weighting for your scores?

Re: Apple's intentional crippling of Mobile Safari

#314
post #291

Earlier quoted context omitted.

And regulators are obviously unwilling/unable to hit them with fines that really make a difference beyond "cost of doing business" small change.

Now it's straight up protectionism from USA. You touch our tech margins, we won't do business with you. So yeah the regulators are unable, even if they wanted to something. Doctorow is right when he keeps saying that countries should make it legal to jailbreak devices. The problem is that first country that tries that will get hammer from the almighty POTUS.

The Chinese kicked out American companies when they were sure they could replace them with their own.

Keeping money in your own country and not funding the B2s that will bomb you one day.

Re: Apple's intentional crippling of Mobile Safari

#315

I built https://pwascore.com/ several months ago. Where pwa.gripe cherry-picks and has an axe to grind, pwascore.com is intended to be a more thorough and dispassionate evaluation. I will add desktop browsers soon. Click "Expand All" for a complete and detailed list. Click "How Scores Work" to understand the scoring heuristics.

How did you determine the weighting for your scores?

The most significant effect is that experimental and non-standard PWA capabilities aren't reflected in the primary score. You can see raw/unweighted scores by hovering over the primary score. Chrome wins handily if you count experimental/non-standard features.

For standards-based features I used a 4-tier model, described about halfway through the README (which I should also add to About):

    ┌────────┬──────────────┬───────────────────────────────────────────────┐
    │ Weight │ Tier         │ Rationale                                     │
    ├────────┼──────────────┼───────────────────────────────────────────────┤
    │ 3.0    │ Core PWA     │ Prerequisites for production PWAs (6 features │
    │        │              │ features: Web App Manifest, Service Workers,  │
    │        │              │ Caching, HTTPS, etc.)                         │
    ├────────┼──────────────┼───────────────────────────────────────────────┤
    │ 2.0    │ Important    │ Enhance PWA functionality (18 features: Push  │
    │        │              │ API, Add to Home Screen, Offline Support,     │
    │        │              │ Display Modes, etc.)                          │
    ├────────┼──────────────┼───────────────────────────────────────────────┤
    │ 1.0    │ Standard     │ Default weight (94 features)                  │
    ├────────┼──────────────┼───────────────────────────────────────────────┤
    │ 0.5    │ Experimental │ Nice-to-have capabilities (43 features:       │
    │        │              │ Sensor APIs, Bluetooth, NFC, AR/VR, etc.)     │
    └────────┴──────────────┴───────────────────────────────────────────────┘
This weighting turns out to be reasonably conservative. For example, if you hover over the score for Firefox (the largest benefactor), you'll see that it bumps Firefox's score by 5.

I'm very open to feedback. This is a sincere attempt to quantify vendors' PWA support.

Re: Apple's intentional crippling of Mobile Safari

#316

I built https://pwascore.com/ several months ago. Where pwa.gripe cherry-picks and has an axe to grind, pwascore.com is intended to be a more thorough and dispassionate evaluation. I will add desktop browsers soon. Click "Expand All" for a complete and detailed list. Click "How Scores Work" to understand the scoring heuristics.

Well the notifications on your web site doesn't provide the full idea of how limited it is in Safari. We have to ask users to install the shortcut before allowing notifications with Safari. Guess how many users actually go through with installing the shortcut? Nearly none. If we had to ask users to go into their settings and switch the "enable notifications" flag we wouldn't call that supporting anything. The whole p…

[dead]

Re: Apple's intentional crippling of Mobile Safari

#317
post #218

Earlier quoted context omitted.

> Let Google dominate the web No thanks

Fix their dominant position through legislation, not with more monopolies and anticompetitive behavior.

I can do neither, actually. I can merely observe reality as it is and look at which forces affect the direction of the world. And right now, I observe a reality where one of the most significant forces which counteract a completely Chromium dominated web is Apple's user-hostile insistence on preventing browser engine competition on iOS.

I have very little faith in a legislative solution here since I believe politicians care about browsers, not browser engines. They see Chrome, Brave, Vivaldi, Edge and Opera and see a diverse marketplace with sufficient browser competition. They don't seem to care about the technical monoculture behind it all.

Re: Apple's intentional crippling of Mobile Safari

#318

Earlier quoted context omitted.

You have to explicitly allow all of those features to work in a webpage, they aren't on by default, so I'm not sure what you're worrying about.

> so I'm not sure what you're worrying about. Complexity primarily.

Complexity for who? The user having to click "Yes I want to enable Web Bluetooth for this website"? Or for the developers? Because if it's for the developers, it's literally their job to make complex things simple for users.

Re: Apple's intentional crippling of Mobile Safari

#319

Earlier quoted context omitted.

>Google alone cannot and should dictate a standard, even though apparently we are fine with them attempting to do just that. They did not "dictate a standard". They saw a good use case for an API and made one for it (Web Bluetooth is what I'm really focused on). If the other W3C members want changes made, then they can make suggestions, and Google or someone else can implement the changes. They can even implement the…

You continue to dwell on Bluetooth while ignoring that there are reasons to not just blindly follow Google which is what pages like this are advocating for. I honestly don't care about Bluetooth and I don't have any stakes on whether or not it is supported, and I also don't know enough about it to actually talk about security on it. I will leave that to people that actually know what they are talking about instead. I…

>blindly follow Google

You obviously did not read my comment or understand it, so this pointless internet interaction is over.

Re: Apple's intentional crippling of Mobile Safari

#320

Earlier quoted context omitted.

Do you remember Internet Explorer before Edge? Jeez I never want to go back to that. And that’s what we’d end up with in a browser monoculture.

Fix their dominant position through legislation, not with more monopolies and anticompetitive behavior.

Are you talking about Google or Apple? Because Apple is being sued by the DOJ for monopolistic and anticompetitive behavior. There are numerous examples of it spelled out in the lawsuit:

https://www.justice.gov/archives/opa/media/1344546/dl?inline

Post reply on HN