1st AdminJS Community Survey Summary
Our goal, as the AdminJS team, is to build software with and for the community. The first step to doing so is to know each other better. Hence, in mid-June, we decided to run a short community survey.
The first AdminJS Community Survey consisted of four questions:
- What is your current role?
- What is the size of the company you’re working for?
- How many AdminJS instances are you running currently?
- Who is using the AdminJS panel in your company?
We’ve sent over 500 invitations over Slack and received 32 responses, which gives us a 6% response rate. It’s not an excellent value, but we consider it a good start!
Results show that more than 50% of respondents are Software Engineers, and almost 30% identify themselves as CEO or CTO of their companies. Data shows that our community is primarily technical.
Taking a look at the responses to the second question shows that most respondents work in small and medium businesses (below 50 employees). However, there is also a noticeable group working in enterprise organizations.
An interesting fact is that half of the respondents maintain more than one AdminJS instance within their infrastructure. Further data investigation shows that small and medium companies are the ones who install AdminJS on more machines. Some of our users are software houses building multiple applications at once, which might explain this phenomenon. Still, we plan to dive deep into this anomaly to understand why people need more than one instance of AdminJS in their setup.
Answers to the question about who uses the AdminJS panel were counterintuitive. We’ve built AdminJS for a specific use case, in which non-technical people need to edit their database entries. Thus, the expected answer would be that the majority of our users are non-technical employees.
However, over 65% of our respondents are Software Engineers, with only 40% of answers indicating that non-tech workers even have access to the AdminJS panel. Management-level seems to be working with AdminJS in only 30% of cases.
This knowledge helps us understand whom we’re building the software for and gives invaluable insights helping to shape the future of AdminJS. Of course, this survey is only a single step on the road to better understanding our users. Still, we hope that by reading this article, you’ve learned that you are in good hand using AdminJS. And if you’d like to share your thoughts, just drop me a line at chris@adminjs.co. Cheers!
