whelp, there it is

  • esskay@beehaw.org
    link
    fedilink
    English
    arrow-up
    8
    ·
    1 year ago

    Good to hear. I’m kinda hoping the Apollo source will become public once it closes. Anything that gets us close to that kind of experience would be great.

    • BrooklynMan@lemmy.ml
      link
      fedilink
      English
      arrow-up
      20
      ·
      1 year ago

      I’m the UX designer on the app, so the idea is to get close in terms of usability and style while making the app “our own”. So, the app will, ideally, feel a lot like Apollo, but without outright copying it.

      We want to take the best of Apollo (minus some things we don’t like about it), and make something that’s inclusive of how lemmy works and operates.

        • BrooklynMan@lemmy.ml
          link
          fedilink
          English
          arrow-up
          11
          ·
          1 year ago

          I’m not involved in that project, but it’s an open community project. I’m sure you can go to them and voice your wishes.

      • Sinnz@feddit.de
        link
        fedilink
        English
        arrow-up
        7
        ·
        1 year ago

        Thanks for the already great work. It’s a bit barebones right now but easy to use. Excited to see what will be coming to the app!

      • TheRoarer@beehaw.org
        link
        fedilink
        English
        arrow-up
        6
        ·
        1 year ago

        minus some things we don’t like about it

        What don’t you like about Apollo? If you don’t mind me asking.

        • BrooklynMan@lemmy.ml
          link
          fedilink
          English
          arrow-up
          14
          ·
          edit-2
          1 year ago

          well, as a UX designer, there are some decisions he made, years ago, that were based on an older philosophy of iOS interaction design that have since been updated. An overreliance on list display modalities, for example, pull-up menus, and other minor things in the interface which make complex workflows tedious and which can be optimized using more contemporary workflow ideologies. Stuff that, as a solo developer, he didn’t have time to address but which, as a new team starting out, we can redesign from the ground up.

          We’re starting fresh, so we don’t have to worry about changing some monolith this that already exists. We have a lot more freedom than Christian does/did. We want to set a foundation based on the best of what we’ve learned from the greats but with a path for growth for the future for ourselves and our users.