A visual editor is definitely on our roadmap. Our strategy is to make the schema easy to read, write and understand. We want to ensure the dev experience of working with the Lowdefy schema is first class so that change review and version control can be as productive as possible.
Adding a visual dev interface is resource intensive can easily distort the schema quality. We figured by first maturing the schema and making sure it works well with dev tooling, we can add a visual dev interface on top as Lowdefy becomes more popular.
I'm founder of a startup that develops DevOps tooling and we're debating how early to build out the ui. (We have the basics down with Vue like I mentioned.)
So then we really asked how lean can we make this platform to keep it agile while experimenting with the mechanics of the schema. After more than a year of that the experimentation paid off and we now have a very flexible, yet understandable schema for building apps.
But yes. Adding a visual editor on top is one of our goals - and we are getting closer and closer to making it happen.