> Everybody will slowly move to "web only" as 30% would kill their ability to compete with anybody else.

Frankly, yes, please. I mean, I'm biased as my whole career is in web app development, but there are so many things these days that do not need a whole native app. They're just communicating with a server backend somewhere, using none of the unique native functionality of the phone (much of which is available in browser APIs these days anyway). I can block ads in a web app much more easily. It's much harder to do customer-hostile things like block screenshots in a web app.

Native apps definitely have a place, but I think they're very overused, mostly for reasons that benefit the business at the expense of the customer.

▲

xnyan 2 hours ago | parent | next [-]

> I think they're very overused

I disagree, native apps on iOS have important abilities that no web application can match. The inability to control cache long-term is alone a dealbreaker if trying to create an experience with minimal friction.

▲

mircerlancerous an hour ago | parent | next [-]

Service workers allow you to control cache in web apps; you may be a bit out of date.

There are hardware APIs for some stuff that only works in native (cors, raw tcp), but 99% of apps don't need those.

▲

pphysch 2 hours ago | parent | prev [-]

Those same elevated controls are used to steal PII and sell to data brokers. Again, it's the companies that are trying to force apps on their users. If it were genuinely a much better UX, they wouldn't have to do that.

▲

xnyan an hour ago | parent [-]

I don’t think you are correct, but I could be wrong. For example, can you replicate the functionality of TikTok - autoplay unmuted videos as the user scroll down to new videos? It’s the experience that the user expects.

	▲	mrguyorama 8 minutes ago \| parent [-]
		I'm sorry but why do you think this can't be done in a website?

▲

BiteCode_dev 2 hours ago | parent | prev [-]

Apple makes sure it's not practical.

You still can't have a "share to" target that is a web app on iOS. And the data your can store in local storage on safari is a joke.

Of course, forget about background tasks and integrated notifications.

In fact, even on Android you miss features with web apps, like widgets for quick actions, mapping actions to buttons and so on.

And no matter how good you cache things, the mobile browser will unload the app, and you will always get this friction when you load the web app on the new render you don't have on regular apps.

	▲	mircerlancerous an hour ago \| parent [-]
		Service workers solve the cache issue; web apps can run permanently offline after initial load. You may be a bit out of date on the state of the web.