No-code isn't about the tools, it's about who gets to build. The real power is giving domain experts and non-technical people the ability to create apps themselves, rather than waiting for developers to do it for them.
No-code is a who. Often when we talk about no-code, we're talking about tools, right? Usually we're talking about the domain of visual programming, of the being able to drag things around on the screen, be able to express intent. This is like what Webflow does, this is what some of these other tools do. But what I have found is that no-code is much more about who is creating these tools than it is the way that we create the tools. It's going to be about somebody who doesn't have deep technical training, but who has an attitude towards technology that says, Yeah, there could be an app for that. There should be an app for that. And that level of entitlement, I can make the app for that. I can see how to get from here to there. And then the job of the tool is to enable that no-coder to make that happen. So when you're looking around asking what is no-code, what is really no-code, I think we get lost in the idea of without writing a line of code or stuff like that. The question is who can use the tool? And when it's a wider universe of domain experts, we have done the job of no-code and created real value in the end.
