Low-Code
Building mostly visually with small amounts of custom code where needed.
Mostly visual, with a bit of code where needed.
What It Is
Low-Code is a Technology item, filed under Platforms. The canonical meaning is building mostly visually with small amounts of custom code where needed.
It is an idea you reason with rather than a deliverable you hand over, so two teams can both hold it correctly and still apply it differently. That definition is deliberately narrow — the narrowness is what makes it usable.
How It's Used
Low-Code earns its keep in build decisions, tooling and the plumbing behind a working system. In real work it sits close to No-Code, Page Builder and Integration. The practical test is whether a decision changes because of it.
Why It Matters
The cost of being vague about Low-Code shows up later, not today. When it is unclear, small technical debts compound into a rebuild. Deciding it deliberately costs one conversation. Leaving it undecided costs several.
It is an idea that changes what you decide, not an item you tick off. Mostly visual, with a bit of code where needed.
Termshift™
How the meaning shifts depending on who is using it, and where.
Inside the industry, Low-Code is used tightly and assumed to be understood: building mostly visually with small amounts of custom code where needed.
Away from the jargon, it is mostly visual, with a bit of code where needed.
The Bottom Line
Low-Code pays off when it is specific and costs you when it is not. Mostly visual, with a bit of code where needed.