A project to learn who is using Ember, and how
With nearly 1600 responses, here are the 2017 survey results!
During the course of the survey, Ember 2.12 became the latest stable release of the framework. The 2.x release cycle began in August 2015, and although 14% of developers still maintain a 1.13 app the largest segment of developers work with the last one or two Ember releases.
Ember's Long-Term Support releases have emerged as a visible trend, and 21% of participants use the 2.8-LTS release (the most recent during the survey).
We asked respondents how likely they were to recommend Ember to a friend or colleague. An average recommendation score is 8.4, and the calculated Net Promoter Score is 42. The majority of responses were a perfect 10.
Using the recommendation scores we created three segments of Detractors (1-6), Passives (7-8), and Promoters (9-10). Participants reported their reasoning for their score as free-form text, and below we've provided the most frequent category of responses in each segment based on similarity analysis.
Here is a flavor of what reasons participants gave for their scoring:
As the last question of the survey we asked participants: "What is the most important thing the Ember project can do today?" Using text similarity analysis, we identified the most commonly mentioned topics. Here they are with a selected quote.
Better Documentation, Examples and Guides
We were curious how important these topics were to participants with different amounts of experience. The following chart shows how experienced with Ember developers mentioning each topic are:
Performance was a common theme regardless of experience with Ember. Documentation and guide improvement requests were more common from developers with less Ember experience while requests for tree shaking, routable components and mobile support were more prevalent among experienced Ember developers.
Employers are choosing Ember despite challenges in finding experienced Ember developers in the job market. Among survey participants, 66% of developers who learned Ember this year did not know Ember when they were hired to their current job, and 49% of developers who learned Ember this year were hired by a company that adopted Ember after they were hired. Companies clearly believe in the benefits that Ember can bring their business and are willing to invest in training their developers.
Ember developers continue to most commonly work on product with a small team. However their roles are becoming more focused on the framework over time: In another question participants reported 45% of them now work with Ember "all the time". This number is up from 32% in 2016.
Almost half of survey participants have been using Ember for over two years.
Most developers work on an Ember application that targets hundreds or thousands of users. In responses to another question in the survey, we noted that more developers work on B2B or B2C apps than internal tools compared to last year.
Nearly one thirds of Ember developers work with an app that is more than two years old. One in five Ember developers is working with an app create in the last three months.
Ruby retains the top spot in desired and actual server-side languages, however it also dropped 4% as a production platform. The only notable mover further down the list is Java, which jumped almost 4% in popularity over the past year.
Atom moved up a spot to become the editor of choice primarily due to a drop in Sublime share. Interestingly, VS Code saw a 13% surge over the past year.
Additionally 3% of participants report a disability and 92% of participants were male.
We would like to thank everyone who took the time to participate in the 2017 Ember Community Survey! We hope this information can provide a platform for discussion and ideas around the entire Ember ecosystem as it moves forward.
You can view a summary of the responses to all questions from the survey, and you can view the raw survey data. You can also view the demographic data, which has been decoupled from the primary corpora.
Questions? Feedback? Please email firstname.lastname@example.org