• eveninghere@beehaw.org
    link
    fedilink
    arrow-up
    0
    ·
    edit-2
    4 months ago

    As a user, I don’t really get the argument of either side.

    Apple’s killing WPAs because they can’t allow 3rd party web engines to do that… That doesn’t make sense to me because Apple is still going to allow these browsers to open these WPAs as normal websites anyway.

    Now, how is it an attack to the openness of the web, though? Maybe these websites lose convenient access to users? But what do the users lose here? Especially given that they can distribute their apps through third party app stores. I don’t really understand the problem.

    • Max-P@lemmy.max-p.me
      link
      fedilink
      arrow-up
      0
      ·
      4 months ago

      I think they fear someone will make a browser that makes native apps less desirable.

      Google could wrap all the iOS widget, expose them to WASM and basically let people bypass the AppStore entirely and install everything as Chrome “apps”.

      Safari conveniently lacks a lot of the features that would compete with native apps in features, like refusing to implement WebPush until very recently.

      They don’t want web apps to even have a chance to compete with their AppStore. With Safari being the only allowed browser, they could make sure the browser is always less desirable than downloading the app.

      • eveninghere@beehaw.org
        link
        fedilink
        arrow-up
        0
        ·
        4 months ago

        But they are going to allow 3rd party app stores in EU, right? Then those chrome-based web apps wouldn’t be a bigger threat. Maybe I’m missing something.

        • Mars@beehaw.org
          link
          fedilink
          English
          arrow-up
          0
          ·
          4 months ago

          The apple third party App Store solution should be in a list under the title: Notable Examples in Malicious Compliance