Low-Code, No-Code: What developers really think…

Low-code and no-code platforms are on the rise. Businesses are drawn to their promise of speed, ease of use, and cost-effectiveness. But what do developers - those who spend their days writing, debugging, and refining custom software - really think about these platforms? At Propel Tech, we’ve got developers at all levels with plenty to say on the subject.

The appeal: A quick fix for basic needs

For businesses looking for a simple, functional application, say, automating a small workflow or managing basic data, low-code and no-code solutions can be a quick and effective fix. As Mark Hansgate , Senior Developer, puts it:

“If all you need is a very basic app, then this is fine. But anything more advanced and you may struggle.”

Accessibility is one of the major selling points of low/no-code. Small businesses, particularly those without in-house developers, can build something functional without extensive coding knowledge. But what happens when a business wants to scale?

The limitations: scalability, security and customisation

What starts as a simple, low-code app can quickly outgrow its limitations. Jiahao Wu , Junior Developer, points out:

“Customisation is non-existent, because no-code solutions are generally used to solve common business logic. But every business eventually has unique traits, which leads to customisation needs.”

Ben Hopper , Software Development Team Lead, agrees:

“They’re quick to set up but don’t really provide a long-term robust solution at an enterprise level. If you have developers, why bother? If you don’t, why hire for something that won’t scale?”

Then there’s the issue of security. Giving non-technical users control over data flows and integrations can introduce vulnerabilities. Ben warns:

“Data access is the main concern. The person setting up the low-code solution needs read access to everything and must understand how the data connects. They may expose more data than they should.”

Mark adds:

“Using established products with a long track record is always a good idea. They should have already covered potential security issues.”

Reducing reliance on developers?

If low-code solutions are meant to reduce reliance on developers, why do developers often end up involved anyway?

Ben highlights a common problem:

“They require someone with advanced IT knowledge to set up, manage, and maintain. I’ve seen developers create and maintain these solutions, but when they leave, you’re left with one app in low/no-code and 99 apps custom-written—with no support.”

Debugging can also be an issue. When low-code works, it works. But when something breaks? That’s another story. Ben explains:

“Debugging is poor and limited. When something doesn’t line up, it can break easily. Often, the people managing the low-code solution don’t have the skills to fix it, so it gets pushed back to IT.”

And what about the quality of code produced by these platforms? Some tools allow for code export, but Mark warns:

“I’ve heard the code can be very low quality, making it difficult for developers to take on. You’d probably be looking at a full rewrite instead.”

The verdict: right tool for the right job

So, do low-code and no-code solutions have a future? Yes, but they aren’t a one-size-fits-all answer. They’re useful for quick prototypes, small-scale applications, and businesses without dedicated development teams. But for complex, scalable, and secure applications? Traditional development is still king.

As Mark puts it:

“You could try to do your own plumbing, but a flooded house would be more expensive to fix than just getting a plumber in the first place.”

Low-code and no-code are part of the tech landscape. But if businesses want longevity, flexibility, and security, developers are still an essential part of the equation.

What’s your take? Have you had success (or frustration) with low/no-code solutions?