I see flexibility as the biggest obstacle to no-code tools. Pick any no-code platform and that platform is inevitably going to have some limitations to it. Now

I see flexibility as the biggest obstacle to no-code tools. Pick any no-code platform and that platform is inevitably going to have some limitations to it. Now for some applications that are fully thought out, this might be just fine. The problem is for all the other applications. What if your app needs some new functionality and you realize that the no-code platform can't do it. What do you do then? The article mentions that you can write "low-code" but that just gets us back to where we started for the most part. A big part of selecting your stack is making sure it's still open ended enough so new features can be bolted on later. Until no-code platform standardize in some fashion (at least in the way AWS/GCP standardized), it's going to be a really hard sell. Sure this platform can do everything you need it to right now. But will that still be the case 3-6-9-12 months down the road? Without a magic ball to tell you the future it's almost impossible to predict this.