Also, considering advice from [2]: - Build tools for a specific set of developers who don’t have the skills to build the tools they need.
This, and feedback from a few initial users have us asking ourselves if our target audience for Lowdefy is correct. With internal tools, we are directly targeting. mid-sized and larger companies, and currently our product is not yet packaged to serve their minimum requirements out of the box.
When we introduced Lowdefy to data analysts, backend devs, etc. they immediately responded very positively with a sense of empowerment - now they can get stuff on the web without learning html, css, js, etc. The complexity to do basic stuff on the web has not changed much since 2015 [3]
If we framed Lowdefy towards backend-devs / data scientists / analysts, would this be a better audience which resonates more with our value offering? - Lowdefy makes building web UIs as simple as writing a query.
[1] - https://news.ycombinator.com/item?id=26443406
[2] - https://medium.com/@gerstenzang/developer-tools-why-it-s-har...
[3] - https://hackernoon.com/how-it-feels-to-learn-javascript-in-2...
A wswig for internal UI/dashboards has a lot of value for companies that don't have a dedicated internal tools team.
My company had an internal tools teams at one point but it got killed because of other business priorities.
We use https://github.com/sferik/rails_admin, that still requires development time and frontend knowledge, but the framework is terrible.
https://marmelab.com/react-admin/ is much better but also required development time and frontend knowledge.