Remix.run Logo
▲ spogbiper 6 hours ago

Why is Apple so hell bent on preventing alternate browser engines in iOS? Is there a financial benefit for Apple in forcing their own engine on every user? At the surface level this just seems silly so I must be missing something.

▲modeless 5 hours ago | parent | next [-]

The web poses a threat to their monopoly on iOS app distribution. If web apps could easily install PWAs with a home screen icon, with 64-bit wasm and access to a bunch of OS APIs not currently exposed to installed PWAs, then a lot fewer people would find it necessary to jump through Apple's App Store review hoops for the privilege of giving 30% of their revenue to Apple, on top of paying for the developer program subscription and buying Macs to run XCode.

▲nchmy 5 hours ago | parent | next [-]

This is it. The only answer. 30% toll-booth/extortion racket

▲hn-acct 3 hours ago | parent | prev | next [-]

> XCode. > 30%.

What features on the browser are blocked that are preventing your app from being a PWA? Is it one of the many Google supported privacy breaking features no other vendors want to implement?

▲realusername 26 minutes ago | parent | next [-]

Personally I have two issues with PWA for iOS:

- Install discoverability is awful and there's not a single install button API like Chrome

- Safari often break core web features like localStorage or indexDB and since it's the slowest browser to update, you are playing russian roulette

▲burnte 5 minutes ago | parent [-]

> and since it's the slowest browser to update, you are playing russian roulette

Because only updating the browser during a full OS upgrade was a stupid move. There's absolutely no reason it can't be upgraded via the app store like Google does with Chrome and other system apps, even ones that can't be removed.

▲cyberax 3 hours ago | parent | prev | next [-]

Regular apps have more access to de-identifying information than PWAs. JFYI.

There are all kinds of small issues. For example, we can't do HDR on iOS for photos in the browser because WebGPU doesn't support it.

▲ 3 hours ago | parent | prev [-]
[deleted]
▲basch 3 hours ago | parent | prev | next [-]

transpile a copy of gecko/firefox to js that renders to canvas?

▲paulryanrogers 2 hours ago | parent [-]

Sounds wildly inefficient

▲leptons 4 hours ago | parent | prev | next [-]

It's all of that, and also worse than that.

Apple is on the W3C comittee that gets to decide on which proposals will become standardized browser APIs. And they use their power there to block API proposals that could make browsers more capable, competing with native apps.

Apple is holding up quite a few useful API proposals, and they won't even suggest any changes to make to the proposals. They just do not want web browsers to be any more capable than they currently are. Apple is literally stifling innovation in favor of their own greed.

▲ 4 hours ago | parent | next [-]
[deleted]
▲paulryanrogers 2 hours ago | parent | prev [-]

Must W3C proposals be unanimously accepted?

It seems odd the world is letting one company hold our hand behind our backs.

▲leptons 2 hours ago | parent [-]

Firefox follows Apple on most things Apple wants to block. But again, instead of providing any feedback or proposing any changes, they just let these proposals die in committee. I would not doubt that someday we find out Apple has been somehow forcing Firefox to do this. There is simply no good reason to block WebBluetooth, WebSerial, or any of the many other APIs that would benefit developers and users. And no, it isn't a security issue, and no it isn't a privacy issue, as these APIs work the same way existing APIs work with regards to security and privacy - they are strictly opt-in per-website, just like the microphone and camera APIs are done now.

The only reasons I see Firefox blocking it is 1) Apple is paying them, 2) Firefox just doesn't have the resources to implement them. I'm leaning towards option 1, because Firefox shouldn't care what other browser makers have the resources to implement as long as the API proposals are sound (and they are sound).

Edit: If you're going to downvote, at least provide a comment as to why I'm wrong about any of this. Provide some evidence that counter my statements. I admit I stated opinions, not facts.

▲rstat1 an hour ago | parent [-]

WebBluetooth and WebSerial shouldn't be a thing anyway, websites don't need access to serial ports or bluetooth

▲leptons 42 minutes ago | parent [-]

>WebBluetooth and WebSerial shouldn't be a thing anyway, websites don't need access to serial ports or bluetooth

What kind of thought process did you use to arrive at this conclusion? It's really not very well reasoned, honestly.

There have already been several great projects that use these APIs. You thinking they don't matter is nonsense, because many people know that web browsers do benefit from these APIs, and I have many uses for them myself.

