Posted on 04-17-2012
For the last couple weeks I’m neck deep in getting to know the developers who already use the CityGrid APIs. I want a better understanding of who a developer is, what kind of business they have and what they are looking to get out of the API.
- Twitter Profile
- LinkedIn Account
- Facebook Profile
- Google + Profile
- Github Profile
Usually I know the URL of their website, but if I don’t, I can extract from their email address or sometimes Rapportive will provide for me. I visit each developer’s site and look for:
- Blog w/ RSS Feed
- Business Contact Email
- Business Contact Form
Next I build a quick one sentence description, telling me who they are and what they do. I also assemble a comma separated list of keyword and key phrases that best represent what they do.
Before I’m done looking around their site I take a picture of their home page, so I have a visual reference to go with the developer profile. The home page image can go further than just a logo sometimes.
I take all of this information, put it into a database, and connected it to a JQuery Carousel that allows me to watch a slideshow that walks me through the world of my developers, and watch like a TV channel.
This process not only gives me a 100K understanding my developer ecosystem, but helps me remember as much as I can about each developer. From this I hope to better engage them on a daily basis as well as provide feedback to the CityGrid API roadmap based upon quality API developer segmentation.
comments powered by Disqus
Winning in the API Economy
|Download as PDF|
Latest Blog Posts
- Showcasing Your API Integrations With Other Platforms
- Increasing The Focus On APIs In Higher Education Is Important
- Getting To Know Mike Amundsen For The API Craft 2014 Detroit Hypermedia Panel
- 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