Sure. Yet any no-code derivative is therefore stuck with a general-purpose implementation. Which admittedly is fine in many contexts. However, the distinction

Sure. Yet any no-code derivative is therefore stuck with a general-purpose implementation. Which admittedly is fine in many contexts. However, the distinction is important. You "assemble" no-code. You cannot buy a dog puzzle and reconfigure it to be a cat puzzle. IMO, this is the inherent limitation of a no-code toolset. Also, users are handicapped by the developer's capability. That is to say, the efficiency and specificity of the tool's internal codebase represents an invisible glass ceiling for its users.