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
- My API 101 Workshop At @APIStrat In Chicago Next Week
- Some Advice For The Enterprise When Beginning Your API Journey
- Machine Readable API Definition Format Swagger Matures to 2.0
- How Do We Continue Moving Green Button Data And APIs Forward?
- Beyond Public APIs In Government: Internal Access to Resources
- Can You Show Me The ROI On All Of This API Stuff Before We Commit
- In The Future APIs Will Be Default For All Cities
- No Public APIs Are Not Going Away Just Cause A Few BigCos Fumble At It
- Internal API Search Engine For Everyone At Your Company (Not Just Developers)
- If You Need Assistance With Your Healthcare API Strategy I Have The Person
- Explaining APIs To Senior Leadership: Access To Company Resources Without The IT Hassle
- A Conversation With @ijroth, @dorkitude, @antonyfalco, and @medjawii In The Next Generation API Stack Panel @APIStrat
- API Evangelist Thoughts On The Right To An API Key And Algorithmic Organizing
- Explaining APIs To Your Senior Leadership
- An API Evangelism Strategy To Map The Global Family Tree
- Thank You For Your API Evangelist Blog(s)
- Video From The Hypermedia Panel At API-Craft In Detroit Last Month
- Please Open Source Your API Before Shutting It Down
- Explaining My Work Around APIs In Higher Education To Institutions
- You Can Have An API Just By Choosing Products And Services That Have APIs
- Using Excel As An API Datasource And An API Client For The Masses
- Brewing Up Something Awesome With The Jive Software API
- Relationship Between APIs And Containers
- Real-time and Visualizations Will Be Key in Financial API Deployments
- Notification Focused Startups Within Leading API Ecosystems