It's tough to get developers to care about things like offline-first, because it's tough for them to convince managers to allow them to spend time on a feature that won't work on iOS (since it won't work in Safari, and Apple has banned other browser engines on their platform).
Ultimately it's users that lose out but also the web as a platform, as it pushes people, like the author of the article, towards walled-garden solutions like native apps.
Apple is looking for service worker use-cases, so if it's something you're interested in, let them know https://lists.webkit.org/pipermail/webkit-dev/2017-July/0292....
When the iPod came out, I never understood why I couldn't just drag the music files directly onto the device and I had to get iTunes and use iTune's tedious interface.
Now they have the app store; another unnecessary restriction. As a developer, it's nice to own an Android phone because I can just run whatever code I want on it and I don't need to buy any special licenses, hardware or proprietary SDKs to do that.
I understand where you're coming from, I do. But when it comes to a phone, I greatly prefer the standardized hardware/interface/OS over the free for all. I hate to use the "it just works" nonsense, but that is exactly what it does.
Working in the Enterprise, the iPhone is infinitely easier for us to troubleshoot, and manage. Because everyone is running the same thing.
This is a non-sequitur. Fragmentation of Android OS versions isn't caused by Android letting you use web apps.