Posted on 03-23-2012
Every Monday I generate a list of all new API developer who registered for the CityGrid API the week before. This list has the name and email address for each developer, and I manually go down the list, and email them individually, letting them know I’m here to help.
As I email each new API developer I use Rapportive to identify more information about them, such as their website URL, Twitter and LinkedIn profile. If a developer has a Twitter or LinkedIn profile, I engage them on those networks.
After 3 months of doing this, I’ve noticed that developers who work for larger companies have LinkedIn profiles and developers who either are freelance, own or work with a smaller development shop tend to have Twitter.
It makes sense. Twitter is a more public forum, and smaller companies tend to need to market their skills and services and actively engage the world around them. While established companies tend to keep their developers in a more closed environment, suitable for the business social network LinkedIn.
This type of information helps me segment my API developer audience into various groups allowing me to craft blog posts, announcements and share other information with them on appropriate channels. I’m not a big fan of emailing, so being able to push out information regularly on LinkedIn and Twitter, and engage with users that are active on these networks, works very well for supporting my approach to API developer support.
comments powered by Disqus
Winning in the API Economy
|Download as PDF|
Latest Blog Posts
- The New StrongLoop API Server Provides A Look At Future Of API Deployment
- Models For API Driven Startups Built Around Public Data
- Will You Add Me To API Evangelist And How To Spot The Cool Kids
- When I Remix APIs Using Swagger How Do I Deal With Authentication Across Multiple APIs
- It Takes A Team Of Evangelists To Raise An API
- Support For Only Two Creative Commons Licenses In The API Commons
- Machine Readable Terms of Service Didn't Read Applied To APIs Via APIs.json
- API Deployment For Non-Developers Using Zapier, Google Docs, and APISpark
- State of Hypermedia Today @ API Craft In Detroit
- Need A Formal API Standard For Your Government Agency? Fork 18Fs, And Make It Your Own!
- CORS Makes Your API Portable And Remix-able
- Chief Data Officer Needs To Make The Department Of Commerce Developer Portal The Center Of API Economy
- An API Definition As The Truth In The API Contract
- Look At Existing APIs In The Space Before Designing Your Own
- Libraries Hacked: UK Library API, Data And Technology Hacks
- Financial Data Aggregator Yodlee Looking For A Director of Developer Evangelism
- AutoDevBot Open Sources Their API Monitor
- Low Hanging Fruit For API Discovery In The Federal Government
- Looking At 77 Federal Government API Developer Portals And 190 APIs
- Applying APIs.json To API Discovery In The Federal Government
- The Power In API Discovery For APIs.json Will Be In The API URL Type
- Fixing The Machine Readability in API Commons
- Evolving How We Approach The API Lifecycle With APIMatic
- APIs Can Open Up Your Company To Outside Ideas
- APIs Are Often Just A Facade That Is Covering Up The Legacy View Of World