Why there are still no non-WebKit browsers on iOS
1 comment
- Points375
- Comments221
1 comment
Story details from Hacker News ↗ · linked article on blog.mozilla.org.
Why there are still no non-WebKit browsers on iOS was first seen on Hacker News · Front page on Nov 20, 2026. Since then it has appeared in 73 checks on 3 different days. Its best position was #8 of 30, reached on Nov 20, 16:14 UTC. It dropped off the list after Nov 22, 07:44 UTC.
Position on Hacker News · Front page at every check (lower is better).
Best rank per day (UTC).
Platform metric as reported by Hacker News.
A few top-level comments from Hacker News, shortened. Read the full thread on Hacker News.
You also cannot work on this outside of Europe. Developers have to use VPN or special networks to make iOS think they are in Europe. Otherwise you cannot build and run with a custom engine. It is completely bonkers. Apple is smart enough to just allow this world wide AND still make huge profits.
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.
There are non-WebKit browsers on iOS but they don't qualify for notarization: - Reynard: Gecko-based, iOS 13+, extension support https://github.com/minh-ton/reynard-browser - Blinker-Fluid: Chromium-based, iOS 12+, content blocker https://github.com/Nodesclock/Blinker-fluid I am guessing neither of them are relying…
Archived daily, weekly and monthly lists that include this entry.
Not at the moment. It was last on the list on Nov 22, 07:44 UTC, after 3 days of trending.
#8 on Hacker News · Front page, on Nov 20, 16:14 UTC. Trendoday checks this list every 15 minutes.
It was first seen on Nov 20, 2026 and has been on the list on 3 days (73 checks) since.
375 points and 221 comments; submitted by lapcat on Nov 20, 2026.