Comment by TheDong
7 months ago
I agree with the point about non-EU web developers.
As long as people in the US can't test their web app on "firefox for iOS" without first buying a plane ticket to the EU and getting an EU sim card, all eu-only browser engines on iOS will be second-class citizens.
I think the next logical extension is that actually limiting general public use across the entire world makes apple less compliant with the DMA. Mozilla will not be able to justify putting significant effort into the iOS port as long as it can only reach a small fraction of users, so in reality the way to get browser-engine competition in the EU is to mandate that apple _not_ impose EU-specific rules about what apps can be installed.
Apparently, a faraday bag and an ESP32 is all that's needed to make an iOS device think it's in the EU.
I saw it posted on hn before. Apparently, you emulate some wifi APs that are geolocated to inside the EU and that's enough.
What a load of BS. How can I test my website on safari without owning Apple hardware? I can't so I don't.
You can run Gnome Web for free. It's the open source version of WebKit so you won't be able to see all the tweaks Apple adds to their proprietary build, but it's close enough that obvious differences are visible, at least on desktop.
Safari on iOS cannot be tested without paying Apple so I generally don't for my personal stuff either.
All of that said, American developers often can't even be bothered to support characters like ñ or é, so I think it's quite reasonable to expect an EU browser to be a second class citizen for American developers. We can work around that pretty easily by simply not buying products and services that don't work well in the EU.
Right, but approximately zero people have ever said "this website doesn't work on Firefox, so I won't use this website". They say "this website doesn't work on Firefox, so I won't use Firefox".
13 replies →
I develop on Firefox and it works on Chrome and Safari with no issues on all OSes (Windows, Mac and Linux). In the extremely rare case when there are some platform specific issues customers tunnel to my dev machine and check the web app (it's Vue) with their iPhones or Macs. I remember only two issues in about 3 years with this customer, all of them with the Apple ecosystem:
1. A form that could not find anymore a picture when they selected it from the Mac Photos app. Apparently Photos creates a temporary file that disappears before the browser submits the form, when probably reads it again from disk. No problems when the picture is loaded from a normal folder. We should read the picture into the memory of the browser and add it to the form from there, of transition to a JSON request. My customer decided that it's a niche case and it's not worth working on it.
2. A slight misalignment of an arrow and a checkbox, but that also happens in a different way with Chrome and Firefox, so there is some structural bug in the DOM/CSS of those UI elements. We're working on that.
Except those issues I can't remember any cross browser or cross OS problems in the last years. If it works in Firefox it works in Chrome and Safari too.
> How can I test my website on safari without owning Apple hardware?
Arduously?
Check this very surprising thing out:
https://github.com/WebKitForWindows/WebKitRequirements/relea...
This is how Playwright has a webkit engine. An old discussion:
https://schepp.dev/posts/running-webkit-on-windows/
And this visual engine rendering compare tool leverages it:
https://github.com/niutech/splitbrowser
Separately, not sure if/when this will be a real thing for Linux:
https://www.omgubuntu.co.uk/2025/03/kag-orion-web-browser-co...
I mean, ideally you can choose to _not_ do so, tell your users "We only support Firefox and Chrome on iOS, and not Safari, because we do not own apple hardware", and then report bugs to mozilla/chrome if iOS users report differences.
Being able to run cross-platform browsers on iOS does in fact make the very thing you're complaining about better.
I would love it if the EU did in fact force apple to release a cross-platform iOS emulator to allow web developers to properly test iOS browsers, but presumably apple would argue that there are strong technical reasons there (and the DMA differentiates real technical reasons from monopolistic arbitrary roadblocks).
For making browsers available across regions, that's very obviously not driven by strong technical reasons. Making cross-platform code has real technical burden.
I've worked at a company that did this. We didn't have Apple hardware (except for a very old Mac that took forever to boot). Chrome was promised, Firefox was often tested, Safari was unsupported.
Customers bought Samsung tablets to use our SaaS product. If you're in the right area of business, you can just ignore Safari.
> but presumably apple would argue that there are strong technical reasons there
They already have to make the appropriate iOS simulators and firmware for European developers. Making that available to American developers costs them nothing extra. They just don't want to.
> tell your users "We only support Firefox and Chrome on iOS, and not Safari, because we do not own apple hardware"
I'd be pissed if someone did that for my browser engine of choice. Also, from what I understand, Apple still leads in accessibility, so this would be an asshole move towards consumers stuck in that ecosystem just because Google and Microsoft can't get their act together.
2 replies →
> and then report bugs to mozilla/chrome if iOS users report differences.
A very unreasonable expectation.
Not the most practical but you can rent a macOS VM.
Browserling has a usable free trial. They have a finite number of VMs dedicated to the trial, so sometimes it takes a while to get to the front of the queue, but it's been good enough when I've needed it. https://www.browserling.com/
A hobby dev will not do such thing.
7 replies →
Go to an Apple store or use a friend's hardware.
No thanks. If apple wants others to care about their browser its up to them to make it reasonably easy to test.
It’s relatively easy to own Apple hardware when one lives outside the EU, but basically impossible to use that hardware to run their own browser engine on iPhones or iPads.
> How can I test my website on safari without owning Apple hardware?
Download the windows version from their website?
If Apple doesn't want to make their browser available for other hardware that's on them and they'll suffer the consequences. Blocking other entities from making their browser available on Apple's hardware is very different.
What's the point in testing on a browser that hasn't been updated in 15 years, even if you bother to set up a VM specifically for it (since every other browser works on all three OSes)?
https://en.wikipedia.org/wiki/Safari_(web_browser)#Windows
1 reply →
I remember Safari for Windows. It had a Mac chrome that was extremely weird to look at on Windows XP. It did work but Apple killed it after a short while, maybe because they decided that after all the iPhone was not going to use web apps Apple could not cash on, but native apps Apple could get their 30% from the store.
And it can’t just be the woefully insufficient TestFlight 10k users because there are possible upwards of a million developers who need to test their websites/web apps in the EU.
> As long as people in the US can't test their web app on "firefox for iOS" without first buying a plane ticket to the EU and getting an EU sim card, all eu-only browser engines on iOS will be second-class citizens.
VM is EU. Heck, it can be an ephemeral instance on EC2, so it would only cost money while in use, probably tens of cents or something.
If there's a will, there's a way.
Remote debug on iOS is ass unless you are fully invested into their ecosystem.
And apple has some "nice" licencing nonsense around their software that makes VMs not the "obvious" solution.
Ah, that was silly from me, I forgot about those shenanigans.
I have a bit of experience with cloud mobile simulators (like Appetize). Ignoring the question of whether their simulators have EU builds that allow running alternative browser engines, the experience simply sucks for developing interactive apps.
You can't develop an app if you aren't able to test it like a real user would use it on a real device.
Testing mobile interactions such as scrolling and swiping, as well as animations' performance cannot be done through a VM.
Only real devices allow to test these aspects properly.