All the solutions I used were mostly tailored to a single use case, and they made it easy to get 95% of the work done. I'll even include interface builders as no-code.
Then getting to the finish line has always involved writing serious code that would plug itself to the proprietary API whatever No-Code-Solution-du-Jour supported. Of course, if the company selling the no-code goes under, good luck!
Then there's collaborative work and source control support. Most folks are comfortable with GSuite-Style collaborative work but that really doesn't scale.
But there's still a fundamental issue. Every time I worked with non-technical folks using no-code, there was a subset of users that just "got it" almost right away and would end up exploring and maxing out what the tool could do. But the majority of users seemed to be confused and could not move past the hand-holding tutorials. It's almost as if the former could describe what they want so well that it's not ambiguous...
All the solutions I used were mostly tailored to a single use case, and they made it easy to get 95% of the work done. I'll even include interface builders as no-code.
Then getting to the finish line has always involved writing serious code that would plug itself to the proprietary API whatever No-Code-Solution-du-Jour supported. Of course, if the company selling the no-code goes under, good luck!
Then there's collaborative work and source control support. Most folks are comfortable with GSuite-Style collaborative work but that really doesn't scale.
But there's still a fundamental issue. Every time I worked with non-technical folks using no-code, there was a subset of users that just "got it" almost right away and would end up exploring and maxing out what the tool could do. But the majority of users seemed to be confused and could not move past the hand-holding tutorials. It's almost as if the former could describe what they want so well that it's not ambiguous...