Anybody that thinks otherwise is hopeless naive, Steve Jobs himself envisioned a web app future as the future of technology; before Apple found out the gold mine that the app store became.
I think that's the hypothetical part, it's not reality. Safari continues to be a fully modern browser. It doesn't release new features quite as fast as Chrome, but it does generally adopt them.
If Apple were attempting to put a "stranglehold on innovations on the web", Safari's feature set would look very different. But that's not what's happening.
Like I said, Apple does lots of anticompetitive things. I'm not blind to what they do with the app store. I just don't think that the single browser engine policy is motivated by this, or has much effect on it, given how Apple does keep maintaining Safari as a modern browser.
The only reason Apple has banned alternative engines and continues to hold back on major web technologies is anticompetitive behaviour.
I'm torn on this honestly. Safari (particularly mobile Safari) is literally the only thing keeping the web from becoming Chrome-only. While I would love to see Safari-alternative engines on the iPhone, I fear that the "open web" in terms of browser compatibility is cooked the day that happens: Commercial web developers are supremely lazy and their product managers are, too. They will consider the web Chrome-only from that day forward and simply refuse to lift a finger for other browsers.
I think when IE6 died, on one hand it was a relief for web developers, who (very quickly) deleted all the code needed to maintain compatibility, but on the other hand, it made the web worse by bringing us closer to browser monopoly.
That's not true. It's not even available on most computers. IE was about Microsoft not following web standards and abusing its monopoly position; Safari is a minor browser by overall market share and is broadly standards-compliant.
> the fact that PWAs didn’t take off in the last decade js purely due to Safari.
So then why aren't PWA's super-popular on Windows and on Android? Since Safari doesn't affect those?
It's officially compliant but in practice there's a lot of buggy implementations in Safari and you'll spend lots of time on workarounds and debugging.
It's also the last non-evergreen browser being tied to the OS so it's the slowest to update, compounding that effect.
> So then why aren't PWA's super-popular on Windows and on Android? Since Safari doesn't affect those?
Personally I think that's because it's still not that convenient even on Android even if better.
IE had a lot of browser features which officially were there but in practice didn't fully work.
I had issues with forms, zIndex, SVGs, backgrounds and localStorage with Safari. All of which I consider basic browser features which should always work.
Of course it's not as bad as IE but Safari is clearly lagging very far behind Chrome and Firefox
Says who?
"Yes, PWAs have become popular on these platforms. I work for Microsoft on the Microsoft Store (app store on Windows) and I work with the Edge team, and I work on PWABuilder.com, which publishes PWAs to app stores. Some of the most popular apps in the Microsoft Store are PWAs: Netflix, TikTok, Adobe Creative Cloud, Disney+, and many others.
To view the list of PWAs in the Store, on a Windows box you can run ms-windows-store://assoc/?Tags=AppExtension-microsoft.store.edgePWA" - https://news.ycombinator.com/item?id=46457849
https://www.google.com/search?q=safari+is+the+new+ie
And Apple purposely will never implement lots of APIs that only their native apps allow (which other browsers implement), specifically to force many developers to create a native app to use these APIs, so that Apple can force the developer to give them a percentage of any purchases made through the app. They can't force a developer to give them a cut of purchases made through a web browser, which is why they purposely hobble the Safari browser engine and then force all other browsers to use this engine. If you can't see how bad this is, then you've been taken over by the reality distortion field.
It's spelled out in the DOJ lawsuit against apple, among many other anti-competitive practices.
Microsoft got sued and lost in an antitrust suit for bundling IE with Windows. Apple bundles Safari with iOS but forbids any other browser engine but their Safari engine. Can you imagine if Microsoft forbade any other browser from being installed on Windows? It's time Apple was brought to justice over their abusive anti-competitive practices.
Here's the whole DOJ suit against Apple:
https://www.justice.gov/archives/opa/media/1344546/dl?inline
>Hard disagree on safari being even in the same ballpark as IE;
It's a crap browser, and Apple implements things the way they want to, especially around touch interactions. So I have to have a real iPhone to debug problems with Apple's implementations. Safari fucking sucks, it just does, and your trolling comment doesn't disprove it.
>what’s your alternative, Google owns the entirety of the browser space?
I don't care if they do or if they don't. All I want is an alternative to Safari on iOS. Is that really so bad??
https://www.justice.gov/archives/opa/media/1344546/dl?inline
You'll still have to debug it. Even when other browsers are allowed, Safari isn't going away.
"Safari fucking sucks" isn't an argument that Apple is being anticompetitive. There are a bunch of things that suck about Chrome too. And Firefox as well. No product is perfect.
>There are a bunch of things that suck about Chrome too. And Firefox as well. No product is perfect.
Google doesn't prevent Apple from offering Safari for Android, Apple just wouldn't be able to make money offering it through Google's app store the same way they can extort iOS developers that sell anything through the native app.
"Chrome sucks too" is very subjective. I've never had a problem with it. I'm curious what you think sucks about Chrome. Firefox - well, I used to use it a while ago, but not so much anymore. I will fix bugs there and they are easy and free to fix. I can't say the same about Apple's Safari.
Apple used to make Safari for Windows, but it sucked so badly, and they figured they couldn't make any money from it, so they discontinued it. So they could definitely make Safari for other platforms, but they would rather force developers to buy an iPhone instead. Fuck that.
I'm sorry iPhone users, but you'll forever be second class citizens in my product sphere, and you can blame Apple for that, until they allow other browser engines.
I can’t help but wonder if your company’s leadership shares your level of disdain for your customers.
Yeah, if you want to test against Safari you need Apple hardware. If you can't be bothered to get some cheap secondhand Apple hardware for testing for your business, then that says more about the business decisions you're making. The idea that Apple ought to be obligated to make its browser available on other platforms seems pretty silly to me.
You sound like someone complaining they want to develop a Microsoft Word plugin on Linux, and they're upset Microsoft doesn't sell a Linux version of Office and that they have to get a copy of Windows. What do you expect? You develop and test on the platforms where your desired users are. If you can't accept that basic reality, then maybe you shouldn't be making software.
Then you simply are not paying attention.
There are thousands upon thousands of articles written about how Safari is the worst web browser.
https://www.google.com/search?q=safari+is+the+worst+browser
It's not idiosyncratic at all, it's a very mainstream, real thing. Just because you have your head in the sand does not mean it doesn't exist.
>If you can't be bothered to get some cheap secondhand Apple hardware for testing for your business, then that says more about the business decisions you're making.
I shouldn't have to spend any money for the privilege to debug Apple's crap browser.
>The idea that Apple ought to be obligated to make its browser available on other platforms seems pretty silly to me.
I never said they were obligated, only that they once did, and failed miserably, and couldn't monetize it, so they packed up and went home. They could, and once did have Safari on other platforms. Now they don't so fuck Apple, I don't care what they do or care about their users any more than Apple cares about developers.
>You sound like someone...
You sound like an Apple fanboi, and there seem to be many brainwashed similar to you in this comment section.
None of what you described is accurate, I only want Apple to allow other browser engines on iOS, and to not be anti-competitive assholes. That's it. And the DOJ thinks so too, so you're not in the right here defending Apple's tyranny.
>What do you expect? You develop and test on the platforms where your desired users are. If you can't accept that basic reality, then maybe you shouldn't be making software.
I expect Apple to be abusively anti-competitive and not block other browsers from using their own browser engines. Once they do that, then I will shut up about it. Until then, Apple are the assholes. Not me. Not other browser makers. Just Apple, and their apologists.
They generally are pretty caught up on features. They have webgpu, they support the web notifications API (once a PWA is installed), lots of stuff. My main gripe is that they make it too hard to install PWAs, but we're still waiting for an actual API for that. (Maybe in 2027? [0])
> And Apple purposely will never implement lots of APIs that only their native apps allow (which other browsers implement)
Can you give an example?
[0]: https://blogs.windows.com/msedgedev/2025/11/24/the-web-insta...
>Can you give an example?
Web Bluetooth, Web USB, Web NFC, Web Serial...
Of course Apple will uphold its usual charade to claim that it's about pRiVacy & sEcuRiTy to maintain plausible deniability. They could easily implement it and keep it disabled by default, such that users could make the conscious choice to enable it or keep it disabled. Any adequate analysis of Apple's behavior and motivations must mention Apple's conflict of interest, because Apple will be biased against technology that could diminish the value proposition of "native" apps which Apple has been taxing so unchallenged for all these years.
Chrome-only non-standards. Note that Firefox is against these, too.
> Any adequate analysis of Apple's behavior and motivations must mention Apple's conflict of interest
I've yet to see an adequate analysis that doesn't pretend that anything Chrome shits, sorry, ships is immediately a standard that must absolutely be implemented by everyone immediately.
Funny how you agree that Firefox opposes these non-standards, and how Google rushes things. And immediately turn around and basically say "no-no-no, Apple is to blame and Safari (and, by extension Firefox) must absolutely implement these non-standard features from Chrome".
The rest of demagoguery is irrelevant.
BTW literally the moment Firefox relented and implemented WebMIDI they had originally opposed, they immediately ran into tracking/fingerprinting attempts using WebMIDI that Chrome just couldn't care less about.
There is nothing "funny" about me acknowledging facts, that's what a reasonable person should always do, try it. What's not funny though, is how you're butchering and misrepresenting my arguments to such a gross degree. I've never stated that everybody "must implement these non-standard features from Chrome", instead I've made a much more nuanced argument about how Apple's conflict of interest is motivating them to reject entire feature sets for competing technology instead of helping to implement a safe standard, which is indicative of their bad faith motivations. That anti-competitive strategy has been essential for Apple in collecting billions in app taxes by systematically hobbling any competition before it can emerge.
>BTW literally the moment Firefox relented and implemented WebMIDI they had originally opposed, they immediately ran into tracking/fingerprinting attempts using WebMIDI that Chrome just couldn't care less about.
So? Just as native apps give users certain freedoms that can have problematic aspects, web apps should have _equal rights_ and be able to play on a level playing field. The choice and freedom should be the users' and not that of Apple's finance division. None of this gives Apple the right to uphold its anti-competitive strategy with its corporate double speak. And the fact that you're so hyperfocused on specifics while failing to grasp the broader argument, so you can cheerlead for Apple's anti-competitive behavior, is revealing a clear bias.
It literally is "everyone must immediately implement anything Chrome shits out". You don't even accept the fact that both Safari and Firefox team reject the entire premise on the same grounds.
Nope. "They must work on better standards for these features that Chrome ships".
> The choice and freedom should be the users' and not that of Apple's finance division.
Funny how in the paragraph you respond to I didn't mention Apple once.
> And the fact that you're so hyperfocused on specifics while failing to grasp the broader argument
There's no broader argument. You literally dismiss Firefox as irrelevant [1], assume that whatever Chrome ships is good, and assumes that Apple is both a bad actor driven entirely by money an must implement whatever Chrome comes up with (under the guise of "should work to implement a safe standard").
[1] Their position on these Chrome features is literally the same as Apple's https://mozilla.github.io/standards-positions/
It isn't factually and certainly not "literally" that. I've explicitly stated that the problem isn't the rejection of the specific implementation in its current form, but the wholesale refusal of features to deny rival technology equal rights, instead of helping to implement a safe standard. That is evidence of Apple's bad faith motivation to hobble competing technology in favor of their App Store tax funnel. You consistently refuse to understand this and resort to deflecting from and distorting that fact.
>There's no broader argument.
There is, it's the one you've been deflecting and distracting from, because it refutes your biased talking points completely.
>You literally dismiss Firefox as irrelevant [1][1] Their position on these Chrome features is literally the same as Apple's https://mozilla.github.io/standards-positions/
No I don't. You're literally making stuff up and ignoring the fact that I have actually even started my response with an acknowledgement of that point: "You're right that Firefox also opposes some of these specific implementations in its current form, and that Google often rushes features. However, that doesn't diminish Apple's conflict of interest at all, so sometimes their arguments happen to align with reality just as a broken clock is correct twice a day." https://news.ycombinator.com/item?id=46457938
>and assumes that Apple is both a bad actor driven entirely by money an must implement whatever Chrome comes up with
There is no such assumption, only the fact that Apple has a conflict of interest, which manifests itself in anti-competitive behavior, for which I've provided documented evidence. I've also never stated that they "must implement whatever Chrome comes up with", that's a gross misrepresentation, which you are stubbornly repeating, despite me having refuted it several times now. Your bias in this matter couldn't be more obvious, due to your dedication to distorting any evidence that refutes Apple's propaganda narrative, so you keep blindly repeating the same tired and old talking points despite evidence to the contrary.
Rule of the thumb is "nothing you say before 'but' matters". Apple's opposition to Chrome features is not just echoed by Mozilla. It is repeated almost verbatim.
And yet, you completely ignore all that, and go to say "well, Apple is bad, and conflict interest, so Apple must work on a better safe standard for these features". You don't even for a second assume that two of the three browser vendors oppose these features for the same reason. No. Chrome shipped them, so they absolutely must work to implement these features (in some form) because Apple bad or something.
> There is no such assumption,
"the wholesale refusal of features to deny rival technology equal rights, instead of helping to implement a safe standard." Yup. "Whatever Chrome ships must be implemented no matter the cost and despite any opposition for any reason".
> only the fact that Apple has a conflict of interest, which manifests itself in anti-competitive behavior
Which literally has nothing to do with Chrome-only non-standards. Chrome wants them. It's on Chrome to design and implement them safely. Neither Apple nor Mozilla owe them anything regardless of the amount of demagoguery around their decisions. Both Apple and Safari pointed out the issues they have across many discussions. Chrome didn't care.
Safari has multiple issues, that's true. None of them stem from refusing to support every shitty thing that Chrome vomits into the world and calls a standard.
Speaking of "denying rival technology equal rights". Do you know that WebSQL was implemented by Chrome and had approval from Safari, but got killed due to opposition from Mozilla? Did Mozilla "deny rival technology equal rights"? Or perhaps, just perhaps, they had valid concerns that lead to rethinking of the approach?
You can't even come up with proper rebuttal of Mozilla's and Apple's concerns (you don't even know about their concerns to begin with) beyond "but native apps" and diatribes about Apple.
BTW here's Mozilla relenting on just one of the hardware APIs: https://news.ycombinator.com/item?id=33995022 (sadly, the twitter account has been locked)/ Original quote: "Just a day after shipping an impl to Firefox Nightly, this is the first discovered case of WebMIDI-fingerprinting... Chrome still allows web developers to enumerate attached MIDI devices without user consent or even a notification, btw."
Apple has veto power over what becomes web standards now. If they didn't abuse that power, and also forbid other browser engines on iOS, then there wouldn't be a problem. They abuse their power in a way that hurts everyone but Apple, and the DOJ took notice.
You say Firefox doesn't implement the same APIs that Apple won't as proof of something, but Opera and other browsers do implement those APIs, so that really cancells out whatever argument you thought you had.
Back in the day, Microsoft invented XMLHTTPRequest, and if Apple had veto power over web standards back then, the web might still be "Web 1.0", hypothetically speaking.
But now Apple can block progress in web browsers now, and the DOJ will likely prove that they are abusing their position to the detriment of everyone that uses a web browser, so Apple can make a few more dollars from their app store.
It should not be so difficult for anyone to understand.
Yes
> but if it’s not that, then refusing to ever adopt those standards (or to provide their own alternatives) is either foolish NIH syndrome on Apple’s part or it’s greed.
Note that Firefox's position is literally exactly the same as Apple's on these Chrome-only features: https://mozilla.github.io/standards-positions/
Until Apple lets other browser engines on iOS, they are behaving like greedy tyrants.
Oh yes, you do. To the point of inventing contract clauses for Firefox.
It's just extremely unfortunate that Safari is now between a rock and a hard place (only because of Apple) as really they are the only web engine of note to withstand "whatever Chrome spits out is standard now"
But there's still all sorts of wonkiness they just makes Safari non viable. If you don't PWA install, your storage gets cleared alarmingly quickly. If you do install it's still cleared wicked fast. Notifications seem to have incredibly unreliable delivery issues and require PWA installs to work at all. The features are closer to parity than before but the base functionality is still sabotaged deeply. 'The user is secure' with Apple is amazing doublespeak (the second meaning being securely in Apple's pocket with no where to go).
It's worth noting that Interop participants meet and decide via unanimous consent what they are going to work on each year. The anti-trust case against Apple would be far stronger if they didn't show up & find some stuff to work on, to agree to. And with apologies as I break out the tin foil hat, showing up also gives them some leverage to shape what doesn't get worked on too.
>Can you give an example?
Web Bluetooth API, and lots of others. My product could use bluetooth but we're forced to work around Apple's Safari limitations and use Wifi instead, which drains the battery faster. We do not want to write a specific app for iOS (which costs us money to build and maintain), which then allows Apple to extort us for a percentage of sales through the app. Bluetooth would be the better option, but Wifi works although is a bit more cumbersome to deal with. So sorry Apple fans, you have to use wifi with our product because Apple reasons.
I am going to open a bottle of champagne when the DOJ finally forces Apple to allow other browsers on iOS.
https://www.justice.gov/archives/opa/media/1344546/dl?inline
Interop 2025 is a subset of web features, but Apple gets a veto on which features get included in each Interop round, and vetoes heavily. It doesn't reflect interoperability in general. Safari also consistently starts out the worst each year, and improves the slowest.
They don't support notifications correctly, they have a semi-broken implementation. Only a subset of sites will work, even though they'll work perfectly on Chrome or Firefox or even minor browsers. Even if you put the site on the homescreen.
Which is of course bullshit
--- start quote ---
The allegation that Safari is holding back web development by its lack of support for key features is not new, but it’s not true, either. Back fifteen years ago IE held back the web because web developers had to cater to its outdated technology stack. “Best viewed with IE” and all that. But do you ever see a “Best viewed with Safari” notice? No, you don’t. Another browser takes that special place in web developers’ hearts and minds.
...even though Chrome is not the standard, it’s treated as such by many web developers.
https://www.quirksmode.org/blog/archives/2021/08/breaking_th...
--- end quote ---
No, we do not want to write our own iOS app where Apple can then extort us for a percentage of any sales through the app, and we have to pay for the priviledge to develop that app, as well as buy Apple hardware to do so.
So instead we use Wifi, where we can maintain one single codebase - the web application, which works on both Android and iOS, but has to use Wifi. If Apple allowed Chrome to use its own browser engine, we would simply tell users to install Chrome to interact with our device. Then we don't have to pay Apple for anything, nor should we have to.
Apple purposely won't implement some APIs so they can force developers to create an app for their app store where they can collect money from any additional sales through the app. It's all spelled out in the DOJ suit, why won't you just read it??
https://www.justice.gov/archives/opa/media/1344546/dl?inline
Also, why would your company cut off its nose to spite its face? If using Bluetooth is a customer requirement (as opposed to merely a “nice to have”), why wouldn’t you go to the lengths to provide an app for them?
That seems like victim blaming. Apple is the tyrant here.
> If using Bluetooth is a customer requirement (as opposed to merely a “nice to have”), why wouldn’t you go to the lengths to provide an app for them?
Because then have to hire an iOS developer and pay for everything to develop an app, which Apple can then use to extort a percentage of sales for anything purchased through the app. Or I have to write the app myself, and I'm already working 18 hours a day. FUCK THAT. Not going to happen. Apple users will always be second class citizens to me as long as Apple treats other browsers like second class citizens and forbids other browser engines. Making an iOS app isn't a clear pathway to riches, so Apple users will just have to use a more clunky wifi experience. That's just the way it is.
DID YOU READ IT? Below are some of the relevant sections.
https://www.justice.gov/archives/opa/media/1344546/dl?inline
Rather than respond to competitive threats by offering lower smartphone prices to consumers or better monetization for developers, Apple would meet competitive threats by imposing a series of shapeshifting rules and restrictions in its App Store guidelines and developer agreements that would allow Apple to extract higher fees, thwart innovation, offer a less secure or degraded user experience, and throttle competitive alternatives. It has deployed this playbook across many technologies, products, and services, including super apps, text messaging, smartwatches, and digital wallets, among many others.
9. Apple suppresses such innovation through a web of contractual restrictions that it selectively enforces through its control of app distribution and its “app review” process, as well as by denying access to key points of connection between apps and the iPhone’s operating system (called Application Programming Interfaces or “APIs”). Apple can enforce these restrictions due to its position as an intermediary between product creators such as developers on the one hand and users on the other.
16. Apple wraps itself in a cloak of privacy, security, and consumer preferences to justify its anticompetitive conduct. Indeed, it spends billions on marketing and branding to promote the self-serving premise that only Apple can safeguard consumers’ privacy and security interests. Apple selectively compromises privacy and security interests when doing so is in Apple’s own financial interest—such as degrading the security of text messages, offering governments and certain companies the chance to access more private and secure versions of app stores, or accepting billions of dollars each year for choosing Google as its default search engine when more private options are available. In the end, Apple deploys privacy and security justifications as an elastic shield that can stretch or contract to serve Apple’s financial and business interests.
43. Developers cannot avoid Apple’s control of app distribution and app creation by making web apps—apps created using standard programming languages for web-based content and available over the internet—as an alternative to native apps. Many iPhone users do not look for or know how to find web apps, causing web apps to constitute only a small fraction of app usage. Apple recognizes that web apps are not a good alternative to native apps for developers. As one Apple executive acknowledged, “[d]evelopers can’t make much money on the web.” Regardless, Apple can still control the functionality of web apps because Apple requires all web browsers on the iPhone to use WebKit, Apple’s browser engine—the key software components that third-party browsers use to display web content.
60. For years, Apple denied its users access to super apps because it viewed them as “fundamentally disruptive” to “existing app distribution and development paradigms” and ultimately Apple’s monopoly power. Apple feared super apps because it recognized that as they become popular, “demand for iPhone is reduced.” So, Apple used its control over app distribution and app creation to effectively prohibit developers from offering super apps instead of competing on the merits.
We’re done.
So then why doesn't Firefox support the Web Bluetooth API either? How can you jump to the conclusion that the lack of Safari support is about apps?
The reality is that the Web Bluetooth API is a draft. Not ratified. Not on the formal standards track. And Firefox doesn't even intend to implement it, due to security and privacy concerns around it and the fact that is it not ratified.
But go on assuming it's all about being anticompetitive...
> It's all spelled out in the DOJ suit, why won't you just read it?
I just did a Ctrl+F for Bluetooth and everything relates to smartwatches, not web APIs. There are only two references to Safari, none of which say anything about standards. The phrase "web standard" appears nowhere. The document is 88 pages long, and it's not immediately obvious to me where any of what you're talking about is spelled out. I hope you'll understand I'm not going to spend my afternoon reading the whole thing.
>Not on the formal standards track.
What a coincidence, Apple gets to vote on what the "formal standards track" is, and they have voted against anything that would hurt their app business.
>But go on assuming it's all about being anticompetitive...
Okay... Apple are anticompetitive and always have been. They forbid their OS from being installed on any hardware that isn't manufactured by Apple, even though it was easily possible to do. Their walled garden is very famous for being anticompetitive - banning any browser from using their own browser engine and forcing Safari is absolutely anti-competitive.
You know what? Just go fucking read the DOJ antitrust suit against Apple, it details the very many ways Apple is anti-competitive:
https://www.justice.gov/archives/opa/media/1344546/dl?inline
But I bet you won't.
But that's not what the conversation is about. I pointed out that in this area, it doesn't appear to be.
So I don't know why you keep pushing this PDF. It doesn't say anything about this specific area. I already checked.
And if you don't care about what Firefox does, then I think it's clear you're not having this conversation in good faith. You're not open to evidence or counter-argument, you just have a knee-jerk reaction that Apple is bad. OK, you do you. But I'm not going to waste any more time with someone who "doesn't care" about the most obvious counterpoint to their argument.
You mean that Chrome is the new IE
> Steve Jobs himself envisioned a
> web app future as the future of[...]
His remarks at the time of the initial iPhone release (with the benefit of hindsight) were clearly because they weren't ready to expose any sort of native API's.
Pissing on you and telling you it's raining was typical Jobs reality distortion field marketing, and not an indication that he actually believed it was raining.
This is inappropriate. People can reasonably disagree without being insulting to each other.
If you have concrete evidence that Apple is deliberately withholding some essential advancement in Safari or its support for Web standards so that it can sell more apps, by all means, cite it.
Just read the summary that Gemini provides for a good quick understanding, and follow up the multiple articles about it. Then please don't come back and say that there is nothing concrete about this evidence, that is just people speculating about a behavior that Apple has been engaging repeatedly and continuously for over a decade.
You claim to know something with certainty, so one can reasonably expect you have the expertise and data to prove it. If you come to the kitchen claiming to be a chef, you’d better come with sharp knives, not photos of them.