Low/no-code tools as replacements for devs is never going to happen.
But as an "aid" to empower developers... absolutely.
The lowest hanging fruit for a low-code solution would be in the Front-End space since you're dealing with a visual medium anyway, and because Front-End work isn't "hard" as much as it's super tedious which is generally a good target for disruptive automation.
Of course one of the big challenges will be that devs are most comfortable coding in text-heavy non-GUI environments like the IDE or terminal, and any low-code tooling that leans on a visual interface is going to struggle.
This was actually a huge problem for me at https://rapidream.com (apologies for the shameless plug). I wanted a Figma-to-React dev-tool that I could actually use on my real "day-job" projects, but designing an interface and user flow for users who don't like low-codey tooling was almost a bigger challenge then the actual tech.
But as an "aid" to empower developers... absolutely.
The lowest hanging fruit for a low-code solution would be in the Front-End space since you're dealing with a visual medium anyway, and because Front-End work isn't "hard" as much as it's super tedious which is generally a good target for disruptive automation.
Of course one of the big challenges will be that devs are most comfortable coding in text-heavy non-GUI environments like the IDE or terminal, and any low-code tooling that leans on a visual interface is going to struggle.
This was actually a huge problem for me at https://rapidream.com (apologies for the shameless plug). I wanted a Figma-to-React dev-tool that I could actually use on my real "day-job" projects, but designing an interface and user flow for users who don't like low-codey tooling was almost a bigger challenge then the actual tech.