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)?
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)?
https://developer.apple.com/support/dma-and-apps-in-the-eu/#...
Orion uses WebKit and has uBlock origin so I'm not so sure it's a limitation of WebKit itself.
Write enough code and you can make these extensions run on IE6. :P
Just get the Wipr Safari extension, haven’t seen an ad since I got it the year extensions were introduced.
As a result, I would expect Chrome/Firefox/Edge/Opera to ship their own browser engines on iOS but am doubtful that many other apps will embed Chromium/Gecko with the possible exception of apps that only operate in the EU.
Luckily I’m extremely close to having them inducted into the fruit cult just by having them play around on my dev iPhone when I’m not working. So fingers crossed it happens before get pushed over the edge.
As an aside: what kind of OS allows apps to create read-only contacts in the Contacts app, ffs…
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!
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.
Just to correct the common misconception. It is browser vendors that need to build web extension API support on top of WebKit. Orion browser [1] did this both for macOS and iOS . The support is still in beta and improving with each new release. iOS support remains limited to what is possible to achieve with a JS wrapper. Nothing prevents Firefox from doing the same and offer at least partial web extension support on iOS.
> 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...
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.
- fullscreen on iPhone
- WebBluetooth
- WebUSB
- WebMIDI
- WebSensor
- Web Push notifications - that are less limited than in current safari
- WASM simd
- WASM multithreading
- WebGPU
This will make PWA apps less crippled.
i know these guys https://fingerprint.com use so many of these when fingerprinting.
Regular users care about the experience of the browser. A superior rendering engine can potentially improve this experience.
That's probably true for quite a lot of people in those categories.
They want something that reliably gets them from A to B and back, with occasional side trips to C, D and E. They want something that does that in a way that matches their personal style. They want something that isn't going to cost them an arm and a leg to run.
Forty, fifty, and sixty years ago people cared a lot more. Starting really in the mid-90s, that changed. Nowadays, there are probably as many gearheads as there were decades ago, but as a population they represent a smaller percentage. And there's a tiny percentage of people who care only so that they can mod their engines to run less efficiently so they can pwn the libz.
Inasmuch as people do care about the 1.3 4 banger — they choose it because it generally runs more reliably over time with fewer litres burned per 100km.
> They want something that isn't going to cost them an arm and a leg to run.
Pick a lane.
Most people who buy cars don't actually give a shit how many cylinders, spark plug configuration, or hamsters are involved in the engine. They want to know that it will work and not cost them too much in fuel, maintenance, insurance, and repairs. They want it to "look good" for their sense of style, and they want it to be a "safe" car.
In order, it's usually price, style, then fuel efficiency (not engine, but whole car fuel efficiency), insurance cost, and everything else. For some people, it ends up being style, price, then everything else.
But if you are going to spend 10k$+ on a car, then you start caring, A LOT. I've seen the change from when I was a student willing to take any crap on wheel, vs when I had some money to burn on a car and I spent weeks looking at everything to end up buying a 10k$ 20yo Porsche 911 :D See, I didn't even look at the fuel cost: only the engine perf per dollars. And it cost me an arm and a leg to run, in Hong Kong where the fuel cost is the highest in the world !
People don't work as rational machines balancing perfectly cost and profit in a constant manner over time. It's more a constraint compromise game with a repressed desire for luxury that seem to drive us: you'll buy what you can afford and within those boundaries you will choose comfort and design over economic optimization. Like when people buy an iphone, evidently they didn't look at all about cost for performance and choose something economically suboptimal but luxurious.
Accept it and you'll start liking them more I think.
I did indicate that personal style comes into it, and I don't think that it's not an emotional decision. But there's a reason that Camry, Corolla, and Accord show up in bestselling car lists every year (and similar models elsewhere in the world), and it has nothing to do with "caring about what's under the bonnet".
There is a subset of people who do care about the engine, but they don't do so because they actually know a damned thing about how the engine runs, but because a big engine makes them feel powerful in their oversized pickemup trucks that never carry a load in the bed.
Your assertion that people who buy an iPhone aren't looking at cost for performance is partially correct, but only insofar as most (I mean > 99% of people including people in tech—including myself) wouldn't be able to objectively measure phone performance worth a damn. Anecdotally, I know a number of people who have switched from android devices to iPhones because they see their friends holding onto the same iPhones for years without complaints, yet they can't see the benefit of holding onto their android phones and realize that they may be spending a bit more up front, but are getting more possible useful years of phone updates than had been available in Android until promises made (and several years to see if they are kept) just few months ago.
Yes, I also know people who are enamoured of their Android devices and have their own smugness about what they think that they've gotten over the "sheeple" who buy Apple devices, but most people really don't give a shit about the phone operating system any more than they do about whether the engine in their car is 3, 4 or 6 cylinders (people who by v8s are intentionally buying a v8) or whether it happens to just be a family of hamsters running around underneath—as long as it runs.
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.
As a regular user - I do.
The changes include more than 600 new APIs, expanded app analytics, functionality for alternative browser engines
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.