4 ms·

I literally started a deep dive into the current state of progressive web app support on iOS this week. WebKit does seem limited on many html apis, but I haven

I literally started a deep dive into the current state of progressive web app support on iOS this week. WebKit does seem limited on many html apis, but I haven’t seen the bugs this article mentions, yet. 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.

mtomweb 4y ago
For bugs see: https://open-web-advocacy.org/walled-gardens-report/#ios-safari-is-buggy https://open-web-advocacy.org/walled-gardens-report/#ios-saf... And https://open-web-advocacy.org/walled-gardens-report/#evidence-of-long-term-neglect-and-developer-discontent 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 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.
- dmitriid 4y ago
  For bugs don't see "open advocacy" site. Because a lot of it a poorly rebranded Chrome propaganda. For example, decrying lack of support for device/hardware APIs which are all Chrome-only non-standards that both Apple and Mozilla will never support. The site does throw in a few legitimate complaints (like IndexedDB), but otherwise it's poor quality.
duxup 4y ago
I think it is worth noting that web apps in 2007 weren’t up to the task…
- mtomweb 4y ago
  True. Or even 2010
  - pfarrell 4y ago
    Exactly, for both time periods. In 2007, it was probably because Apple wasn't ready for the demand to create apps, see John Gruber's complaints from his notes on the launch [0]. By 2010, the money was too good to invest in webapps. 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. 0: https://daringfireball.net/2007/06/wwdc_2007_keynote https://daringfireball.net/2007/06/wwdc_2007_keynote 1: https://developer.mozilla.org/en-US/docs/Web/API https://developer.mozilla.org/en-US/docs/Web/API
    - dmitriid 4y ago
      > I was wondering what you could accomplish now that many of the apis are now reasonably stable. 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/ 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.
  - d12bb 4y ago
    Or even 2022.
    - duxup 4y ago
      It’s doable but as far as fully featured applications, PWAs that don’t just act like a website & offline support it isn’t easy.

mtomweb 4y ago

For bugs see: https://open-web-advocacy.org/walled-gardens-report/#ios-safari-is-buggy https://open-web-advocacy.org/walled-gardens-report/#ios-saf... And https://open-web-advocacy.org/walled-gardens-report/#evidence-of-long-term-neglect-and-developer-discontent 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 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.

dmitriid 4y ago
For bugs don't see "open advocacy" site. Because a lot of it a poorly rebranded Chrome propaganda. For example, decrying lack of support for device/hardware APIs which are all Chrome-only non-standards that both Apple and Mozilla will never support. The site does throw in a few legitimate complaints (like IndexedDB), but otherwise it's poor quality.

duxup 4y ago

I think it is worth noting that web apps in 2007 weren’t up to the task…

mtomweb 4y ago
True. Or even 2010
- pfarrell 4y ago
  Exactly, for both time periods. In 2007, it was probably because Apple wasn't ready for the demand to create apps, see John Gruber's complaints from his notes on the launch [0]. By 2010, the money was too good to invest in webapps. 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. 0: https://daringfireball.net/2007/06/wwdc_2007_keynote https://daringfireball.net/2007/06/wwdc_2007_keynote 1: https://developer.mozilla.org/en-US/docs/Web/API https://developer.mozilla.org/en-US/docs/Web/API
  - dmitriid 4y ago
    > I was wondering what you could accomplish now that many of the apis are now reasonably stable. 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/ 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.
- d12bb 4y ago
  Or even 2022.
  - duxup 4y ago
    It’s doable but as far as fully featured applications, PWAs that don’t just act like a website & offline support it isn’t easy.