• Vent
    link
    fedilink
    arrow-up
    30
    ·
    1 year ago

    Firefox supports PWAs, at least on mobile.

      • xigoi@lemmy.sdf.org
        link
        fedilink
        arrow-up
        11
        ·
        1 year ago

        They open in a window separate from the browser and don’t display the browser toolbar, so not just shortcuts.

        • Gamey@feddit.rocks
          link
          fedilink
          arrow-up
          4
          arrow-down
          1
          ·
          1 year ago

          The main purpose of PWAs is not to remove the browser toolbar but rather cache most of the website to improve speed and reduce data usage if I am not wrong, there are external tools to get rid of the toolbar but Firefox dropped the PWA spec which includes a lot more than just that.

          • AnarchoYeasty@beehaw.org
            link
            fedilink
            arrow-up
            2
            ·
            edit-2
            1 year ago

            The caching is the result of service workers which Firefox definitely supports.

            edit: oh just scrolled down and saw you already commented that later.

      • Vent
        link
        fedilink
        arrow-up
        4
        ·
        1 year ago

        Real PWAs, though PWAs aren’t that different from shortcuts tbh

        • Gamey@feddit.rocks
          link
          fedilink
          arrow-up
          2
          ·
          1 year ago

          As far as I know their main purpose is to cache various parts of the website properly which is a lot more than just a shortcut.

          • 𝒍𝒆𝒎𝒂𝒏𝒏@lemmy.one
            link
            fedilink
            arrow-up
            3
            ·
            1 year ago

            Regular websites can do that too using service workers - Lemmy’s webapp uses this to show an error when an instance is unreachable

            What we call a PWA is usually just a webpage with a webmanifest, and a service worker script to manage loading those cached resources you mentioned

            • Gamey@feddit.rocks
              link
              fedilink
              arrow-up
              2
              ·
              1 year ago

              Seems like you are right, the caching for proper offline usage and use with very limited internet connections is all done trough service workers. Their main job seems to be system integration and while Firefox Android kind of sucks at that too it doesn’t seem like they ever cut that down so they just dropped it for desktop users.

      • lw6352@lemmy.world
        link
        fedilink
        arrow-up
        3
        ·
        1 year ago

        On Android at least, Firefox PWA’s don’t seem to support registering system-level things (like ‘Share To’ handlers) - you need to use a Chrome PWA for that…