Seriously. I don’t want to install something on my phone when the dev is just using a WebView, if that’s what it’s called. When the app is basically just a website with the browser hidden.

What’s the reason for that? To attach the customer? To sell the app for money? Is there more ad revenue that way? Do you reach more people?

(Are there any good reasons for it, too? Security, maybe?)

  • AgentGrimstone@lemmy.world
    link
    fedilink
    arrow-up
    37
    arrow-down
    1
    ·
    11 months ago

    We had a project once that ran completely fine as a website except for the ability to scan bar codes. That one thing forced us to create an app and the rest of the app was just showing the website.

    • Syenite@lemmy.world
      link
      fedilink
      arrow-up
      2
      ·
      11 months ago

      There are JS barcode libraries out there, some better than others, some free, others paid. A few years back at a corporate job I built just the thing - a web app designed to replace a 3rd party mobile app. The back-end was Laravel + various AWS services, with a responsive front-end made with Tailwind.

      The requirements were to make it mimic most of the mobile app’s functionality. There was also location tracking via browser APIs (to track the cargo at all times) and a barcode scanner. I used a paid library for that, and it was quite expensive, but very reliable. So it can definitely be done as a web app.