One of the primary advantages of Low-Code is that it makes non-developers operational in creating interfaces or solving feature requests. Those developers can focus on creating better data sources, focusing on public facing products, etc. But low-code is great for letting otherwise smart people build internal tooling. I haven't seen many public facing low-code tools that don't go off the rails pretty quick with any kind of complexity.

FWIW, I've done some explorations with low-code.

Written format:

Using Hasura with Low-code: https://hasura.io/blog/hasura-for-the-low-code-ecosystem/

Retool: https://retool.com/blog/event-driven-architecture-and-reacti...

Microsoft Power-automate: https://hasura.io/blog/integrating-hasura-with-microsoft-pow...

Retool (again): https://hasura.io/blog/integrating-hasura-with-retool-for-bu...

Bubble: https://hasura.io/blog/tutorial-using-hasura-api-with-bubble...

Draftbit (Again): https://hasura.io/blog/a-tutorial-using-hasura-with-draftbit...

Rapid prototyping listicle: https://hasura.io/blog/rapid-prototyping-with-hasura/

Videos:

Draftbit: https://www.youtube.com/watch?v=WrhQKt5-QY8&list=PLTRTpHrUcS...

Appsmith: https://www.youtube.com/watch?v=e4swzfSAevo&list=PLTRTpHrUcS...

Retool: https://www.youtube.com/watch?v=qhFs431UwIw&list=PLTRTpHrUcS...

I do think there's lots of power to low-code and I think for internal tooling specifically or for testing theories or even short-lived public-facing tools, they fit a solid use-case of turning smart people int actionable devs. They still need to "think like a programmer", which essentially makes UI a language, albeit one that's more verbose.

But with a generation of kids learning Scratch and other tools like that soon to hit the job market, maybe these tools are primed for major adoption?

Today I still ask businesses that ask me to help with tools why this CAN'T be a low-code solution, similar to the old adage, "why shouldn't this be a spreadsheet."

Full disclosure, I work for Hasura so there's some heavy handed surfacing of Hasura in those links, but it just goes to show what's possible when you decouple front-end from the API layer, letting different tools solve their scoped problem space.

Edit for formatting.