4 ms·
> The last thing you should want as a developer is to use a half baked API that Apple hasn’t dig fooded first. That is a massive and sweeping generalization. I
by shkkmo 7y ago
> The last thing you should want as a developer is to use a half baked API that Apple hasn’t dig fooded first.
That is a massive and sweeping generalization. If developers are being put at a competitive disadvantage by not having access to a feature, I'm pretty sure some of them would love to use an unstable API to stay competitive.
- GeekyBear 7y agoDidn't Spotify complain that there wasn't a public API to store music in the local storage of the Apple watch one year and then not make use of it after the API was made public in the next version of the OS?
- shkkmo 7y agoAre you asking me? I don't see your point.
- saagarjha 7y agoSpotify whined about a lack of an API but did nothing when the API was eventually released.
- shkkmo 7y agoAnd how does that have relevance to the question of if developers will use APIs marked as unstable? I ask again, what is your point? Throwing out random facts is not a discussion.
- saagarjha 7y agoHere Spotify has chosen to not use an API that Apple has marked as stable.
- shkkmo 7y agoAnd as such clearly fails to be relevant to the discussion.
- scarface74 7y agoOnce Apple introduces an API,Apple has to support it for years even if it’s not the best. See Microsoft’s cluster of bad APIs and a dozen ways to do anything for a degenerative case.