No. Designers and some devs hate web apps for minuscule reasons your average user doesn’t care about and doesn’t notice at all.

If an app helps them to get a task done, it simply doesn’t matter if the thing is native or not. At least, if you use a somewhat reasonable UI approach like Ionic.

Users absolutely want their apps to be as fast and fluid as possible. This is why they buy the newest Apple and Android phones every year, because their web apps are getting slower and slower.

> Users hate web apps, especially on mobile, and it has nothing to do with functionality. Web apps on the App Store invariably provoke angry screeds about how the look and feel is not right.

> Native apps are even more essential on mobile. On the desktop, web apps just look weird and waste battery life. On mobile, they feel wrong. That difference in feel provokes visceral hatred.

They don't have to waste battery life. This is mostly due to poor coding/architecture, instead of "web". Especially with WebGl and Wasm.

I agree with this. When you are creating a mobile experience for a website, you typically are burdened by the knowledge and existing designs/functionality of the desktop version which was usually built first.

When you are designing for a mobile app, you are free from the shackles that bind you to the desktop.

Of course, there is nothing stopping you from creating a separate web mobile experience, but human nature makes it harder to do so.

The biggest problem with mobile apps is that you don't always have a reliable connection to the internet, even when your carrier is claiming you have 4g lte with all the bars.

Web apps should really have the option to cache the page entirely for offline use.

They do. It's called a PWA. Service workers cache the assets.

https://developer.mozilla.org/en-US/docs/Web/API/Service_Wor...