Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

API parity:

The last thing you should want as a developer is to use a half baked API that Apple hasn’t dig fooded first. Apple has slowly opened up Siri and it’s opening it up more in iOS 13 specifically for music. Apple is not going to do an Alexa style voice command line. The intents system while more limited is better for most users and developers.



> 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.


Didn'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?


Are you asking me? I don't see your point.


Spotify whined about a lack of an API but did nothing when the API was eventually released.


And 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.


Once 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.


Here Spotify has chosen to not use an API that Apple has marked as stable.


And as such clearly fails to be relevant to the discussion.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: