The entire gist behind these tools that try to get away from "code" is based on the assumption that code somehow makes things more expensive or difficult. I really don't think that's true.
The entire gist behind these tools that try to get away from "code" is based on the assumption that code somehow makes things more expensive or difficult. I really don't think that's true.
I think no-code only makes sense if you make multiple, similar products comprised of existing building blocks and then using a basic visual editor to mark the relation between them. But again, with code it can be similar, you can have differet libraries/packages/APIs and just describe the connection between them.
I think one of the draws to these kinds of applications is that designers are trying to close the gap between themselves and developers.
I'm interested in this problem, but I'm taking a different approach, because I totally agree with you. The source of complexity is not the inherent complexity of coding itself - it's just the complexity of the problem.
So I'm currently trying to build a coding language for UI designers. The idea is that it would merely a textual interface to express design specifications, unlike other languages which are geared towards implementation. And it would use the same verbiage and mental models that designers are familiar with.