Monthly Archive: December, 2018

The Future of Salesforce IDEs

As you hopefully have seen, we have been working hard to build a first-rate, modern developer experience with the Salesforce Extensions for Visual Studio Code. In the last year, we have added many new features to the extensions including the free replay debugger, the ability to develop against any org, and lots of other productivity enhancements. We have no intention of stopping either. We will continue to invest in these extensions to make them the premier developer experience for the Salesforce Platform. This post will give you a look into where we are heading with IDEs and developer tools on the Salesforce platform.

Building in the open

We are strong believers in open source developer tools. The final product of a developer tool is always better when the end users are involved in the process of prioritization, designing features, and providing honest feedback throughout the product lifecycle. To this end, we are committed to building the Salesforce Extensions for Visual Studio Code in the open. This doesn’t just mean that we open source the code, but rather we run the project in the open — for everyone to see and participate.

There are several things we have done to make this project as open and transparent as possible. First, we do all our development in a public repository on Github. If you want to send a pull request, comment on a change, or just look at the code to see how things work, you are free to do so. You can see which features we are actively working on and which pull requests we are currently reviewing.

Second, we publish our roadmap. We don’t maintain a secret private roadmap and a public roadmap, there is just one. The main reason to do this is so that, you as the end user of this tool have visibility and influence on what we build and when we build it. The important thing to remember about this roadmap is that it isn’t set in stone. We ship our extensions every week and are always iterating and adjusting the plans based on customer feedback. Additionally, this roadmap is not complete. That is because usage of these extensions is growing every day. As more and more people are making the switch to Visual Studio Code, we are seeing more and more ideas and requests. We leave room in our backlog and roadmap to accommodate customer requests and bug fixes as quickly as possible.

Third, feature requests and specifications are documented publicly. As the product manager of the Salesforce Extensions, I use Github Issues to document potential new features. This allows me to solicit feedback as early as possible in the planning cycle from customers. Rather than spend the time to build something, release it, and then get feedback, we can get feedback before a single line of code is even written. Additionally, this allows you to help with prioritization. If there is something you are passionate about, let us know with a comment or a