[ladon86]

> Today, iOS users already have the ability to set a third-party web browser — other than Safari — as their default. Reflecting the DMA’s requirements, Apple is also introducing a new choice screen that will surface when users first open Safari in iOS 17.4 or later. That screen will prompt EU users to choose a default browser from a list of options.

Any idea if this means you can actually choose a different browser, or are you choosing a different WebKit wrapper (e.g. the current version of Chrome on iOS)?

[hanshenning]

> To reflect the DMA’s changes, developers will be able to use alternative browser engines — other than WebKit — for dedicated browser apps and apps providing in-app browsing experiences in the EU.

https://developer.apple.com/support/dma-and-apps-in-the-eu/#...

[wlesieutre]

So now European users could be using Firefox with mobile gecko engine, but no one in the US will ever test with that because they're not allowed to have it. Fun!

[ckcheng]

> actually choose a different browser, or are you choosing a different WebKit wrapper

I understand the "WebKit wrapper" for iOS criticism and do want different rendering engines available (e.g. Firefox's) and yet...

The worse thing about Firefox for iOS is the wrapper part, not the lack of rendering engine choice part. The UI of Firefox on iOS is inconsistent and buggy, and syncing doesn't sync well, etc. I doubt using FF's own rendering engine instead of WebKit would help the situation, as it'd drain engineering resources away from making the "wrapper" more usable.

I've always used Firefox, on Mac, Linux, Windows, Android, everywhere I can, but I find myself using it less and less on iOS... and it's not because of the rendering engine!

But since this change for the DMA will allow FF to use its own rendering engine (in the EU), hopefully maybe it'll reenergize the development of FF and improve the "wrapper" part more - even for non EU users!

[jerbear4328]

Writing this on FF for iOS, the biggest reason I want to use the Firefox engine is for Firefox extensions. WebKit doesn't support extensions except the App Store ones in Safari, I want to use traditional extensions from AMO. Just let me use uBlock on my phone!

I do agree, the Firefox iOS UI is clunky, but I find it useful for stuff where I want to sync passwords or tabs. I use Safari for browsing the web casually because it's nicer, and the feature of swiping between tabs is so convenient.

[pier25]

Nitpick but a browser engine is much more than the rendering engine.

[judge2020]

Per Macrumors:

> Apple is giving app developers in the EU access to NFC and allowing for alternative browser engines, so WebKit will not be required for third-party browser apps. Apps will be able to offer NFC payments without using Apple Pay or the Wallet app through Host Card Emulation. Apps can also access field detect, and a default app can be set to activate when an iPhone is placed near a terminal.

Although this only changes things for us developers. Regular users really don’t care what browser is running the web pages they’re looking at, everyone who downloads chrome does so to get their synced bookmarks and history.

https://www.macrumors.com/2024/01/25/ios-17-4-alternative-ap...

[addicted]

> Regular users really don’t care what browser is running the web pages they’re looking at, everyone who downloads chrome does so to get their synced bookmarks and history.

This is ahistorical. Regular users switched to Firefox and Chrome in droves from IE. And it wasn’t to sync their bookmarks. It was because they provided a much better experience.

If Blink or Gecko are able to provide a better experience than WebKit on iOS that would certainly prompt many users to switch to browsers using those engines.

[noqc]

Um, no. Regular users care about being able to run ublock origin.

[mvdtnz]

That's like claiming only mechanics are interested in what engine a car is running - regular users only care about the seat and steering wheel.

Regular users care about the experience of the browser. A superior rendering engine can potentially improve this experience.

[e_y_]

That's exactly what I predicted for NFC when Apple announced Apple Pay. Apple kept developers from using any of the NFC APIs until they were ready to roll out Apple Pay, and then only allowed non-payment NFC after that. It gave them 10 years to establish Apple Pay.

Being the system default was obviously very convenient for customers and there would be a very high bar for any other payment app to compete, but Apple wanted to make absolutely sure there was no possible competition.

[wiseowise]

> Regular users really don’t care what browser is running the web pages they’re looking at, everyone who downloads chrome does so to get their synced bookmarks and history.

As a regular user - I do.

[twism]

that's the case now but in the future you can now offer regular users features that currently only android chrome can do

[bhpm]

FTA:

The changes include more than 600 new APIs, expanded app analytics, functionality for alternative browser engines

[ladon86]

Ah, I clearly didn’t read it closely enough. Thank you!

[hjnilsson]

Well first version it will be different WebKit wrappers, as they are the only option available on iOS right now.

But they simultaneously open the door to other browser engines, so I imagine Firefox at least will release their app with a new browser engine down the line.

[insane_dreamer]

Wonderful; now devs have to support a plethora of browsers on iOS instead of just one -- the same shit-show as on the desktop.

[lacerrr]

they have to do that anyway, or did you forget all the non-iOS mobile users?

[pathartl]

I would imagine this doesn't open up the opportunity for other engines.

[ryaneager]

They state the exact opposite in the second sentence of the article. Please, at least read the opening paragraph before commenting.

[olliej]

So I'm guessing you didn't read the article then?

[sunnybeetroot]

No need to imagine, the answer is at the top of the article.

[andylynch]

It does, but on closer reading looks restricted to EU, they certainly aren’t suggesting a , say, gecko based browser could be published globally outside the EU.

[fredoralive]

"New frameworks and APIs for alternative browser engines — enabling developers to use browser engines, other than WebKit, for browser apps and apps with in-app browsing experiences."