Re:Apple's intentional crippling of Mobile Safari continues
by nozzlegear on Sunday March 22, 2026 @11:45AM
(#47478714)
> A lot of very prominent apps are written using web technologies anyways. Take a look at the continued popularity of React Native (and Flutter as well).
And it shows through their laggy interfaces and non-native UI/UX. The people don't like apps built with web tech; developers and LLMs like them because they're a shortcut.
Re:Apple's intentional crippling of Mobile Safari continues
by rejhgadellaa on Sunday March 22, 2026 @01:22PM
(#47479806)
> The people don't like apps built with web tech
Then why do most people spend > 90% of their time in a browser (or web-powered app) on desktop?
Re:Apple's intentional crippling of Mobile Safari continues
by nozzlegear on Sunday March 22, 2026 @02:03PM
(#47480283)
Irrelevant, we're talking about mobile here.
Re:Apple's intentional crippling of Mobile Safari continues
by rejhgadellaa on Sunday March 22, 2026 @02:33PM
(#47480593)
How is that irrelevant? Isn't it important to ask the question "why did this thing work on desktop, but not on mobile?"
Re:Apple's intentional crippling of Mobile Safari continues
by genthree on Sunday March 22, 2026 @02:17PM
(#47480436)
No choice.
Re:Apple's intentional crippling of Mobile Safari continues
by rejhgadellaa on Sunday March 22, 2026 @02:36PM
(#47480626)
Funny you would say that. Because businesses and users have only one choice on iOS: native apps, because the web app isn't viable (and/or available) on iOS.
The UX of visiting a site and with a single click of a button having an app on my home screen sounds great. I'd also like to have the option of side loading a native app too. And if those options sound unappealing, you can keep using the App Store if you want the assurance of using an 'officially approved' app.
A lot of very prominent apps are written using web technologies anyways. Take a look at the continued popularity of React Native (and Flutter as well).