These APIs allow me to avoid Apple's App Store, and being forced to buy Apple desktop and mobile devices just to develop an iOS app where they can then extract even more money from me through the app. So Apple users will just have to suffer instead, because I refuse to give Apple that kind of money.

I need Web Bluetooth to communicate with my hardware device product. I don't want to have to pay Apple for the privilege to use bluetooth when it works perfectly fine in a web browser that isn't intentionally crippled.

▲omnimus 4 hours ago | parent | prev | next [-]

It's so funny considering that at some point Jobs was pushing this version of webapps as future of iOS instead of native appstore apps.

▲nchmy 4 hours ago | parent [-]

PWAs were literally Steve Jobs' vision for the iPhone when he launched it https://www.youtube.com/watch?v=QvQ9JNm_qWc

▲paulryanrogers 2 hours ago | parent [-]

That may be what he said at the time. It was easier for Apple and differentiated from competitors. Yet that changed so quickly I find it hard to believe they weren't already working on native apps behind the scenes.

▲dhosek 12 minutes ago | parent [-]

There was some movement that way, but it was a skunkworks project and not part of the official plan, as I recall.

▲thedonkeycometh 2 hours ago | parent | prev | next [-]

[dead]

▲theturtletalks 5 hours ago | parent | prev | next [-]

It’s exactly what I’m doing with my personal OS. It’s a web app that runs on my Mac and I access it on my phone using Tailscale and PWA. I haven’t missed not having a native app since web is that good now.

Apple only allows you to access the microphone if you use HTTPS so I had to use Tailscale serve to get a url and I use that.

Distribution is tricky since you’re asking a person to run a web app but fuck Apple’s walled garden.

▲dimitricole 5 hours ago | parent [-]

[dead]

▲theturtletalks 4 hours ago | parent [-]

This is actually really cool! I can make apps for friends and family and I guess their own personal OS? And it’s open-source. You should put a link to the GitHub on the website:

https://github.com/snowy-ghost/ovenlight

▲dimitricole 4 hours ago | parent [-]

Thanks! And yes exactly, friends and family is who it's for and also just fyi mic access does work inside Ovenlight. And great feedback, I wanted to make it open source so that people felt comfortable trusting it to serve their private apps, so I'll make sure that's front and center on the site. Curious what does your personal OS do?

▲theturtletalks 3 hours ago | parent | next [-]

Yes I really like how you allow me sharing the app with one person without sharing my whole computer. And since it’s native, you can probably do PiP and even widgets. And PWAs don’t support FaceID either and yours does.

For my personal OS, the main app is one where I can control terminals on my Mac on a web page and I built that into the personal app. The other is a calendar that’s not connected to Google or Apple calendar. It has an MCP so Claude can schedule tasks for me, workout session, LinkedIn posts, etc. It has a nice timeline so I can see my day.

Another big app is curator where I started finding and collecting nice things I find on the internet and good websites. Overall it’s a great playground to get ideas off the ground before turning them into fully fleshed products.

I also made a lot of mini apps in personal OS for websites I don’t like or push ads so I use their unofficial API. It also has a built in web browser in the web app itself so I can look at the website changes and dictate to the AI at once. Overall it’s helping me build an open-source Shopify for every vertical.

▲rsingel 3 hours ago | parent | prev [-]

This is really cool. Excited to play with it.

My one suggestion is to create a style guide for Claude so that the homepage doesn't have Claudeisms.

For example, Claude loves the word hold, which is v annoying. The word "with" is right there.

E.g. "anyone holding its invite link"

▲viktorcode 4 hours ago | parent | prev | next [-]

That does not add up. In the EU you can distribute apps on iOS outside of App Store. So, there's no monopoly.

▲mentalgear 4 hours ago | parent [-]

Effectively it is because getting accredited as an official App Store is made so ridiculously demanding by Apple that almost no one can afford it and then you still have to somehow get consumers to switch to your App Store.

▲viktorcode 4 hours ago | parent [-]

Why do you have to set up your own App Store when others have already done that? There are alternative stores; publish there without any Apple oversight.

▲rpdillon 3 hours ago | parent [-]

There's plenty of oversight on the alternative app stores. Apple still retains the authority to block apps regardless of what store they come from.

▲viktorcode an hour ago | parent [-]

What's important is that you can publish without Apple's review. I doubt that unless you publish something extremely criminal Apple would care to revoke the certificate.

