If keeping a monopoly alive in a small part of the technological world prevents a monopoly for everything, it's worth doing so.
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?
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.
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.
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 not connected to Google or Apple calendar. It has an MCP so Claude can schedule tasks for me, workout session, LinkedIn posts, etc.
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.
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"
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.
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.
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.
https://en.wikipedia.org/wiki/United_States_v._Microsoft_Cor....
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"
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.
Yet…
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.
https://www.gov.uk/government/publications/mobile-ecosystems...
and this org is doing the most and best work to force Apple to change. Please support them: https://open-web-advocacy.org
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
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.
> …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.
For others, here's the real truth of the matter: https://infrequently.org/series/browser-choice-must-matter/
> 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.
Here's our most recent exchange https://news.ycombinator.com/item?id=49727868
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.
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?
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.
So.. Yes. More hoops to jump over, less competition, bigger market share, profit.
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.
Safari is as bad at PWAs on iOS as Firefox is for PWAs on Android. https://pwascore.com/
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.
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?
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.
You need to be up-to-date if you're going to spew bullshit. Ask the AI first.
- 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 on BrowserEngineKit nor following the safe programming guidelines Apple enforces for them to be distributable (and get JIT support on the store basically).
This is insane. Basically if you have a cool project you want to show progress and build hype around, you're not allowed to. Apple knows exactly how deadly this is
- something similar to ADB
- profiles like graphine OS
- ability to remove the bloatware apps (music, books, etc..)
- real firefox with real adblock extension
I think a lot of google users would jump ship.
I'm confused about this part. Is there some sort of code signing requirement that wouldn't be available to the "original" Firefox iOS app?
The sentence after that explains what they mean. They would have to migrate users from the Firefox WebKit SKU to the Firefox Gecko SKU in the EU and migrate all the data from one SKU to the other, essentially a full browser migration.
Not enough people care → the economics doesn't make sense → Mozilla doesn't care. This is "why there are still no non-WebKit browsers on iOS."
But, is there a genuine ‘non-asshole’ reason for these continued Apple restrictions post the EU regulations?
I find it hard to believe.
[1]: https://developer.apple.com/support/alternative-browser-engi...
Apple already lost in Europe and must now allow other browser engines to be installed on iOS by European users.
A recent project of mine is web app only, and works great on iOS and Android as an installed web app, exactly the same way. Whether Firefox is running WebKit or not, web apps are a thing on iOS already, so that's not even relevant to this discussion at all.
You can theoretically ship a new default browser that implements more Javascript APIs. There's no way to use that to render web sites added to the home screen though. And they routinely ban browsers that add more APIs for sites.
Because they maintain true ownership, they can and do dictate all terms of usage of their devices. And that means 'no unapproved browsers'.
They are better classified as indefinite rentals, and not 'sales'
And hey, don't downvote me, I'm seriously just a messenger here.
This includes a long list of strict requirements, some of which are hypocritical because Apple itself doesn't follow them, e.g., "Prioritize resolving reported vulnerabilities with expedience, over new feature development" and "Most vulnerabilities should be resolved in 30 days".
One requirement that Mozilla mentions in their blog post: "Not sync any state (including cookies) between the Alternative Web Browser Engine App (EU) and any other app, even another app of the same developer, unless the user has explicitly given permission for state to be synced, either by signing into both the Alternative Web Browser Engine App (EU) and the other app, or through another mechanism of providing explicit permission"
> Use memory-safe programming languages, or features that improve memory safety within other languages, within the alternative web browser engine at a minimum for all code that processes web content;
This doesn't seem like a reasonable requirement. Webkit probably doesn't satisfy it.
If privacy and user control are hurdles for you, then your software will not make its way onto my hardware.
1. The user already has WebKit Firefox installed on their iPhone, with bookmarks, passwords, history, etc.
2. Apple requires that the non-WebKit Firefox be a separate app, available only in the EU and Japan.
3. If the user wants to switch from WebKit Firefox to non-WebKit Firefox, the user loses their bookmarks, passwords, history, etc.
In contrast, when the WebKit Firefox simply releases an update in the App Store, the user data is retained. Thus, Apple is making it extremely difficult for Firefox to switch from WebKit to non-WebKit.
In general, Apple does allow iOS apps by the same developer to share data, so this restriction for non-WebKit browsers is totally arbitrary. "App groups allow multiple apps produced by a single development team to access shared containers and keychain access groups, and communicate using interprocess communication (IPC)." https://developer.apple.com/documentation/bundleresources/en...
The way you phrase it, you make it sound like Mozilla doesn't care about privacy or user control. That's not the situation here. Also, I notice that your HN account was created less than a hour ago seemingly for the sole purpose of making this comment, which is strange.
Btw, i stand with Mozilla on the overall issue here, Firefox should be permitted as is, in the official app stores, unencumbered by any artificial limitations nor having to jump over arbitrary complicated hoops. I'd also add, it is a reason for why i still don't buy an iPad, because i'd like to have the same browser than on my desktop os, Firefox, and not a reduced version, ie. its full proper implementation.
This isn't really meaningful for Mozilla, though.
I do want an iPad. I like the fact that I can visit my hospital and my bank's websites on it.
I think if Chrome or Firefox were possible to be installed, then the bank and the hospital would eventually target chrome-only, thinking it would save them time or money.
Can you understand, for your mere preference, you might literally cause me and people like me harm?
It is completely bonkers.
Apple is smart enough to just allow this world wide AND still make huge profits.