Low-code

Low-code sits between no-code tools, which allow no programming at all, and traditional development, where everything is written by hand. It is common for internal business apps, customer portals, dashboards and workflow systems, where much of the work is forms, tables and approval steps.

Low-code is aimed at people with at least some technical skill. A business analyst might build most of an app visually, then a developer writes custom code for a tricky calculation or a connection to an old system. That mix is what separates it from no-code, and also from vibe coding, where AI generates ordinary source code from plain-language requests.

How it works

A low-code platform provides visual builders for the main parts of an application: screens designed by dragging components, data models defined as tables and relationships, and logic set up as flowcharts of steps and conditions. The platform handles hosting, user logins, permissions and updates.

Where the built-in pieces are not enough, developers write code inside the platform, usually small scripts in a common language or custom components, and connect to outside systems through APIs. Many platforms now include AI features that suggest screens, generate formulas or build first drafts of an app from a description, which still need checking.

Like no-code, low-code ties you to a vendor. The application usually runs only on that platform, licences are often charged per user or per app, and moving away means rebuilding. In return, teams can deliver internal tools much faster than building everything from scratch, and the platform takes care of much of the security and infrastructure work that small teams struggle to maintain. Good platforms separate a test version of each app from the live one, so changes can be tried without breaking the tool staff are using. Where that is missing, a small mistake in a visual flow can stop a business process until someone notices and undoes it.

Example

A regional association needs a system for member registrations, event bookings and certificate tracking. A staff member with basic technical skills builds the forms, member tables and approval flow on a low-code platform in a few weeks. A freelance developer then writes custom code to connect it to the payment provider and to generate certificates in the association's required layout.

After a year, membership grows and licence costs rise with the number of staff who need access. The association reviews the total and finds the platform still costs less than maintaining a custom application, but it documents every custom script and exports its data regularly in case it ever needs to move. It also sets up a test copy of the app, so new forms and rules are tried there before members see them. Two changes that would have broken event bookings were caught that way in the first year.

Why it matters for your business

Low-code can deliver internal tools and portals faster and more cheaply than full custom development, especially when the app is mostly forms, data and approvals. The trade-offs are vendor dependence, per-user licensing that rises as you grow, and limits on design and performance for public-facing products. It suits organisations with some in-house technical skill; if nobody can maintain the custom code, a simpler no-code tool or a properly supported custom build may be safer. Ask any vendor how you would get your data and logic out if you left.

Common mistakes

• Choosing a platform without modelling licence costs as users and apps grow.
• Letting custom code pile up inside the platform without documentation or version control.
• Using low-code for a public, high-traffic product where speed and design control matter most.
• Assuming the platform's security settings are correct by default without reviewing who can see what data.

Questions people ask

What is the difference between low-code and no-code?

No-code tools are fully visual and need no programming. Low-code tools are mostly visual but let developers add custom code for logic, integrations and special features. Low-code offers more flexibility for complex needs but expects more technical skill.

What are low-code platforms used for?

Mostly internal business apps: approval workflows, data entry tools, dashboards, customer or member portals and systems that connect older software. They are less common for public marketing websites or consumer products, where design freedom and performance matter more.

Is low-code going to replace developers?

No. Low-code reduces the amount of routine code needed, but complex logic, integrations, security reviews and maintenance still need developers. In practice it changes their work, letting them focus on the hard parts while others build the simple screens and flows.