> The DMA was passed many years ago (January 2022), before the cited investments in PWAs. So if Apple was acting to proactively stave off regulation, you have a big hole in your theory of causality.
I'm not sure I do? The DMA was passed in January 2022. In that entire span of time when Apple was actively arguing in court that PWAs were an alternative to the app store, at no point did they ever consider building out a proper security model for PWAs that didn't rely on the assumption that Safari would be the only supported browser.
You're saying that Apple learned about the DMA before they started looking at PWAs seriously, then we got to February 2024 and suddenly Apple was caught flat-footed about browser requirements? That doesn't make sense: either they knew about the DMA and their current lack of PWA security models are an active decision that purposefully complicated compliance with the DMA, or Apple somehow wasn't thinking about the DMA in which case it's kind of silly to say that it disproves anything about their apparent web strategies.
This is a situation where the excuse makes Apple seem more suspicious, not less. Apple knows in 2022 that the DMA is coming. In February 2024 out of the blue they announce that they're shutting down PWA support. If that's not strategic, it's at least wildly incompetent. And I don't think that Apple is wildly incompetent -- I think that announcement was strategic.
> So if Apple was acting to proactively stave off regulation
I'll also note that this is not a theory, Apple is actively arguing in the US that PWAs mean that it shouldn't be regulated. I don't really understand the contention here, the way I see it Apple is saying that PWAs are a proactive strategy to stave off regulation.
We can disagree about their motivations beyond that regulation, about whether they would consider dropping support in the absence of regulation, but it is just a fact that Apple started investing more heavily in Safari around the same time that regulation arguments started popping up in both Europe and the US, and it is just a fact that Apple has proactively put forward PWAs as an argument in court cases as to why it shouldn't be regulated.
Is it really that weird to connect those dots?
----
> Apple’s interest in the web cannot be gauged by how much they support technology funded and evangelized by a bunch of current and ex-Googlers
Apple's support and advocacy for PWAs is pathetic even ignoring Chrome's support. It's not like Chrome has good PWA support, the entire notifications API is obviously designed by an advertising company with zero real input from any stakeholders other than advertisers.
Ideally, investment from Apple into the PWA ecosystem would mean not leaving the entire PWA specification to be written entirely by an advertising company, it would mean proactively getting involved in the process. It would mean asking questions like, "aside from Google, who on earth does it benefit that notifications have to be triggered by a remote server and can't be scheduled locally?"
The state of PWAs is as much a story about the apathy of every other company besides Google as it is a story about Apple holding back on basic support for extremely needed features like reliable offline storage. I'm not giving Apple credit for sitting back and twiddling its thumbs while Google ruins the spec, and then turning around and saying, "you can't expect us to implement these features, the proposed specs are terrible."
Yeah, of course they're terrible, where were you while Google was ruining them? I'm surrounded by people arguing that Safari is some kind of final bastion against Chrome hegemony, but in practice Apple does nothing with that bastion. They let Google make all the decisions, and then use that as an excuse to offer middling browser support. I'm not giving them credit for that. I'm not talking about exposing web usb support, I'm talking about things like: is it possible build an alarm clock as a PWA?
I'm not asking Apple to bow to Google's every demand, I'm asking them to act like they're a stakeholder in the web and to give even one single damn about whether it's possible to build privacy-respecting offline webapps. Apple's apathy towards influencing or pushing the PWA web standards process in a productive direction is just as much a problem as their apathy towards supporting obviously beneficial capabilities like icon badges. Apple defers power to Google and then uses that as an excuse for further inaction.
I'm not sure I do? The DMA was passed in January 2022. In that entire span of time when Apple was actively arguing in court that PWAs were an alternative to the app store, at no point did they ever consider building out a proper security model for PWAs that didn't rely on the assumption that Safari would be the only supported browser.
You're saying that Apple learned about the DMA before they started looking at PWAs seriously, then we got to February 2024 and suddenly Apple was caught flat-footed about browser requirements? That doesn't make sense: either they knew about the DMA and their current lack of PWA security models are an active decision that purposefully complicated compliance with the DMA, or Apple somehow wasn't thinking about the DMA in which case it's kind of silly to say that it disproves anything about their apparent web strategies.
This is a situation where the excuse makes Apple seem more suspicious, not less. Apple knows in 2022 that the DMA is coming. In February 2024 out of the blue they announce that they're shutting down PWA support. If that's not strategic, it's at least wildly incompetent. And I don't think that Apple is wildly incompetent -- I think that announcement was strategic.
> So if Apple was acting to proactively stave off regulation
I'll also note that this is not a theory, Apple is actively arguing in the US that PWAs mean that it shouldn't be regulated. I don't really understand the contention here, the way I see it Apple is saying that PWAs are a proactive strategy to stave off regulation.
We can disagree about their motivations beyond that regulation, about whether they would consider dropping support in the absence of regulation, but it is just a fact that Apple started investing more heavily in Safari around the same time that regulation arguments started popping up in both Europe and the US, and it is just a fact that Apple has proactively put forward PWAs as an argument in court cases as to why it shouldn't be regulated.
Is it really that weird to connect those dots?
----
> Apple’s interest in the web cannot be gauged by how much they support technology funded and evangelized by a bunch of current and ex-Googlers
Apple's support and advocacy for PWAs is pathetic even ignoring Chrome's support. It's not like Chrome has good PWA support, the entire notifications API is obviously designed by an advertising company with zero real input from any stakeholders other than advertisers.
Ideally, investment from Apple into the PWA ecosystem would mean not leaving the entire PWA specification to be written entirely by an advertising company, it would mean proactively getting involved in the process. It would mean asking questions like, "aside from Google, who on earth does it benefit that notifications have to be triggered by a remote server and can't be scheduled locally?"
The state of PWAs is as much a story about the apathy of every other company besides Google as it is a story about Apple holding back on basic support for extremely needed features like reliable offline storage. I'm not giving Apple credit for sitting back and twiddling its thumbs while Google ruins the spec, and then turning around and saying, "you can't expect us to implement these features, the proposed specs are terrible."
Yeah, of course they're terrible, where were you while Google was ruining them? I'm surrounded by people arguing that Safari is some kind of final bastion against Chrome hegemony, but in practice Apple does nothing with that bastion. They let Google make all the decisions, and then use that as an excuse to offer middling browser support. I'm not giving them credit for that. I'm not talking about exposing web usb support, I'm talking about things like: is it possible build an alarm clock as a PWA?
I'm not asking Apple to bow to Google's every demand, I'm asking them to act like they're a stakeholder in the web and to give even one single damn about whether it's possible to build privacy-respecting offline webapps. Apple's apathy towards influencing or pushing the PWA web standards process in a productive direction is just as much a problem as their apathy towards supporting obviously beneficial capabilities like icon badges. Apple defers power to Google and then uses that as an excuse for further inaction.