I joined a few low code hackathons back in 2024, before this agentic stuff.
They're fully dead from what I see. With low code, you'd drag a component onto the screen, click it, look for a field (which may have a different name to the original field), fill that in, and then spend 30 min trying to align it on screen.
With agents, you just tell them what to do. Draw boxes on a piece of paper, take a photo with Claude on your phone, and you'll have a functioning UI.
If you wanted to modify layouts, you can do it straight from the toilet seat on your phone.
The other big feature in low code is maintaining API specs. You'd tell it what the tables are, what to connect to, data objects, and all that. Another thing that AI does better.
I suspect that people who use low-code prefer the node based editor (making UX assumptions here) will still prefer that UI when having to dig into what the Ai did. Similar to how developers (who are holding Ai right) will look at the code.
My other take on the title question, separate from your contextualization and based on my own low-code setup, is that having simpler abstraction layers that give more consistency in application implementation will be beneficial. It is very frustrating that they will implement the same thing in as many different ways as there are days in the week.
My context is low-code via text/template from a declarative config / data.
I joined a few low code hackathons back in 2024, before this agentic stuff.
They're fully dead from what I see. With low code, you'd drag a component onto the screen, click it, look for a field (which may have a different name to the original field), fill that in, and then spend 30 min trying to align it on screen.
With agents, you just tell them what to do. Draw boxes on a piece of paper, take a photo with Claude on your phone, and you'll have a functioning UI.
If you wanted to modify layouts, you can do it straight from the toilet seat on your phone.
The other big feature in low code is maintaining API specs. You'd tell it what the tables are, what to connect to, data objects, and all that. Another thing that AI does better.
I suspect that people who use low-code prefer the node based editor (making UX assumptions here) will still prefer that UI when having to dig into what the Ai did. Similar to how developers (who are holding Ai right) will look at the code.
My other take on the title question, separate from your contextualization and based on my own low-code setup, is that having simpler abstraction layers that give more consistency in application implementation will be beneficial. It is very frustrating that they will implement the same thing in as many different ways as there are days in the week.
My context is low-code via text/template from a declarative config / data.