Posted on 11-12-2013
I was working with Google APIs over the last couple days while building Google Spreadsheet to API tools. It gave me a chance to look around the Google Developers Area and rediscover some of the positive approaches the API pioneer brings to the table.
In this post I wanted to highlight the Google Drive Code Libraries. While the Google approach isn't perfect, I think it sets a good bar for what can be achieved by API providers when delivering their own API code libraries.
I think the languages represented are the baseline for any modern API, and all API providers should consider providing the following languages:
Languages like Go and Node.js are definitely forward leaning, but represent very fast growing areas of the API integration space.
Java and Objective-C represent the mobile space, something API providers can't be ignoring in 2013.
If your target audience is the enterprise, you have to have .NET and Java as part of your API library.
PHP, Python and Ruby are the web staples, that are default for any API that is catering to general web developers.
It should get easier to generate code libraries automatically for API providers who have developed some sort of API definition for their APIs, but for others you will still have eto hand-roll your own code lbiraries.
comments powered by Disqus
Winning in the API Economy
|Download as PDF|
Latest Blog Posts
- Which Building Blocks Should I Use As Part Of My API Support Strategy
- Common Building Blocks of Cloud APIs
- Viewbook Uses Flickr API Design When Designing Their Own
- Expanding An API Designers Horizon Using Apiary
- What Version Of The API Economy Are You Investing In?
- I Am Up To 34 APIs Out Of The Netherlands
- Hello World Product API With Blueprint, RAML And Swagger
- The New Github Developer Program and Integrations Page
- I Have A Valuable API Resource, What Now?
- A Better Understanding Of Government APIs And Their Consumers Before Considering Charging For Use