[da_chicken]

End users don't care about if it's an app or not.

What they care about:

- Does it do what I need it to

- Can I access it easily

- Is it easy to navigate

- Does it work or is it buggy

- Is it slow

- Does it abuse notifications

- Is it prompting me to log in all the time

- Are there too many ads

- Can I use it on any device I have

- Does it complain about updating constantly

I don't think any of those actually has to do with being a website. The problem is that web browsers and websites didn't get a not-stupid UI for phones faster than the phone vendors could funnel everyone into their walled garden. Remember "click here for mobile" and having to develop two web interfaces? And half the time functions would be missing on one side?

[swishman]

I feel like I'm taking crazy pills reading these comments. Apps are clearly better for end users.

HTML and css is SUPER slow. It doesn't feel native, it doesn't feel good to use.

You also get so many weird glitches with state refreshing, sessions being cleared, log in not persisting.

Has anyone here actually used a PWA? You can feel that it's slow and clunky. Apps feel SO much better with the native UI, pre-downloaded, much faster etc.

[edude03]

You might be taking crazy pills or you've yet to come across an app that's just a webpage inside a web view (a lot of apps these days unfortunately)

[swishman]

For sure, and these apps feel bad. I notice instantly. But they manage local storage, caching, and sessions much better than a PWA anyway

[akoboldfrying]

I've found the most consistent indicator of overall app quality to be whether it is extremely small in size. An Android app under a megabyte in size is going to use the familiar, high-performance platform-native UI because it doesn't have room to do anything else. It is gonna do what it says on the tin and nothing else. It won't have ads. It won't phone home. Since it doesn't show ads and doesn't phone home, it's quite likely open source, meaning it quite likely has a GitHub project that I can look into if something goes wrong -- and because it's so tiny, I won't need to spend days trying to figure out how it works.

[Rohansi]

Or, you know, it's small because it's just a WebView wrapping a website.

[Rohansi]

> You also get so many weird glitches with state refreshing, sessions being cleared, log in not persisting.

And these don't happen in native apps? Because they somehow have less bugs?

> Apps feel SO much better with the native UI, pre-downloaded

React Native apps are pre-downloaded and have a native UI. Lots of them feel really bad. Not all, though.

You can make fast websites/PWAs just like you can make slow apps.

[swishman]

A web app is limited. Even if it loads fast, it feels clunky. Apps using native components have a much higher ceiling. Users don't care what tech is underneath

[Rohansi]

> A web app is limited. Even if it loads fast, it feels clunky.

But what about it feels clunky?

HTML and CSS are a lot faster than you want to believe. You can't tell me you've never used a website that isn't slow. Problem is the people making most websites don't care to optimize or profile anything.

[pjmlp]

Except most "native apps" shipped by most companies are Webviews, React Native, Cordova, Flutter, MAUI, and very seldom written with the native SDKs.