▲boxed 5 hours ago | parent | prev [-]

That's an entirely separate thing. Allowing alternate web engines is wholly different from those web engines being able to add arbitrary icons to springboard.

▲odo1242 3 hours ago | parent | prev | next [-]

Browser engines require JIT compilation to work with any sort of performance. The whole iOS security model is (at least partially) based on Apple being able to validate all app code in advance, so Apple doesn't want apps to be able to ship engines that can do their own code generation since they can't sign code generated at runtime.

▲geocar 6 hours ago | parent | prev | next [-]

> Why is Apple so hell bent on preventing alternate browser engines in iOS?

To keep Safari relevant.

> At the surface level this just seems silly so I must be missing something.

I worry a lot about the day Chrome becoming possible on iPhones, because at that point, people will be able to ignore Safari.

▲curt15 5 hours ago | parent | next [-]

Chrome wouldn't magically install itself or make itself the default browser. Users would only ignore Safari if they explicitly want to use Chrome.

▲Tagbert 5 hours ago | parent | next [-]

True, but Google is very aggressive about promoting Chrome on its sites and Gmail. And if you have it installed as an alternative browser it will not stop asking you to make it the default.

▲superb_dev 4 hours ago | parent | next [-]

Every Google app I have will first ask to open a link in Chrome, even though it’s not installed. They are very aggressive about it

▲hysan an hour ago | parent | next [-]

Google Maps loves to randomly decide to forget your chosen default option and bring up their picker with Chrome up top and system default below the fold. (And no, I rarely update maps and I only have one account that’s always signed in. There’s nothing I’m doing that would make me think that I “reset” maps somehow.)

▲lern_too_spel 35 minutes ago | parent | prev [-]

That's a problem with iOS not allowing setting default apps for a long time (2020 for browser, 2025(!) for maps). If these prompts remain, it's because iOS users have gotten used to it, so Google thinks it can get away with it. This was never a problem on Android.

▲lern_too_spel 5 hours ago | parent | prev [-]

I've used Firefox as my default browser on Android for years. I have not run into this issue.

▲tredre3 2 hours ago | parent | next [-]

Google is less aggressive on mobile browsers, as well as on Firefox in general (I still see it there occasionally). But try going to google.com in any Chromium-based browsers on a desktop PC and you'll see this: https://ibb.co/xt3V26mQ

(the nag likely varies by region, time of day, your browser extensions, operating system, and moon alignement so ymmv)

▲lern_too_spel 33 minutes ago | parent [-]

If you use a Chromium-based browser, you search from the omnibox and would ~never see that.

▲bigyabai 4 hours ago | parent | prev [-]

Same here, and I refuse to use mobile apps for many experiences. No idea where people get the idea that Chrome is forced onto you if you don't want it.

▲GeekyBear 5 hours ago | parent | prev | next [-]

Google literally paid companies with popular software downloads to hide a Chrome install inside their own product's installer.

If users didn't pay enough attention while clicking next through the installer, they ended up with Chrome as their default browser without understanding how that had happened.

▲curt15 5 hours ago | parent | next [-]

Which iOS applications bundle Chrome in their own installer?

▲andylynch 2 hours ago | parent [-]

Dude is talking about Windows. This used to be super common

▲curt15 7 minutes ago | parent [-]

The article is about web browsers on iOS.

▲lern_too_spel 4 hours ago | parent | prev [-]

This story sounds a lot like Apple hiding a Safari install for people installing iTunes to use their iPods. https://www.theregister.com/off-prem/2008/03/24/mozilla-ceo-...

This behavior is disallowed on the App Store, and nobody is asking for that policy to change, but of course Apple, Google, and the Android OEMs can use their privileged position to bundle apps with the OS.

▲Twey 4 hours ago | parent [-]

> of course Apple, Google, and the Android OEMs can use their privileged position to bundle apps with the OS.

https://en.wikipedia.org/wiki/United_States_v._Microsoft_Cor....

▲troupo 5 hours ago | parent | prev | next [-]

Google goes out of its way to force me to use Chrome.

E.g. despite repeatedly getting "use safari/default browser" all Google apps will ask you again, and again, and again, and again, "Open in Chrome (default choice), Safari, System browser"

▲geocar 5 hours ago | parent | prev | next [-]

Users will install Chrome because they will run into a website which only works on Chrome.

