* Vibration
* Background Sync
* Bluetooth
* NFC
* Notifications
* Web Push
A feature more devs should use- I've been surprised how much websites behave like native apps if you just "add to homescreen" instead of downloading an official app, e.g. twitter, instagram.
When you open the shortcut, it doesn't launch as a tab in safari, but appears independently in the app switcher. They are often indistinguishable from official apps!
Seems like a great way for devs to avoid app store pains
I can think of several light weight patch editors I’d like be able to use. There’s probably not enough demand for someone to make a stand alone app for them.
I can’t see any reason why this needs to be controlled by apple’s app store.
The alternative is to install random software on your computer for every device (or, if you're a Linux user, you'll likely simply be excluded and whine about it).
Just look at all the old hardware like CNC machines still running just fine on old computers, and imagine if they were connected via WebUSB instead.
WebUSB is just a terrible idea if you're not an ad company.
Not if it's an Open Source project made by a bunch of people for the love of the game. Install a PWA and you have it even when the site is down, if not code available on GH. It's possible to do on a computer (write code and distribute an app not via an app store)...but not in the magical protected-profits land of mobile devices.
Your way of thinking is the reason why we now have a half dozen trillion dollar companies controlling the world.
Things that should be removed, according to me:
* Audio recording
* Geolocation
* Motion
* Media capture
Complexity primarily.
But why not Bluetooth or NFC? I can’t imagine any way those could be annoyances, or even why websites would want them outside of some extremely specialized applications.
Similarly, if my bank website could do NFC tap-to-pay securely, that would be pretty cool. I can imagine lots of interesting opt-in uses for NFC in a webapp.
Arguments that these features are held back by Apple specifically in order to keep apps on the app store where they can control things and take 30% at least hold water, I think, even if that reasoning doesn't apply to Mozilla rejecting features.
I suspect like many here, at $work we use a shit-ton of Flexoptix SFPs.
Flexoptix are not a $megacorp, they are a (very) small German company.
They manage to ship cross-platform apps to flash the SFPs. So its really not that difficult.
I would think a web app would be more of a pain the the butt to maintain because you have to deal with CSS reactive UI etc.
An enormous amount of the cost of developing a lot of native apps is customizing the appearance and behavior, to match some slide deck mockup or to make it “on-brand” or whatever. It’s better for the user, and way cheaper, if you just… don’t do that. Hell a lot of common UI elements are easier in native than web if you just don’t try to customize them a ton (data-backed tables and list views and such are sooooo nice)
Chromium gives 0 sh*t about users' privacy, and just pump the APIs out for websites to track their users more easily.
And even then, where does one draw the line on "privacy"? Especially given that every other app on the user's phone is granted every permission under the sun and feeding on as much data as possible.
The core of the problem isn't supporting web bluetooth etc or not...the core of the problem is that dumbass humans will go "yes use all the permissions" because their hands are already shaking from tiktok withdrawal.