• jacksilver@lemmy.world
    link
    fedilink
    arrow-up
    13
    ·
    7 months ago

    I’ve used it before and it’s got it’s pros and cons. Ultimately the big thing is not all apps need to be the “killer app”. Some apps are pretty simple, so a one size fits all can be nice. It’s definitely not the same as developing natively, but for small teams/apps it’s not too bad.

    • GissaMittJobb@lemmy.ml
      link
      fedilink
      arrow-up
      3
      ·
      7 months ago

      If you’re prioritizing cost, you should probably already be building a web application imo. There’s very few cases where I would recommend cheaping out and building a native app, it’s just kind of unsound.

    • GissaMittJobb@lemmy.ml
      link
      fedilink
      arrow-up
      3
      ·
      7 months ago

      If you’re prioritizing cost, you should probably already be building a web application imo. There’s very few cases where I would recommend cheaping out and building a native app, it’s just kind of unsound.

    • GissaMittJobb@lemmy.ml
      link
      fedilink
      arrow-up
      3
      ·
      7 months ago

      If you’re prioritizing cost, you should probably already be building a web application imo. There’s very few cases where I would recommend cheaping out and building a native app, it’s just kind of unsound.

    • GissaMittJobb@lemmy.ml
      link
      fedilink
      arrow-up
      3
      ·
      7 months ago

      If you’re prioritizing cost, you should probably already be building a web application imo. There’s very few cases where I would recommend cheaping out and building a native app, it’s just kind of unsound.

    • GissaMittJobb@lemmy.ml
      link
      fedilink
      arrow-up
      3
      ·
      7 months ago

      If you’re prioritizing cost, you should probably already be building a web application imo. There’s very few cases where I would recommend cheaping out and building a native app, it’s just kind of unsound.

      • ericjmorey@programming.dev
        link
        fedilink
        arrow-up
        2
        ·
        edit-2
        7 months ago

        It looks like your reply got submitted multiple times.

        I agree with you now about preference for web apps, but that was not the case when Google started pushing Flutter.

        • GissaMittJobb@lemmy.ml
          link
          fedilink
          arrow-up
          4
          ·
          7 months ago

          Looks like my Lemmy-client of choice did some retrying when I had poor connection, sorry about that.

          I think trying to go cheap on native apps was always kind of a fool’s errand, tbh. Cordova, Xamarin, React Native and so on - all pretty sub-par solutions leading to poor experience without actually materializing the desired savings.

        • GissaMittJobb@lemmy.ml
          link
          fedilink
          arrow-up
          2
          ·
          7 months ago

          Looks like my Lemmy-client of choice did some retrying when I had poor connection, sorry about that.

          I think trying to go cheap on native apps was always kind of a fool’s errand, tbh. Cordova, Xamarin, React Native and so on - all pretty sub-par solutions leading to poor experience without actually materializing the desired savings.

        • GissaMittJobb@lemmy.ml
          link
          fedilink
          arrow-up
          2
          ·
          7 months ago

          Looks like my Lemmy-client of choice did some retrying when I had poor connection, sorry about that.

          I think trying to go cheap on native apps was always kind of a fool’s errand, tbh. Cordova, Xamarin, React Native and so on - all pretty sub-par solutions leading to poor experience without actually materializing the desired savings.

    • GissaMittJobb@lemmy.ml
      link
      fedilink
      arrow-up
      3
      ·
      7 months ago

      If you’re prioritizing cost, you should probably already be building a web application imo. There’s very few cases where I would recommend cheaping out and building a native app, it’s just kind of unsound.