Posted on 03-20-2012
As a building block, a blog is a very valuable tool for building awareness of your API, keeping your developers informed and give a personality to the team beyond an API.
My recommendation to API owners is to always have a blog, however one the most damaging things you can do is stop posting to your blog. A blog is a key variable in my API Stack algorithm, of whether or not an API is worth integrating with, and if you haven’t updated your blog anytime in the last year, I immediately step away.
If you want people to find your API, have a blog. If you want your existing developers to be educated about what can be done with your API, have blog. If you want developers who find your API, to feel confident enough to integrate it into their app, keep you blog updated!
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