Hello everyone!
Thank you again to those who responded to the survey.
I have exported the responses and aggregated them in a spreadsheet.
I have removed the emails 
https://docs.google.com/spreadsheets/d/1iPt5aoI9VGwg-FWSfE4jaNw7NZtyDA6pYanEB0ycWck/edit?usp=sharing
Overall, we can see a good satisfaction around the product and the general direction the project is taking
After that, what comes up the most is the lack of integrations, but that’s normal as it takes the most time!
What I also note is that the communication about the available integrations is not necessarily effective enough: There are requests in the survey that are already developed ^^
Perhaps more time should be invested in communication/training around Gladys 4:
- Writing tutorials?
- Blog articles?
- Video tutorials?
After all, it’s always a trade-off: doing communication or developing features?
I think I may have been very focused on development in the last few months to address major gaps (multi-users, bluetooth presence, etc.) but now that we have these major features, I can dedicate more time to communication and reduce the time I spend coding/reviewing PRs (the ideal would be 50% dev/50% communication)
Development is not everything, we also need to talk about the product to get new users
Product Growth
We had a big boom in installations the first month of the launch in November (780 unique instances of Gladys), but it has slowed down to around 485 instances in February.
Edit: here is the number of new instances per month (this is not the « stock » of instances, it is only the new ones per month):
Despite this, we have 3200 unique visitors to the site each month. I think there is work to be done to get more users to move from just visiting the site to becoming Gladys users.
I think we are missing use cases to show how our users use Gladys: explaining real cases in articles so that site readers can project themselves.
This is what we do here for example:
Everyone in the community is welcome
When you want to « help the project », you often think of development and PR on the code, but that’s not all: proposing new tutorials/articles on the site helps just as much!
The site is open-source and editable by everyone I remind you: GitHub - GladysAssistant/v4-website: Gladys Assistant website · GitHub