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....
The overall vibes leaking from the Safari team on this matter have been arrogant, detached. I don't hold any hope.
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.
Because MTP is utter rubbish.
Really, people complain about iTunes? It's never failed me as slow as it is. Try using MTP...
The Stocks and Weather app were originally HTML/CSS/JS apps just like Dashboard widgets (note Steve Jobs actually describing these apps on stage as 'widgets'), but the performance just wasn't there so they got reimplented using native apis.
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.
I mean, the expected workflow is: I hook up the device to the computer, it shows up as a storage medium in my system. I can move files between the device and my computer as if it was an external disk or USB drive.
Anything on top of that is designed to be annoying.
This is a non-sequitur. Fragmentation of Android OS versions isn't caused by Android letting you use web apps.
This is a newish change though, within the last couple of years.
Can you elaborate on this a bit? I primarily use Chrome as my browser on iOS. Is it really just running the Safari engine under the hood?
Your argument seems to indicate that you just like iPhones better. Otherwise, I think you would have said "I'd prefer that our company either standardize on one model of Android phone or the iPhone." because both would have the same effect - things would be easier to troubleshoot and manage since everyone would be running the same thing.
Anyway, currently as an iPhone user I think Apple comes up massively short on basic features. For instance - on an $800 phone they're missing a physical message-waiting indicator light! That's completely absurd to me. Some others: You can't have multiple users (and this is big for the Enterprise). You can't put app icons wherever you want, you have to stick them all together in one big pile on the screen. You can't see the time a text message came in until you perform a non-obvious gesture. You can't see anything useful in the call history list until you click an item. You can't even change the default browser!
It's no wonder to me why Enterprise customers don't standardize on the iPhone - they'd be giving up all control to Apple.
Doesn't mean you have to reinstall all your apps every week?
You respond to those two lines by saying that the walled garden prevents fragmentation.
It does not.
* If you were unable to run apps other than via the Google Play Store in Android phones, the OS versions would still be fragmented. App developers have nothing to do with that.
* If only Google manufactured and updated Android phones (hence no fragmentation), you would still be able to run whatever you wanted in the phone. "Walled garden" doesn't mean "closed source".
Apple has on multiple occasions over the years removed apps from the stores that weren't updated to use the latest iOS SDK. This meant that since all apps are targeting the latest iOS there is little impediment to moving the entire platform forward.
I do use an Android phone on a regular basis, and there it's useful, since it only pops up when important messages arrive (read: on-call stuff).
But my daily driver is an iPhone, and sorry - this would be an absolute mess with the amount of apps installed trying to notify me of things. It's virtually impossible to determine what notifications or messages are important. Is a waze notification that a friend will almost arrive important? Not really. Is a waze notification that I should leave in 10 minutes important since the traffic isn't optimal? Absolutely. Relying on such an indicator simply doesn't work the moment you have dozens and dozens of apps installed that all send you mostly mundane low priority messages, but from time to time want to tell you something you really want to know.
In my case, a light like that would be on all the time or off when you actually have a pretty important notification - which would mean you simply cannot rely on it. Notifications are already too complex, and at the same time too limited. Simplifying it into a colored light is just adding to that mess.
iTunes is beyond irritating to use, I've not once fired it up and accomplished what I came to do without at least one google search.