Posted on 02-04-2013
Salesforce talked a little bit about its strategy around the development and release strategy around the Salesforce Eclipse plug-in. Providing a little transparency into how they stagger its API releases as well as waiting to release their Eclipse plug-in, until API release is complete.
I’m more interested in this story from an API building block perspective. An eclipse plug-in seems like a building block for only the most mature APIs out there, and especially ones targeting the enterprise. An eclipse plug-in is not for every API, but I think I will add it as a building block to consider.
It also seems like something a 3rd party provider could step up and find success with as well, by building a single or suite of Eclipse plug-ins that provide integrated API developer tools across popular or high value web APIs for Eclipse users.
I believe IDE plug-ins for APIs will be one way we can provide API discovery solutions for developers, by bringing valuable, qualified API resources into their development environments.
comments powered by Disqus
Winning in the API Economy
|Download as PDF|
Latest Blog Posts
- There Are Four API Design Editors To Choose From Now
- Sales, Onboarding And Support In A Self-Service API World
- An API For Developers To Access Their API Account Information
- My Continued Support As Signer Of Oracle v Google Amicus Brief From EFF
- Join Me Tomorrow For A Panel Discussion On API Ecosystems At SF MusicTech
- I Will Review Your API On API Evangelist if You Add An APIs.json File Plus A Machine Readable API Definition
- Hey, Why Isn't This (API) Free
- Resource Base API Monetization vs. Experience Based API Monetization
- Tracking On The Red Flags For API Monetization
- Project Idea: Codenvy-Like Containerized Spreadsheets