northdan.
Vezi pagina în română

IT Glossary

What is Low-Code?

Platforms that build applications mostly visually, with minimal programming — maximum speed on standard cases, with limits worth remembering.

A spreadsheet that can no longer cope and a full custom development project used to be the only two options; low-code platforms opened a middle road. Applications are built predominantly visually — forms, workflows and tables drawn in an interface — with programming reserved for special needs; their no-code cousins remove code entirely. The market names: Microsoft Power Apps in the 365 world, OutSystems and Mendix at enterprise level, with Airtable, Bubble, Zapier, Make and n8n in the neighboring no-code and automation territory. What genuinely accelerates: standard internal applications — registries, request-and-approval flows, field forms, dashboards, automations between systems with existing connectors — delivered in days or weeks, often by technically minded staff rather than programmers; for validating an idea quickly, it is a superb instrument. Where the fairy tale ends, just as concretely: license costs grow with users and can overtake custom development within a few years (perpetual rent versus an owned asset); customization hits the platform's ceiling exactly when the application becomes important and asks for "one more thing"; performance and fine-grained integration have limits; and platform dependence is total — the app does not migrate, it gets rebuilt. The mature decision is case by case: standard internal processes with modest user counts and an uncertain horizon — low-code without hesitation; the company's core product, its competitive differentiator, the long-term system with many users — classic development on code you own. The hybrid is often the answer: low-code at the periphery of internal flows, real code at the heart.

Let’s talk about your project

Message us on WhatsApp or send an email — you talk directly to a developer.

office@northdan.com · +40 752 070 247

Why it matters for your business

From need to application in days

The registry, field form or approval flow that waited for "whenever there's IT budget" gets built this week.

Business people gain autonomy

Power users build their own small tools — minor requests stop queueing behind the development team's backlog.

Ideas validated cheaply

A working low-code prototype tests demand and process before serious development investment — failures become fast and inexpensive.

Frequently asked questions

Low-code or classic development — how do we decide for a given project?

Four arbitration questions: is it a standard process or a competitive differentiator? how many users, over how many years? (compare cumulative licenses against development cost) how deep are the required integrations and customizations? and how serious would platform dependence be? Standard plus few users plus simple integration equals low-code; the long-term core product equals code you own.

What is "citizen development" and what risks does it carry?

Non-IT employees building applications themselves on low-code platforms — real empowerment with a known flip side: ghost apps holding sensitive data, without security, backup or documentation, discovered when their author leaves. The healthy balance: freedom on approved tools, minimal rules about where data lives and who knows about each app, and one central inventory.

Can we migrate later from low-code to classic development?

The application itself — no: it gets rebuilt, since platforms do not export usable code; what survives is the data (almost always exportable) and — valuably — the process already clarified and validated by real use, which makes subsequent custom development far more precise. That is why low-code excels as a learning stage and traps only those who never planned the exit.