When I was first taken on as a developer in 2002 I worked on something like this, though I was very junior. XML was a thing then and so the "app" stored it's co

When I was first taken on as a developer in 2002 I worked on something like this, though I was very junior. XML was a thing then and so the "app" stored it's configuration as an XML file. You would alter your app by writing XML. This meant it looked like code and it failed in the marketplace, as people already had code and they didn't see the use of learning something new. Also this XML had to contain SQL, and HTML, and it had URLs in it. So not something a novice could cope with. The next step taken was to try and build a GUI to generate the XML files, but that didn't sell either because in order to do the really good stuff you still had to understand SQL, and HTML, and Javascript and the URL structure. Even if the app was responsible for some of those things. Projects like these blur the lines between "coding" and "configuring" software, and I think the success of Retool long term will be understanding how to walk that line. The benefit of code is that it allows for greater complexity to be understood meaningfully, and configuration's benefit is that it is easier to learn. I think if someone is expecting to code and gets a configuration interface, that's OK until it limits them, and if they want to configure and end up having to code, then that's a fail for them as well. Good luck.