Back at the release in 2007, web apps were the original way to build for the iPhone until Apple got the App Store working. Apps became king because of the 30% cut.
And
https://open-web-advocacy.org/walled-gardens-report/#evidenc...
Make sure you tap more comments to see the examples.
The number one issue for building native like apps is this https://github.com/web-platform-tests/interop/issues/84
It has been buggy for as long as I can remember and never been fixed.
Not to mention the 10 years of issues with indexeddb or the issues with WebRTC.
The site does throw in a few legitimate complaints (like IndexedDB), but otherwise it's poor quality.
We're like 15 years from the original iPhone launch. I was going through reading about every web API on MDN [1]. I was wondering what you could accomplish now that many of the apis are now reasonably stable. Looks like I'm in for some frustration. Glad to learn about open web advocacy initiative today, mtomweb.
Many of those "stable APIs" are non-standard and exist only in Chrome. Almost every one that is listed as "experimental" on that page are one or more of:
- only exist as a scribble on a napkin. Example "Barcode Detection API" which is literally, and I quote, "not a W3C Standard nor is it on the W3C Standards Track" https://wicg.github.io/shape-detection-api/
- are in the process of gathering requirements or trying to reach consensus
- will not ever be implemented by either Firefox or Safari in the current state of the spec. Example: most of the hardware APIs (Bluetooth, HID, Serial etc., considered harmful and will not implement by both Mozilla and Safari)
However, almost every single one of these are being shipped by Chrome.
Don't be fooled by mtomweb's "web advocacy". It's anything but.