yes. doesn’t it seem like everyone has one.
no. those alone all make sense. you have a service – make some user authentication, some inputs and outputs – and boom…mashups galore.
Gone are the early days when a craigslist google maps mashup was cool and new. Nowadays if you don’t have an API you don’t have anything.
Which means even odd-sounding stuff like the Mastercard API – which in theory sounds great but is kind of scary. I mean can you imagine a Bank of America API – or a Blue Cross Blue Shield API 😉
(ok fine – you can build services on top of APIs and still have something)
I guess the point is more that we are now very far removed from a walled garden application/service model. Future native (or html5) apps on mobile phones interact with APIs on your handsets to read sensors in your device.
So let’s see…we have
(b) protocol definitions and function calls
This is all well and good – but where do you manage all these infernal APIs. Permissions, Privacy, Preferences – the bugbears rear their heads again – because the cloud is not just one thing. Every dataset which is API accessible in the cloud in theory needs its own set of preferences.
Messy…and in some instances not ideal in our opinion.
But then…that’s a subject for the next post 😉