The explosive growth of social media, cloud computing and mobile devices is making Web APIs the primary interface for technology-driven products and services, and placing more and more attention on the emerging “API economy.” And with 50 percent of B2B collaboration predicted to take place through APIs by 2016, we are only seeing the tip of the iceberg.
Sustaining an effective engagement campaign can take a surprising amount of work. You could limit yourself to following the leads from the data you collect, but following without interacting first will get you a very low follow-back ratio. More importantly, if you follow and then forget people, they may follow back, but they’ll soon forget you. A high number of followers who don’t reply to, mention or retweet your account are of no value. True engagement is long-term and repetitive.
Controlling a local database is vital for collecting tweets and users from the Twitter API. Once this is accomplished, you no longer have to worry about rate limits, API reliability or speed of access. I do most of my work with MySQL, but any server-based database can be used—even a flat file in CSV format is a viable solution for minimal storage needs.
Do you know what it means to be “brogrammer?” Can you tell the difference between a real hackathon prize and a lame attempt to patronize developers? Meet Brandon Wirtz who recently participated at some hackathons and has some constructive feedback for the people who organize them.
Businesses are taking advantage of the ubiquity of mobile devices and SMS. This tutorial describes how to send an SMS message to a phone with PHP using the Twilio API. Twilio provides numerous communications services, including the ability to make and receive phone calls through the browser, mobile or desktop, send and receive SMS and MMS messages, and handle short codes.
As more and more Web and mobile applications utilize APIs to drive their respective front ends, performance becomes an emerging concern. XML, long used as a method for exchanging data, is giving way to JSON, now considered the gold standard. But is JSON always the right choice over XML? This article examines the foundations of JSON and XML and the differences between them, providing recommendations for how to choose the right path.
Writing API documentation for software being created with an agile process can be especially challenging because what is being documented is constantly being changed. Project managers and developer leads must assign resources to writers up front, and writers should speak up as soon as issues arise because documentation challenges can snowball much faster in an agile environment.
A workshop on open government data pathways by API Evangelist and current White House Innovation Fellow, Kin Lane, shows there is still plenty of potential for developers, startups and interested citizens to influence the government open data agenda and make use of government data assets. Lane ran the workshop as part of the pre-opening day’s workshop series at API Strategy and Practice, being held in San Francisco for the rest of the week.
Any company that makes an API knows that just having the API is not enough. A bare endpoint is probably worse than not having an API at all. To make your API and platform useful you need documentation, tools, examples and forums. If you are a successful API company you start developing a community of people that work with your service. The community shares ideas and helps each other out.