Posted on 12-28-2012
You can learn a lot from the history of APIs, and following what the pioneers are doing. Salesforce isn't the coolest API within the Hacker News community, but when it comes to building an API ecosystem--Salesforce knows what they are doing.
I was reading through the Salesforce top developers highlights of 2012. Their highlights doesn't just showcase the success of the community, but what Salesforce feels is critical to keeping their ecosystem healthy.
- 800,000 developers and climbing: the Salesforce Platform Developer Community is growing at an unprecedented rate.
- Cool new Salesforce technologies: Identity, Salesforce Touch Platform, Force.com Canvas, and Java on Heroku for the Enterprise were released.
- Content is king: Great books such as The Salesforce Touch Platform Mobile Development Guide and Dan Appleman’s new book Advanced Apex Programming for Salesforce.com hit the shelves.
- Community is making noise: Salesforce Stack Exchange launched and is already at 1,000 users. Developer User Groups have grown to 60 groups across the globe and climbing.
- New leaders have emerged: Andy Boettcher, Junji Imaoka, Keir Bowden, Sanuki Ikou, Simon Goodyear are the most recent MVPs to join ranks of the Force.com MVP Program.
- We are staying connected, more often and in more ways: Webinars, CodeTalks, Google+ Hangouts, Facebook,Twitter, Discussion Boards, and the list goes on.
- Developer Events of Epic Proportions: 10,000 Developers at Dreamforce ‘12 with close to 300 sessions, Developer Zones at Cloudforce in New York, Tokyo, and London, and Developer Weeks in Brazil and India.
What I hear when I read this list is that to get to 800K developers (holy shit), you need to constantly release new technologies, product resources and content to support your platform, give your community a voice with an emphasis on showcasing the leaders--while also engaging with developers both online and offline.
Salesforce has been building their API ecosystem for 12 years! Twice as long as Twitter. What they highlight as part of their developer community in 2012 is something you should be doing in your own developer community.
comments powered by Disqus
Winning in the API Economy
|Download as PDF|
Latest Blog Posts
- I Find It Interesting That Wordnik Created The API Definition Format Swagger
- Where Do We Start With APIs At The University of Oklahoma?
- What I Would Look For When Hiring a Modern API Developer?
- The U.S. International Trade Commission Includes APIs In Latest Report
- Thank You @3Scale For Investing In The Community With @APIStrat
- Introducing API.Report, A Community API News Site
- Extract Knowledge From Audio And Video Using The Clarify API
- 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