You might not consider that magic, but I do: Look how it changes absolutely everything about what you said without you needing to change a single word.

▲fearthemachine 4 hours ago | parent | prev | next [-]

Google (and others, for different reasons mostly amounting to being cheap or lazy) push people toward Chrome, either very-forcibly ("sorry, Chrome only, go away and come back with Chrome") or by making their sites suck on other browsers (Google likes to do this to desktop Safari and Firefox; my latest encounter is that it's, for weeks, been popping up a tiny and long-lived "unreliable stream?" interactive "toast" directly over the "play/pause" button on Youtube for me, for no reason [the streams are fine! My connection is great! My computer is fast!], but I'm sure being on the "wrong" browser is "accidentally" triggering something, yet again).

I recently had to install Chrome (Chromium wouldn't cut it) on my Mac laptop to do a Telehealth call. That and Edge (which is also Chrome, though that wasn't enough for Chromium to be allowed) were the only two browsers it'd permit, Safari, Firefox, and Chromium (I had all three already) were all refused. That horse-shit would be all over iOS too, if more browser engines could run on it.

On the one hand, they may have self-serving reasons for not permitting other browser engines on iOS. On the other hand, I'm very glad they do it for my own selfish reasons.

▲sroussey 5 hours ago | parent | prev [-]

Chrome does not magically install itself or make itself the default browser on MacOS or Windows either.

Yet…

▲orangecat 3 hours ago | parent | prev [-]

I suspect that a $5 trillion company could do a reasonable job of competing in browsers if they had to.

▲solyin 6 hours ago | parent | prev | next [-]

Yes. Apple gets more money if they don't open up, according to this UK government investigation. 2022.

https://www.gov.uk/government/publications/mobile-ecosystems...

▲asdfsa32 6 hours ago | parent | prev | next [-]

There are some browsers but nothing with JIT, Apple doesn't want to allow JIT because it makes it easy to bypass the operating system restrictions.

▲spankalee 6 hours ago | parent | next [-]

They don't want to allow JIT because it lessens the monopoly of the App Store.

▲larme 5 hours ago | parent [-]

For all the hacker news users talking about apple's monopoly, please first talk about Google's monopoly controls of the web. After all apple is at least not monopoly on the entire smart phone market while Google is the web and half of the smart phone market

But hacker news users won't do that because they complain about Apple not because they are close or monopoly, but they make squeezing money from web users a little bit harder

▲chaosharmonic 5 hours ago | parent | next [-]

I don't disagree with you, but that goes both ways here too.

Chrome isn't exclusive to one platform, and conversely Android doesn't force you to use it across the entire operating system.

If Chrome is forcing Web standards even in places where no one wants them, the equal and opposite problem is that Safari has a long history of holding back Web standards that are inconvenient to them, and making the entire industry bend around them because their users don't have the option to just install something else.

Part of the problem is actually that Apple also won't really compete here. They want the vertically-integrated everything, and so WebKit everywhere other than their devices is a second class citizen. The support for its underlying stack anywhere else -- from Linux-based browsers like GNOME Web to runtimes like Bun using JavaScriptCore -- has come pretty much entirely from third parties, and there doesn't really seem to be any sort of toolkit analogous to the CEF that could be used to embed it into other applications.

If anything, the only viable effort to make WebKit available across platforms was Chrome.

▲troupo 5 hours ago | parent [-]

> If Chrome is forcing Web standards even in places where no one wants them

Chrome isn't forcing web standards. Chrome is forcing Google's own APIs, and calling them Web Standards

▲chaosharmonic an hour ago | parent | next [-]

You're not wrong, but think of it this way:

As long as this is the current state of things with WebKit, the counterweight to that is that Apple ultimately gets veto power over any standard the rest of the industry does agree on, and random HTML and CSS features will sit functionally unusable for years because a single OS vendor doesn't see them as a priority.

The problem that we're both ultimately getting at here is that one vendor shouldn't get to have a chokehold on the spec. With Safari it just happens to be closer to what was wrong with IE.

▲nemothekid 25 minutes ago | parent | next [-]

>the rest of the industry does agree on

The "rest of the industry" is functionality just Google. The only reason Google pretends to care about "standards" is because of the large amount of iOS users on WebKit. That evaporates when Google, via Chromium has complete control of the web platform.

▲troupo 11 minutes ago | parent | prev [-]

> As long as this is the current state of things with WebKit

