• rmuk
    link
    fedilink
    English
    arrow-up
    8
    arrow-down
    1
    ·
    9 months ago

    Apple was trying to get rid of PWAs. End of. If you used Safari: no PWAs. If you use Firefox or Edge: no PWAs. Since the PWA rendering engine is part of the OS in the same way that MacOS and Windows include their own web rendering engines separate from the web browsers, they could easily continue use that for PWAs even if Safari was ‘uninstalled’. The whole thing was Apple throwing a tantrum at being forced to do something for the benefit of not-Apple.

    • Zoolander@lemmy.world
      link
      fedilink
      English
      arrow-up
      2
      arrow-down
      7
      ·
      9 months ago

      That is not true. Apple was disabling PWAs because the new EU regs require that they allow other browser engines for browsers and there are considerations that would need to be taken into account for end users. Since PWAs can be run in standalone modes, it is reasonable to expect that they would fall under those regulations as it’s still a browser engine displaying the content but without any window chrome. This changed after it was clarified that it only applies to browsers downloaded from App Stores, known as “dedicated browser applications”.

      The idea that Apple was trying to “get rid of PWAs” is ridiculous since the entire reason the App Store didn’t exist on iPhone was that Apple was trying to push PWAs.

      • apfelwoiSchoppen@lemmy.world
        link
        fedilink
        arrow-up
        4
        arrow-down
        2
        ·
        9 months ago

        One can commit to an idea, not use it anymore, and then try to get rid of it.

        Your arguments make splitting hairs seem simple.

        • Zoolander@lemmy.world
          link
          fedilink
          English
          arrow-up
          2
          arrow-down
          6
          ·
          9 months ago

          At least I made an argument based in reality. You contributed nothing and made no point.