• threelonmusketeers@sh.itjust.works
    link
    fedilink
    English
    arrow-up
    0
    ·
    edit-2
    2 months ago

    PieFed won’t have an app any time soon due to the way it’s implemented.

    Why is that? They seem pretty similar on the surface, so I’m curious differences exist under the hood which would preclude app development.

    • hendrik@palaver.p3x.de
      link
      fedilink
      English
      arrow-up
      0
      ·
      2 months ago

      There isn’t anything stopping this. It’s just that no one is working on an app. And there isn’t any API implemented (yet) for an app to hook in to and fetch posts and comments. Both could be programmed. Someone could also copy the Lemmy API and use arbitrary Lemmy apps with Piefed. I think the developer is open to any of that and I’m pretty sure I read some feature request. It’s just that the focus currently is on other things. And Piefed works well as an progressive web app. You can open it in your browser and click “Add to home screen” and you’ll get an icon and a browser window that pretty much feels like an app. I’m using that and also don’t see any benefit in putting in the effort to maintain an app, when it works well as is.

      • threelonmusketeers@sh.itjust.works
        link
        fedilink
        English
        arrow-up
        0
        ·
        2 months ago

        Both could be programmed. Someone could also copy the Lemmy API and use arbitrary Lemmy apps with Piefed.

        This seems like an interesting idea. On one hand, I could see how it could hamper development, but on the other hand, it would be nice if all of the threadiverse platforms (Lemmy, Piefed, Sublinks, Mbin?) were standardized enough that the apps could be interoperable. I think giving users multiple options for how to access and interact with the content would be good for the fediverse as a whole.

        • Oliver Lowe@hachyderm.io
          link
          fedilink
          arrow-up
          2
          ·
          2 months ago

          @threelonmusketeers @hendrik This is how many Fediverse microblogging systems currently work; they serve the Mastodon API for client to server (e.g. app to server) interactions. GoToSocial doesn’t even provide any user interface; you use it from some app originally designed for Mastodon. Why? I think because Mastodon’s HTTP API is simpler, better documented and well-tested compared to something like ActivityPub’s Client-To-Server API.

          @fediverse