• sugar_in_your_tea@sh.itjust.works
      link
      fedilink
      arrow-up
      6
      ·
      4 months ago

      Yeah, some of these questions made more sense for mobile than desktop. For example, I want to split tabs on desktop, but I don’t on mobile. Likewise, I don’t really care about PWAs on mobile (there’s usually an app with a better experience), but I do care on desktop because that isn’t a thing on my system (Linux).

      I think it would’ve been better had they broken them into groups for mobile and desktop.

    • Eufalconimorph
      link
      fedilink
      arrow-up
      5
      arrow-down
      2
      ·
      4 months ago

      PWAs were a feature I marked “want least”. I don’t like a cluttered home screen, I’d much rather just use bookmarks.

      • fmstrat@lemmy.nowsci.com
        link
        fedilink
        English
        arrow-up
        4
        ·
        4 months ago

        The reason I mention PWA for desktop is very different from mobile, but for either, a PWA can live anywhere, it’s just a menu less browser with the site’s icon vs the firefox one. Handy for sites with no apps that you want to be able to task switch independently for. They dont have to be on a home screen or desktop.

        Granted, the wording of the question would make one think so.

        • Eufalconimorph
          link
          fedilink
          arrow-up
          1
          ·
          4 months ago

          Yes, it’s a fancy way to save a tab. I just leave the tab open. Not a feature I want, so not something I want them to waste limited development time on. It’d be nice if it were through the bookmarks interface, so booarks could save state & history the way tabs do, but that’s not what’s proposed so I’d rather not have this. PWAs are a workaround to make up for the limitations of bookmarks.

    • jbk
      link
      fedilink
      arrow-up
      2
      ·
      4 months ago

      Don’t PWAs already exist and work on mobile? I think they’d work on desktop PWAs again then