"Building Your Business Around Google or Any Other APIs"

I'm reading all the starred items in my Google Reader about Google's latest closing of APIs, most notably Google Translate API. There are some pretty sensational headlines: I don't feel the need to defend Google here, I wish to only defend APIs against people blaming them for what is the fault or responsibility of developers and API owners. I see this same line of attacks on APIs anytime an API company makes a change in their strategy, and developers freak out!

First, let's start with the claims that developers are having the rug pulled out from under them, and you can't build a business on APIs!

This week I was fortunate enough to hear Mark Suster of GRP Partners talk at Gluecon on Cloud Computing: Challenges and Opportunities over the Next Five Years. One important point he made about business platforms and startups (ie. TweetDeck) is you need to have multiple data sources. Without expanding to LinkedIn, Buzz, and Facebook TweetDeck would have been left with only a single data source, and left completely vulnerable.

This is a pretty basic concept when it comes to business. If I start a corner deli, and buy my food from a single food distribution company that delivers every Thursday by truck. Then one Thursday the truck doesn't come, and i'm left for the weekend without any food for my restaurant. Is it valid for me to claim that food distribution companies are no way to build a restaurant?

Even in the case of TweetDeck, using a very unique API (ie. Twitter), they had to diversify with other services. If your building a business around Google Translate API, what sort of plan B and C do you have built into your code? Are you using any of the free or paid solutions out there like Translated.net, WordLingo, Microsoft Translator, Apertium, or ICanLocalize?

Please don't blame APIs because developers don't have a business strategy, or because bloggers are looking for a sensational headline.

Second, let's take a look at Google's approach to Google Translate API. The primary reason Google gave for depracting Google Translate API was:

Due to the substantial economic burden caused by extensive abuse, the number of requests you may make per day will be limited and the API will be shut off completely on December 1, 2011.
I can't help but think, this problem could have been curbed, by bringing Google Translate API under metered billing using the Google Console,as other APIs appear to be heading. This would give a low ceiling of free daily calls on the API, then make users pay for more access.

Except I really don't think Google wants to make its money from translation services, they are focused on where translation supports their core business. World Domination! Wait, no maybe it is search.

If you notice translation is still available in other areas like Google Docs API for translating documents on upload, and in Gmail for translating emails, and Chrome for translating web pages. And of course you can still use the web interface for Google Translate.

So you will still see Google Translate in use where it supports Google's core business. I can see just about any other business making a similar decision.

Also, Google did reach out to communicate the impending deprecation, they called my girlfriend Audrey Watters, and briefed her on the plan. I assume they reached out to others as well.

I would add, that Google could do a better job of communicating their roadmap of various APIs and how they will work to support the core Google set of services, or be offered as a service by themselves. As I watch the Google API ecosystem being pulled together and organized, I still can't quite tell whether the vision is to purely serve the primary Google vision, or provide a wide set of APIs that developers can build businesses on, as recent moves with Google Console might suggest.