In this post, I would like to explain how the service was shaped and how some of the decisions where made that come with creating a new product.

Survey results

At the time when the original announcement was made, I was unsure which features would be most useful, so I made a survey. 56 people where kind enough to answer the questions. If you where one of them, thank you so much — you helped me a lot!

I was asked to publish the results of the survey, so let’s start with the question with the most surprising result:

How would you like to use JavaScript Studio?

My expectation was that GitHub pull request and npm hook integrations would receive the most votes. Talking to potential clients emphasized that they’d prefer to make on-demand calls from a developers workstation. This lead to a pivot and the focus was shifted to make the command line tool the main interface of the service. This also allows for easy CI integrations.