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
- Turning Forms Into APIs: Crap In, Crap Out
- The Private Internal Tier Of My API Service Composition
- API Virtual Stack Composition Like The Absolut Drinks Data API
- An Operational Harness For My Screen Capture API
- Two Things I Learned On Traffic And Weather Today
- Keep Your API Developer Area Blog Up To Date
- Interesting Example of Social Page Over At Cisco
- External API Deployments Using Sync One Possible Future Of Government API Deployments
- What Are Some Good Examples of Hypermedia APIs?
- API Driven Backend For Apps Using Orchestrate.io