editor’s note: the author is Joseph Puopolo, founder of Printchomp, a start-up company. In his view, many young startups do not have the ability to stand on their own feet, and API calls have become a crutch instead of generating data themselves. There are a lot of change and change because the API terms of service are out or been beaten to a dying company, Twitter API change is a wake-up call, the purpose of this article is to remind companies:
model of the hermit crab
I’ve been amazed at how many companies will do applications on the basis of API calls and run big business risks to build their companies. Countless app, especially social app, have been grabbing data from other systems and re displaying patterns in their own systems that have popped up in the past two years. Although API has been widely used, I still think the founders of startups have been downplaying the risk of the business.
The risk of
is obvious, and if the data dries up, your business will be the same. For most of the API based calls that have been made, app can consider what happens when the information flow is no longer available. Companies that offer API aren’t necessarily gone, but it’s definitely going to be the one who changes the rules of the game. Twitter’s API change is a warning and an important reminder. Numerous third party Twitter applications have found that important data streams will cease or considerably slow down after the latest 1.1 API protocol, and their hard work will go to naught. Some people put the blame on Twitter and complain about how they dare to turn off the information flow in their community. But I think much of this responsibility should be shared by developers because they know that they can’t control it, and they also make the ecosystem a foundation.
in Twitter’s developer blog, Michael Sippey cites two examples: Tweetbot and Echofon. Sippey said, "for nearly 18 months, we’ve been teaching developers not to build client applications that mimic or replicate Twitter’s mainstream customer experience.". Reaffirming what I wrote in my last article, this guidance applies." I’m not trying to explain what he says here, but to alert startups that build their business on API.
If you have
startups because the terms of service changes or API changes were throat as possible, you should not risk inherent in the company to cover up. At the same time you remove risk from your company, you should also consider the real value of what you can give the user. In many cases (especially in examples of social applications), some app simply grant a new territory on the basis of Twitter or Facebook information