• Potatos_are_not_friends@lemmy.world
    link
    fedilink
    arrow-up
    61
    ·
    6 months ago

    Department lead.

    The website team is small, but incredibly effective. Everything works. Everything is mobile friendly, responsive, fast. It’s a way better experience.

    I love my app developers, but they’re always behind. Not their own fault. Mobile development is complicated. There’s so many screen sizes, iOS vs Android differences, platform permissions, etc.

    The big reason for us to push the App on people was to get more brand awareness on the App Store. But the website is so much more better.

    You literally can use it as a web app right into your phone and get a better experience.

    And it’ll be such a dark day when I have to dissolve the App team (and hopefully convince them into web dev)

    • Stoposto@lemmy.world
      link
      fedilink
      arrow-up
      11
      ·
      edit-2
      6 months ago

      Why not a responsive web app packaged into native viewer app? Depending on your utilization of native components of cause.

      My team had the same issues you described so we build the web responsive and made that the “Apps” on the App Store + Google Play. There is still a tiny native components that hook into the web so you still need those native developers knowhow, but yes they will have to switch in large to web based development.

      Less maintenance, more devs for the main product, faster progress, fewer headaches with Apple and Google tooling.

      Edit: forgot to app that our customers loved that more features are available now on the “Apps” and that things work the same between devices

    • librejoe@lemmy.world
      link
      fedilink
      arrow-up
      1
      ·
      edit-2
      6 months ago

      But where is has the compromise happened? The Kotlin/Flutter/swift code written? The database? not being sarcastic just unaware.