Specifically for me, my company has a product that could use Bluetooth, but Safari will never implement the Web Bluetooth API, where Chrome has for some time on Android. So the workaround is to use Wifi instead (my product supports both bluetooth and Wifi), which drains the phone battery faster.
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??
> 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.
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.
I don't really care what Firefox does. They get paid massively by Google, so who knows what their motivations are for what they do. Opera implements the same APIs in their browser, but that also doesn't work on iOS because Apple are dicks and force Safari on Opera too.
>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:
You seem to have lost the plot here. I started out by saying Apple is anticompetitive in plenty of areas.
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.
Unfortunately, many people here don’t enter the arena with open minds. Their opinions have congealed; there are good guys and bad guys; and they just want to rant and complain. They don’t want any solutions other than their preferred one.
What the hell? This is a completely unacceptable comment on HN. This is a discussion about Apple and browser engines. We've had to ask you before to observe the guidelines, and we have to ban accounts that continue to post abusive comments. HN is only a place where people want to participate because others make the effort to raise the standards rather than dragging them down. Please start acting like you want this to continue to be a place for worthwhile discussions.
It’s not alleged in the complaint that Apple cripples Safari in order to incentivize developers to build apps instead. Respectfully, did you read it?
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?
>Also, why would your company cut off its nose to spite its face?
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.
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.
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