|
>Weirdly implemented, slow, and frequently unavailable backend services Well, they do have the #1 app store, a syncing/backup service used by half a billion people, and the #1 music store in the world (per profit / people). Oh, and a huge music storage service. I don't find iCloud or iTunes or the App Store slow myself. And I'm tens of thousands of miles from the US, and thousands of miles from a decent latency ISP. They're "slow" and "frequently unavailable" compared to what? Is the experience of bying stuff from the Google Play store any better? Is the experience of buying music off of Amazon any better? (I'm not talking about Open vs Close, and other philosophical stuff -- I'm asking about what you claimed here, e.g that it's "slower"). |
iTunes and the App Store are way slower than the typical web sites I browse (including other stores such as Amazon). I also have problems with them sometimes just not loading at all (white pages). And this is on LTE or 100 Mbit WiFi.
As a developer, you tell the App Store is janky since you can literally see the propagation of your app updates before your own eyes. Sometimes the "update" button shows up before the update is actually available (and the app store redownloads the same version), sometimes the update is available in search results before the app information page, some times the update push notification comes first, not to mention replication geographically and across the different country stores. It's first an hour after your update is released that the app store is consistent. It's pretty tolerable now, but it used to be way worse and would take up to 10 hours - we'd get complaints from users due to all the failed updates when the store was inconsistent. We still get complaints on new app releases for random "this product is not available" errors for the first couple hours.