3 ms·
Shouldn't they have started with an API? Facebook tacked on their API later and look how well that's worked. Facebook's API is horrible, just figuring out how
by wavephorm 15y ago
Shouldn't they have started with an API? Facebook tacked on their API later and look how well that's worked. Facebook's API is horrible, just figuring out how to use the login system is extremely painful.
Google should have built an API first, and built their own Google+ website on it.
- dshah 15y agoMy guess is that they actually have an internal API that they used to build their own "user facing" app. But, their challenge could be that making an API public involves more than just having the lines of code to do what is necessary. Especially at their scale.
- pestaa 15y agoAny time I work with a Google API I am literally surprised how beautifully engineered they are. I trust Google on this one too -- so much in fact, I believe they already have such an API that the website is interacting with, it is just not mature enough to be publicly accessible.
- georgemcbay 15y agoAgreed 100%. The only issue I have with Google APIs is wondering if they might get cancelled. The actual APIs are a joy to use compared to most sites'. They are well designed, well documented, and mostly consistent across different products (once you implement something using one Google API, the rest look pretty familiar if you use them later).