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.
Chrome isn't forcing web standards. Chrome is forcing Google's own APIs, and calling them Web Standards
Consider that if the web was created today, it would never be allowed to run on iOS. The next web-like thing won't be allowed run on iOS without new lawsuits.
https://www.gov.uk/government/publications/mobile-ecosystems...
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.
Yet…
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"
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.
https://en.wikipedia.org/wiki/United_States_v._Microsoft_Cor....
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.
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.
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.
If I can't replicate that on iOS then it's not "just fine," imo, and I presume that's the GP's point. If I can't do that, the "bullshit" is the claim that adblocking works on iOS.
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.
Safari is as bad at PWAs on iOS as Firefox is for PWAs on Android. https://pwascore.com/
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?
> …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.
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?
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.
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"
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.
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.
It seems odd the world is letting one company hold our hand behind our backs.
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?
There are all kinds of small issues. For example, we can't do HDR on iOS for photos in the browser because WebGPU doesn't support it.
The sheer quantity of old school Flash's exploits were a recent memory when the policy was set.
and this org is doing the most and best work to force Apple to change. Please support them: https://open-web-advocacy.org
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.