3 ms·

Hmm -- are you suggesting that Apple is lying in their rationales here? That they should have instead kept supporting PWAs but only on WebKit, in violation of t

by zamfi 3y ago

Hmm -- are you suggesting that Apple is lying in their rationales here? That they should have instead kept supporting PWAs but only on WebKit, in violation of the DMA? Or that they should have argued the DMA doesn't require PWA support for alternative browser engines? Or that it's in fact straightforward to offer an API for browser engines to integrate with caching, background operations, notifications, etc., and Apple should have held off compliance with DMA until these were implemented? If so I'd love to learn more. I'm sort of inclined to believe that these currently sit deep in WebKit and it's a nontrivial exercise to pull them out and offer them as an API to other browser engines.

lxgr 3y ago
> that they should have argued the DMA doesn't require PWA support for alternative browser engines? That would have been the least controversial aspect of their first attempt at compliance, in my view. They could have also just allowed third-party browsers to offer a "PWA home screen" as an intermediate step until the APIs are ready. I can't think of a PWA API that's impossible to implement in a third-party browser other than appearing on the home screen and in the app switcher under its own icon. They could have also just forced the same upon WebKit PWAs until the API is ready. So many options. Yes, all of them would have taken some engineering work, but that hasn't stopped them from doing very complicated things in other aspects of their DMA compliance framework.
- deleted 3y ago
  [deleted]
- gruez 3y ago
  >I can't think of a PWA API that's impossible to implement in a third-party browser other than appearing in the app switcher under its own icon. Yeah but how much work would it be to implement, and is it worth implementing for the 1% of sites that use it?
deleted 3y ago
[deleted]
realusername 3y ago
On Android you can install a PWA with any browser, let's not act like it's impossible. I'm not saying it's straightforward to build the necessary apis for that but they had years to do it.
- zamfi 3y ago
  No one — including Apple — made the claim that it’s impossible. Just that it’s not worth it.

by zamfi 3y ago

lxgr 3y ago

> that they should have argued the DMA doesn't require PWA support for alternative browser engines? That would have been the least controversial aspect of their first attempt at compliance, in my view. They could have also just allowed third-party browsers to offer a "PWA home screen" as an intermediate step until the APIs are ready. I can't think of a PWA API that's impossible to implement in a third-party browser other than appearing on the home screen and in the app switcher under its own icon. They could have also just forced the same upon WebKit PWAs until the API is ready. So many options. Yes, all of them would have taken some engineering work, but that hasn't stopped them from doing very complicated things in other aspects of their DMA compliance framework.

deleted 3y ago
[deleted]
gruez 3y ago
>I can't think of a PWA API that's impossible to implement in a third-party browser other than appearing in the app switcher under its own icon. Yeah but how much work would it be to implement, and is it worth implementing for the 1% of sites that use it?

deleted 3y ago

[deleted]

realusername 3y ago

On Android you can install a PWA with any browser, let's not act like it's impossible. I'm not saying it's straightforward to build the necessary apis for that but they had years to do it.

zamfi 3y ago
No one — including Apple — made the claim that it’s impossible. Just that it’s not worth it.