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
- Making Sure The Most Important Layers Of API Space Stay Open
- A Common Place To Manage All The API Definitions In My World
- Swagger 2.0 For The Docker API
- On Being An API Broker For Hackathons
- Are You A Hypermedia Pragmatist?
- Do You Know That Hypermedia Is A Better Solution For Discovery Than APIs.json?
- API Service Idea: API Via Excel From Within Corporate Email
- With Number Of APIs Continuing To Grow Account Automation Will Be Key
- History Of APIs: NOAA APIs Have Been RESTful For Over 20 Years
- Understanding More About The Web Communications Platform Respoke