Firefox also rejects the Chrome-only non-standards

> ultimately gets veto power over any standard the rest of the industry does agree on

Where "rest of industry" is invariably "we build from Chromium source code with very little changes".

Apple very rarely vetoes standards that non-Chromium browsers (aka Firefox) also agrees on.

▲PaulHoule 2 hours ago | parent | prev [-]

The poor adoption of PWAs is part of that disease.

I mean, Web Workers is something only Google could love. They could have provided an API that would let you give commands to the cache layer of the browser and it would have the speed and reliability of native code behind it and if the system wants to evict one piece of data from the cache to deal with storage pressure... it can. Instead they invented a Rube Goldberg machine which doesn't really do anything and you have to write another Rube Goldberg machine inside the first Rube Goldberg to get "offline operation as a service." And you've got to deal with all the async programming difficulties and unreliability and I know for years all the storage operations you could back it with are awful.

Like I'm the guy who signs off on the ticket being done and I've been the guy who answers the pager when it goes off in 2 in the morning and even when I'm getting a stage demo ready for somebody who has the improv acting and stage magic skills to make a 20% done app look like... magic I have to get that 20% functionality working 100% in some certain sense and the Web Workers API screams "you're going to mess around with this forever and it's never really going to work right" whether the product is under or over baked or just right.

So the discussion about PWAs is another one of those discussions that SV has with itself without involving the other 99% of software developers and web users. Google might have had a lot more luck pushing it had they involved a focus group of people in Minnesota or Dublin somewhere.

And of course that 1/3-baked notifications API just raises my hackles, like the first thing I am going to do with a new web browser is turn it off. I mean, every web site is already trying to spam me every way it can possibly spam me, the last things I need are another pop-up menu that covers content, another dialogue of any kind to close, and the possibility that I'll click the wrong button and get spammed.

