21–30 of 101 posts
Earlier quoted context omitted.
Why would they belong in a platform-specific app but not in a standard-based web app? Because Apple can't get 30% out of it?
Because there's typically at least a minimum of safety checks before an app can go into the app store, whereas a website can do whatever it wants (and can).
Earlier quoted context omitted.
Me too. Device orientation, USB, Bluetooth, vibration, they don't belong in a web app.
Why would they belong in a platform-specific app but not in a standard-based web app? Because Apple can't get 30% out of it?
Rich companies such as Epic, complaining about a 30% cut can cry me a river. Lock iOS down as much as possible and restrict/sandbox the web.
iOS is the only internet connected computer I’ve had that didn’t get malware and/or a virus at some point. Unless you consider an Xbox/PlayStation a computer.
https://medium.com/online-io-blockchain-technologies/the-evo...
This is a good example of how the chromium monoculture hurts the web. It ends up being Google's way or highway.
EDIT: You can filter by features that both Firefox and Chrome support by tapping the Chrome icon. This takes the list from 63 entries to 29
[flagged]
Like it or not, W3C standards have always been reactive to what browsers are already doing.
And what's really remarkable about this list is that quite a few are supported on Safari on Mac, just not on iOS. Like autofocus. It's just a simple attribute you can put on an tag that autofocuses that element when the page loads. It's on Mac Safari. It's on Android browsers. It's just not on any iOS browser because, you have to assume, someone at Apple held it back for not very good reasons.
so basically if an app can be ported as a web app, safari in ios won't support it? seems.....convenient
Should iOS adopt [feature] because Chrome has it, or why else is it on the list? What benefits am I missing as a user?
As a mainly desktop Firefox user, any time I have a web bug my developer colleagues asks me to try Chrome instead because they only develop and test in Chrome. I would say if we care about standards and an open web we should not cater so much to Chrome's whims and wishes…
Looks awesome! While the visualization is cool, I hope some of these will remain "not found" indefinitely. Just because we can stick everything into a web-spec, doesn't mean we should.
Me too. Device orientation, USB, Bluetooth, vibration, they don't belong in a web app.
[flagged]
That's more or less how HTML has always been. Before Chrome, it was IE just adding stuff. Before IE, it was Netscape just adding stuff. JavaScript itself is just a browser adding stuff. Like it or not, W3C standards have always been reactive to what browsers are already doing. And what's really remarkable about this list is that quite a few are supported on Safari on Mac, just not on iOS. Like autofocus. It's just a…