What is low-code? Explained with prefab house frames
Low-code means building business apps from ready-made, tested blocks in a visual editor, adding custom code only where needed. Explained with prefab house frames instead of laying every brick.
- Author
Umair Mateen- Published
- Reading time
- 5 min
- Category
- Engineering
In one sentence: Low-code is a way to build business software by arranging ready-made, tested building blocks in a visual editor instead of writing every line of code by hand, while developers can still add custom code where the blocks are not enough.
The everyday picture
Imagine two ways to build a house. In the first, builders lay every brick by hand, cut every beam on site and mix every batch of cement. It works, but it is slow, and every house needs skilled builders for every task.
In the second, the walls, floors and roof come as prefab frames made in a factory. They are already measured, tested and built to fit together. The builder picks the frames from a catalogue, lays them out on a floor plan and joins them up. The house stands in a fraction of the time.
Prefab does not mean every house looks the same. You choose the layout, the rooms and the finish. And when you want something the catalogue does not have, like a curved staircase, a carpenter builds that one piece by hand. Low-code is the prefab method for software.
Ready-made blocks are laid out in a visual model, and the platform turns that model into a working app. Where the blocks are not enough, a developer adds a piece of custom code.
How it works, step by step
- Pick the building blocks (frames from the catalogue). A low-code platform comes with ready-made parts: screens, buttons, forms, tables of data and links to other systems. Microsoft describes building a Power Apps screen as feeling more like building a slide deck than writing code.
- Arrange them in a visual model (the floor plan). You lay out what the app stores, what each screen shows and what happens when someone clicks. In Mendix, the steps of the work are drawn as flowcharts called microflows and nanoflows. Mendix calls these visual ways of expressing what would normally be written as programming code.
- The platform turns the model into a working app (the frames are joined into a house). The platform handles much of the plumbing underneath: storing data, running the logic and showing the screens. Power Apps, for example, run in a web browser or on a phone or tablet.
- Developers add custom code where needed (the carpenter builds the special staircase). When a task is too unusual for the ready-made blocks, a developer writes that part by hand. Mendix lets developers write Java actions that are called from a microflow like any other step. Microsoft lists JavaScript, plug-ins and custom connectors as ways to extend Power Platform with code.
- Change the plan, not the bricks (move a frame on the plan). To change the app, you edit the model and release a new version, instead of rewriting large amounts of code.
Try it · Myth or fact
Low-code: myth or fact?
Decide for yourself first, then tap each statement to check it.
0 of 4 checked
Where the picture stops
- Prefab frames are hard to move once built. A low-code app is easy to change. Editing the model and releasing a new version is a normal part of the work.
- A finished house stands on its own. A low-code app keeps relying on its platform to run. Power Apps, for example, needs a licence for people to use the apps. Moving to another platform usually means rebuilding the app, so the choice of platform matters.
- A prefab kit is fixed at the factory. Low-code platforms are updated by the vendor over time, which brings new blocks but also means your team must keep the app up to date.
Why it matters for your business
- Speed. Ready-made blocks mean less to build from scratch. Microsoft describes its Power Platform as a low-code platform for rapidly building business solutions.
- Business and IT work on the same plan. A visual model is something a manager can look at and understand, so mistakes in the process are spotted earlier.
- No dead end. Because developers can add custom code, an app can grow beyond what the blocks offer, without starting again.
- Control. The platform gives one place to manage who can see and change data. Microsoft's Dataverse, for example, has role-based security for tables and individual records.
An example
Imagine a 40-person property management company that tracks repair requests in emails and spreadsheets. Tenants report a leak, someone copies it into a sheet, and jobs get lost.
Using a low-code platform, a small team builds a repair app. A tenant fills in a form on their phone. The request appears on a staff screen, a manager approves it and a contractor is assigned. All of this comes from ready-made blocks laid out in a visual model.
One piece is unusual: the company's old accounting system needs a special file format. A developer writes that one connection as custom code. The rest stays in the visual model, so the operations manager can review each change before it goes live.
Frequently asked questions
What is the difference between low-code and no-code?
No-code tools aim for apps built entirely without code, usually for simpler needs. Low-code tools are also visual, but expect developers to add code for the harder parts, so they suit larger business systems.
Is low-code only for non-programmers?
No. Business users can build simple apps, but professional developers use low-code too. They build faster with the visual blocks and write custom code where it is needed.
What are examples of low-code platforms?
Well-known examples include Mendix, Microsoft Power Apps and OutSystems. They differ in how much they suit large business systems, mobile apps or quick internal tools.
Can a low-code app connect to my other systems?
Usually yes. Platforms include ready-made connectors for common services, and developers can build custom connections through APIs for anything else.
Related explainers
- What is a prototype? Explained with a floor plan before the bricks
- What is an API? Explained with a waiter in a restaurant
- Frontend vs backend, explained with a restaurant
- What is role-based access? Explained with office keycards
The DevDrift builds business apps on Mendix, with custom code where the blocks stop: see how.
Sources
Could you explain this to a colleague now?
Mark it and posts that mention it will show a tick. Saved in this browser only.