(And in the "iOS sucks" department, notifications are a big part. I've found that if I have any kind of filtering or groupings I lose important notifications, I will find out i got a text message from my son a week after I get it, etc. To have a decent experience I have to turn filtering/grouping off and give notifications permissions to the few apps that I need notifications from)

▲ozlikethewizard 5 hours ago | parent | prev | next [-]

It's possible to be critical about more than one thing at a type. But to hand it to google, chrome won because it was better for users. Webkit only wins because of structural control. Same for android really, you can run a non google OS on most (all?) android phones, for now at least. the consumer still has choice. Being a hacker is about liberty, and a critical part of liberty is the freedom to make choices (even not the best ones, looking at chrome lol).

▲spankalee 5 hours ago | parent | prev | next [-]

This isn't about Google, it's about Apple. And it's not just about browsers, it's about JIT too.

Consider that if the web was created today, it would never be allowed to run on iOS. The next web-like thing won't be allowed run on iOS without new lawsuits.

▲leptons an hour ago | parent | prev | next [-]

>For all the hacker news users talking about apple's monopoly, please first talk about Google's monopoly controls of the web.

No, Google does not control "the web". You're trying to divert the conversation to Google instead of the topic of Apple's abusive business practices.

Apple doesn't even make Safari for any other platform anymore. They used to but they decided to stop. They could compete with Google's web browser, but they don't. They prefer to stay in their closed ecosystem, not even trying to compete and forcing other browser makers to use their browser engine.

Maybe we should talk about why Apple doesn't make Safari for other platforms and their abusive business tactics, instead of whatever Google does.

▲cyberax 3 hours ago | parent | prev [-]

Can we talk about the mating habits of spotted owls in Nebraska instead? I think it's more relevant to the topic at hand.

▲leptons an hour ago | parent | prev [-]

I'm not sure why JIT is okay on desktop, but not okay on mobile. Is the desktop any less important than mobile? Does Apple not care if JIT is used to exploit desktop computers? My mobile phone is way more likely to get lost or stolen than any other device I own, so I don't keep anything of value on it. I simply don't worry about JIT exploiting it as much as I do someone at a coffee shop walking away with it.

▲nicoburns 5 hours ago | parent | prev | next [-]

Google pays Apple roughly $20B a year to keep Google the default search engine in Safari. It only does this because of Safari's market share.

▲pmontra 3 hours ago | parent [-]

I've seen reports of about 2 billion active iPhones, that would be $10 per device. It means that Google can extract a lot of money from that people.

▲Marsymars an hour ago | parent [-]

Somewhat more money per device - per legal filings, only about 60% of searches go through access points governed by that agreement.

▲GeekyBear 5 hours ago | parent | prev | next [-]

> Why is Apple so hell bent on preventing alternate browser engines in iOS?

They don't trust third parties to keep up with exploits on such a large attack surface.

The sheer quantity of old school Flash's exploits were a recent memory when the policy was set.

▲realusername 5 hours ago | parent | next [-]

Safari is the last non-evergreen browser since it's tied to the OS and the slowest to update so I'm not sure the security argument goes in their favor.

▲lern_too_spel 5 hours ago | parent | prev [-]

At the time of the DMA, this wasn't a problem. What's your next excuse?

▲notnullorvoid 5 hours ago | parent | prev | next [-]

A large part is to hinder PWA capabilities on iOS, having equivalent PWA support to Android would drastically impact App Store revenue.

▲CharlesW 5 hours ago | parent [-]

The Safari team is doing a terrible job of hindering PWA capabilities on iOS: https://pwascore.com/

> …having equivalent PWA support to Android would drastically impact App Store revenue.

This would be a credible argument if PWAs on Android had any impact.

▲notnullorvoid 4 hours ago | parent | next [-]

The biggest potential market (revenue wise) for PWA is mobile games. Safari mobile has no fullscreen, screen orientation lock, or vibration API.

PWA installation is also more hidden on iOS, it can't be initiated from a user interaction on the page. The user has to manually go through the share menu, a very non-intuitive location.

> This would be a credible argument if PWAs on Android had any impact.

How are you so sure they don't? Regardless there is less necessity on Android. Google Play store rules and fees are slightly more favorable, there's also third party app stores, and side loading.

▲dunham 2 hours ago | parent | prev | next [-]

Meanwhile mozilla cancelled their PWA support for desktop. :( I was hoping PWA would help end electron bloat.

Safari desktop, however, even lets me wrap web apps like Slack that weren't coded to support PWA.

▲notnullorvoid 11 minutes ago | parent [-]

Firefox dropping desktop PWA was a catalyst for my switch to Brave across desktop and mobile.

▲nchmy 5 hours ago | parent | prev [-]

Every time this topic comes up, you and your terrible site pop up to spread absolute nonsense about this topic. Are you a paid Apple shill?

For others, here's the real truth of the matter: https://infrequently.org/series/browser-choice-must-matter/

https://open-web-advocacy.org

▲CharlesW 5 hours ago | parent [-]

The site is objective, data-based, and open source, built in response to HN folks posting feelings-based claims. I created it assuming Safari would eat shit, as I was told it would.

> For others, here's the real truth of the matter:

Just look at this person's history and tell me they're objective. I have no skin in the game, other than being a fan of the web as a platform generally and PWAs specfically.

▲rpdillon 3 hours ago | parent | next [-]

I compared your site to https://wpt.fyi/. Your site seems to track fewer features.

▲nchmy 4 hours ago | parent | prev [-]

If you were a fan of the web and PWAs, you would be as vocal as I am in denouncing Apple's nonsense. Instead you just add to it.

Here's our most recent exchange https://news.ycombinator.com/item?id=49727868

▲nchmy 5 hours ago | parent | prev | next [-]

This exceptional series of blog posts explains everything: https://infrequently.org/series/browser-choice-must-matter/

and this org is doing the most and best work to force Apple to change. Please support them: https://open-web-advocacy.org

▲monocularvision 5 hours ago | parent | prev | next [-]

They obviously don’t want to allow alternate browser engines but the only objection the alternate browser vendors have is that they’d had to release a new app (since they allow only alternate browser engines in certain markets)

That sucks, for sure, but I don’t see why that stops the browser vendors. Like… why wouldn’t just release a second app and see how it performs?

▲k9294 5 hours ago | parent | prev | next [-]

> The deal between Apple and Google makes Google the default search engine in Apple's Safari browser, with Google paying Apple roughly $20 billion annually (including a 36% share of search advertising revenue generated through Safari).

So.. Yes. More hoops to jump over, less competition, bigger market share, profit.

▲afavour 4 hours ago | parent | prev | next [-]

A simple technical reason (and no, I’m not saying there aren’t anti-competitive reasons they do it too) is the locked down OS.

Safari has JIT. The webview you use inside apps runs in its own process, and has JIT. If you run JavaScriptCore in your own process, it doesn’t have JIT. So they’re clearly concerned about the possibility of JIT breaking some kind of security concern.

▲nchmy 4 hours ago | parent [-]

This is not even slightly why they prevent alternative browser engines.

▲afavour 4 hours ago | parent [-]

I don't think you can dismiss the fact that they don't even allow their own JavaScript engine to use JIT in third party apps as absolutely nothing to do with it.

▲shmerl 2 hours ago | parent | prev | next [-]

They were always extreme in market manipulation anti-competitive and lock-in behavior like that, as long as they thought they could get away with it, damaging the competition with impunity.

Browsers in iOS is just one of the most infamous examples, but they do it all over the place.

▲doublerabbit 6 hours ago | parent | prev | next [-]

They would have to expose parts of the OS that they like to keep close.

▲ozlikethewizard 5 hours ago | parent | prev | next [-]

The cynic in me says Apple intentionally gimp Safari + webkit making the mobile 'web app' experience pretty terrible on iOS. Poor web apps leads to requirement for good native app, Apple retains strong control over what gets run on their devices and maintains their very juicy cut of in app purchases.

▲CharlesW 5 hours ago | parent | next [-]

> The cynic in me says Apple intentionally gimp Safari + webkit making the mobile 'web app' experience pretty terrible on iOS.

Safari is as bad at PWAs on iOS as Firefox is for PWAs on Android. https://pwascore.com/

▲Tade0 5 hours ago | parent | prev | next [-]

> The cynic in me says Apple intentionally gimp Safari + webkit making the mobile 'web app' experience pretty terrible on iOS.

I mean, that's the prevailing notion.

There's the question of battery life, but that isn't really well served by having e.g. poor touch sampling when a WebGL app can easily go through the entire battery of an iPhone in an hour.

▲carlosjobim 4 hours ago | parent | prev [-]

Is there actually any overlap to talk about of web apps that are also one time payment? What apps are we talking about? I don't see many paid apps out in the wild which aren't exclusively native (as opposed to web). Subscription apps easily bypass Apple's app store cut.

I purchase native apps whenever I need to. I wouldn't mind purchasing a web app if that was the best option, but where are they for sale?

▲alerighi 5 hours ago | parent | prev [-]

Because with browser with an alternative engine (like Firefox) you can run extensions, and with extension you can (for example) block ads reliably on every site, bypass paywalls, access piracy sites, and do all sort of stuff that Apple prohibits you to do.

I wouldn't be surprised if Google will start attaching Firefox even on Android in favor of Chrome... the sole reason they probably didn't already do so is that they fear sanctions from the EU and other countries that have antitrust in place.

▲mannyv 5 hours ago | parent [-]

I run ad blockers etc just fine on iOS.

You need to be up-to-date if you're going to spew bullshit. Ask the AI first.

▲akersten 3 hours ago | parent | next [-]

Ok, I'll bite, how are you running uBlock Origin (or similar blocking that uses the fanboy/easylists) on iOS today? With dynamic JS blocking, like I have on desktop and Android, so that trackers and such are actually blocked, instead of just some weak DNS-level blocklist that does some superficial adblocking. And SponsorBlock, how are you running that?

If I can't replicate that on iOS then it's not "just fine," imo, and I presume that's the GP's point. If I can't do that, the "bullshit" is the claim that adblocking works on iOS.

▲breakwaterlabs 2 hours ago | parent | next [-]

Just FYI, Orion supports extensions. Both Orion and Brave also have native adblocking supporting arbitrary filter-lists that perform dynamic JS blocking.

> SponsorBlock, how are you running that?

This is literally available in the app store, if you choose not to use Brave / Orion.

▲odo1242 2 hours ago | parent | prev [-]

You can run uBO with Orion browser (Apple doesn't allow swapping browser engines, but they do allow network filtering and editing webpages/running scripts)

SponsorBlock has an officially supported iOS app (or you can use Orion browser)

▲akersten 2 hours ago | parent [-]

Just installed Orion and uBO + SponsorBlock seem to work. Thanks.

I had it in my head that that somehow wouldn't be possible without Apple allowing other browser engines. Happy to learn I was wrong!

▲ozlikethewizard 5 hours ago | parent | prev [-]

Ya'll still watching youtube ads though?

▲Asmod4n 5 hours ago | parent [-]

Haven’t seen a YouTube ad in years on iOS, or do you mean the lack of sponsor block?