BRENNEN

Industries / Technology / Software and SaaS

Low-code platforms

Low-code platforms are software tools that let people build working applications, automations and data tools by drawing screens, setting options and writing formulas or plain-language requests, with little or no hand-written program code.

2014

Forrester Research analysts Clay Richardson and John Rymer named the category "low-code" in a 2014 report on platforms for building customer-facing applications with less hand-coding. Richardson said he hesitated to claim they were the first to use the term.

processexcellencenetwork.comsiliconangle.com

32

Milestones achieved across 6 domains.

7

To watch for: announced, not yet confirmed outside.

13

Open deliverables. Nobody has shipped them.

In one minute

Where it started

The promise is older than the name. In 1981 James Martin published a book called Application Development Without Programmers, and in the years after, Apple's HyperCard (1987) and Microsoft's Visual Basic (1990 or 1991, by different accounts) let people build programs by drawing them. Forrester gave the category its name in 2014.

Where it stands

Low-code is in routine use: Microsoft said in April 2025 that 56 million people a month used its Power Platform. Since 2025 the newest tools take a plain-language request and write the whole app, a practice called vibe coding, which Collins Dictionary made its Word of the Year for 2025. One such tool, Lovable, says its yearly revenue rate passed $600 million in September 2026. The same failure keeps returning: platforms ship with open default settings and builders' data leaks, from 38 million Power Apps records in 2021 to AI-built apps in 2025 and 2026. Platforms also close. Microsoft and OpenAI are both retiring an AI app or agent builder on 30 November 2026, about a year after launch.

What is open

Most of what is known about these tools comes from their makers or from scans of other people's live apps. The open jobs below are controlled, repeatable tests that anyone could check: what each platform's default settings expose, what it does to data on import, how accessible its output is, how AI builders do on the same written briefs, and what a team can take with it when it leaves. Each can be started this month with free or trial accounts, open-source test tools and current AI coding agents.

Domains

AchievedWatch forOpen

Advances to build with

4 research notes

Open in low-code platforms

3 of 13 open deliverables

Open · Building apps visually

Accessible by default, measured

A public test of the apps that ten visual builders produce on their default settings: Microsoft Power Apps, Google AppSheet, Bubble, Glide, Softr, OutSystems, Mendix, Retool, Appsmith and Budibase. Build the same small app in each (a sign-in screen, a form, a list and a detail page), publish it, and test it against WCAG 2.2, the web's accessibility standard. Use automated checks and six tasks done with screen readers, the programs that read the screen aloud for blind users. Publish a pass or fail for every task on every builder, and repeat each year.

Built with what exists

free or trial accounts on the ten builders; Playwright with axe-core for automated WCAG checks; the free NVDA screen reader on Windows and VoiceOver on a Mac, scripted with Guidepup; OBS Studio for recordings.

Credit · unclaimed

Open · Data and connections

What import does to data

A public test file of 200 values that software tends to change without asking: gene symbols such as SEPT2 and MARCH1, ZIP codes with leading zeros, ID numbers of 16 or more digits, dates in day-month and month-day order, fractions such as 1/2, strings such as 1E5 that look like scientific notation, and words such as TRUE. Load it by pasting and by uploading a CSV file into ten tools: Excel, Google Sheets, LibreOffice Calc, Apple Numbers, Airtable, Smartsheet, Notion databases, Microsoft Dataverse (the data store behind Power Apps), AppSheet and NocoDB. Record every value each tool changes. Rerun every six months, because the tools' behaviour drifts.

Built with what exists

free tiers or trials of the ten tools; LibreOffice run without its screen, and Gnumeric's ssconvert, for scripted runs; Playwright to drive the web tools; Excel's Automatic Data Conversion settings, recorded on and off for each run.

Credit · unclaimed

Open · Automating workflows

Plain-language automations, tested

Fifty automation requests in plain language, such as "when a form is submitted, add a row to the sheet and email the manager if the amount is over 500". Give each to the AI assistants built into four products: Zapier's Copilot, Make's AI assistant, n8n's AI Workflow Builder and Copilot in Power Automate. Run each workflow the assistant produces against test accounts with planted data, and score whether it did the job.

Built with what exists

free or trial accounts on the four products; a self-hosted n8n and Mailpit, a mail catcher that runs on your own machine, to check emails; test Google Sheets and Airtable bases; a script that checks each account's final state after a run.

Credit · unclaimed

Where it sits