Remix.run Logo
▲ leptons a day ago

It's all of that, and also worse than that.

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.

▲ a day ago | parent | next [-]
[deleted]
▲486sx33 a day ago | parent | prev | next [-]

[dead]

▲paulryanrogers a day ago | parent | prev [-]

Must W3C proposals be unanimously accepted?

It seems odd the world is letting one company hold our hand behind our backs.

▲modeless a day ago | parent | next [-]

If it doesn't work on iOS it doesn't matter how standard it is or many other browsers implement it, because as a developer you can't rely on it. That's a big reason why Apple wants to keep their browser engine monopoly on iOS, to have veto power over standards.

▲leptons a day ago | parent | prev | next [-]

Firefox follows Apple on most things Apple wants to block. But again, instead of providing any feedback or proposing any changes, they just let these proposals die in committee. I would not doubt that someday we find out Apple has been somehow forcing Firefox to do this. There is simply no good reason to block WebBluetooth, WebSerial, or any of the many other APIs that would benefit developers and users. And no, it isn't a security issue, and no it isn't a privacy issue, as these APIs work the same way existing APIs work with regards to security and privacy - they are strictly opt-in per-website, just like the microphone and camera APIs are done now.

The only reasons I see Firefox blocking it is 1) Apple is paying them, 2) Firefox just doesn't have the resources to implement them. I'm leaning towards option 1, because Firefox shouldn't care what other browser makers have the resources to implement as long as the API proposals are sound (and they are sound).

Edit: If you're going to downvote, at least provide a comment as to why I'm wrong about any of this. Provide some evidence that counter my statements. I admit I stated opinions, not facts.

▲rstat1 a day ago | parent [-]

WebBluetooth and WebSerial shouldn't be a thing anyway, websites don't need access to serial ports or bluetooth

▲PaulHoule an hour ago | parent | next [-]

I write biofeedback applications in React that can access Bluetooth heart rate monitors as well as serial respiration and GSR monitors and such. It is pretty simple to draw graphs, display scores, make sounds. And the same application can run on desktop and mobile without a lot of hassle because there are safari-based browsers in the App Store that support the Bluetooth API.

So it is totally useful, I can experiment with and deploy applications and not have to pay to get into the platform and deal with App Store bullshit, I just post my files to the web when I want to update.

I’d argue overall it would be difficult to make applications with a better UI outside web technology, everything else looks like Motif in comparison. There is a reason why there are so many Electron crapplets.

▲Rohansi 21 hours ago | parent | prev | next [-]

Perfectly fine for you to think that. However, you could simply not allow websites to access WebBluetooth and WebSerial instead of supporting browser vendors that refuse to support the features entirely. Both already require you to allow access.

▲leptons a day ago | parent | prev [-]

>WebBluetooth and WebSerial shouldn't be a thing anyway, websites don't need access to serial ports or bluetooth

What kind of thought process did you use to arrive at this conclusion? It's really not very well reasoned, honestly.

There have already been several great projects that use these APIs. You thinking they don't matter is nonsense, because many people know that web browsers do benefit from these APIs, and I have many uses for them myself.

These APIs allow me to avoid Apple's App Store, and being forced to buy Apple desktop and mobile devices just to develop an iOS app where they can then extract even more money from me through the app. So Apple users will just have to suffer instead, because I refuse to give Apple that kind of money.

I need Web Bluetooth to communicate with my hardware device product. I don't want to have to pay Apple for the privilege to use bluetooth when it works perfectly fine in a web browser that isn't intentionally crippled.

▲djriley a day ago | parent [-]

WebSerial sounds like a really neat feature. I could see consumer 3d printing companies like Bambu using that to make 3-D printing from their model libraries dead simple, no need for the end user to even have a slicer. And for the hobbyist it makes all sort of cool web apps possible. There's all sorts of devices that I could see a much better story for if that was possible. Both for the less and more technical user.

▲leptons 13 hours ago | parent [-]

WebUSB is even more interesting. There's been several projects that "rescue" old hardware where the drivers are no longer viable on modern OS, and instead the browser can now support the older hardware.

https://medium.com/@larsgk/web-enabling-legacy-devices-dc3ec...

https://news.e-ink.me/en/archive/2026-04-07/article/rescuing...

https://yes-we-scan.app/details

Not that iOS needs this, but Apple is just holding back innovation. They won't even make recommendations for any changes to get their approval for these browser APIs.

▲Analemma_ 7 hours ago | parent | prev [-]

Of course not: Google adds web features without W3C consensus all the time. And then Hacker News bitches about that too.