Do these tools provide an "integration path"? For example, is there any of these tools written having in mind the fact that they will be replaced by a full fledged software if successful, and as such provide some "injection points" for manualky written software to be executed?
If yes, I can see that being reasonable as a solution to sliwly migrate from a no code software to a fully coded software.
I understand and appreciate the idea of prototyping without code, however this goes end in end with the reality that if adoption is big and you suddenly have to make something performant and it's impossible on the no code tool, you might have a big problem to do (write from scratch) with a tight timeline (performance exploding), potentially losing customers.
If yes, I can see that being reasonable as a solution to sliwly migrate from a no code software to a fully coded software.
I understand and appreciate the idea of prototyping without code, however this goes end in end with the reality that if adoption is big and you suddenly have to make something performant and it's impossible on the no code tool, you might have a big problem to do (write from scratch) with a tight timeline (performance exploding), potentially losing customers.