Posted on 10-25-2012
The most common use of Github by API providers is to publish API SDK's to the popular social coding platform. If you look at most of the the top API providers in operation today, you will find they are actively using Github to not just manage and publicize their API SDK's, but actively interact with their developer ecosystem in the process.
Github provides the necessary workflow for initial design, development and publicizing of API SDKs, allowing owners to create separate repositories for web-based SDKs like PHP, Python and Ruby and mobile SDKs for iOS, Android and Windows mobile.
By making API SDK's public repositories on Github you get all the code management benefits of Github, but also make them available for social interaction by your developers. They will be able to download, fork and potentially commit additions and modifications back to an SDK's repository, allowing owners to harness the creative potential of the developer community.
Active Github repositories for an API are an essential part of any API ecosystem. If you don't use Github for anything else, make sure you publish your SDK's as a public repository. It will make the development of your client libraries a much more social experience, providing huge benefits for your API.
comments powered by Disqus
Winning in the API Economy
|Download as PDF|
Latest Blog Posts
- Someone Please Build My Open, Interactive, Portable, And Visual API Documentation Toolkit
- Dwolla Using Slate For An Evolved API Documentation Experience
- Crazy Mess Of URLs Across 400 Of The APIs In My Stack
- Reworking My API 101 Content: Consuming APIs
- I Need Help To Make Sure The Dept. of Agriculture Leads With APIs In Their Parks and Recreation RFP
- What Is The Biggest Challenge For Fraud Detection API SiftScience?
- Reworking My API 101 Content: Providing APIs
- What I Spent Ada Lovelace Day Working On
- An Outside-In Approach To Jumpstarting An API Effort At The University of Oklahoma
- Exposing Dictionaries From My API Collections