|
|
|
|
|
|
by scarface74
1388 days ago
|
|
|
Once you make an API public, no matter how badly designed it is, you have to support it forever. I would much rather an API be private, let the company dog food it and let their internal employees use it, and then make it public. It also gives them the freedom of completely changing the internal workings. The extensions API and the Siri integration for third parties are great examples. The Siri intent based API is very usable and reminds of the Amazon Lex based API - the AWS version of the consumer Alexa skills SDK. |
|
|
That's simply not true.