"No-code" and "low-code" are fading from search — AI-native app builders killed the category name

Search and vendor language is quietly moving away from "no-code" and "low-code" even as the underlying market keeps growing toward a projected $52bn in 2026, because AI-native tools that build software from a plain-language description have made the old drag-and-drop, visual-builder framing feel dated — a naming shift worth knowing if you're commissioning software and hearing pitches in outdated terms.

The no-code and low-code market isn’t shrinking — most estimates still put it around $52bn in 2026 and growing fast. What’s shrinking is the terminology itself. Vendors that used to sell “visual, drag-and-drop, no-code development” are increasingly describing the same category of product as “AI app builders” or “build software by describing it,” and search behaviour is following the vendors: people are typing “build an app with AI” far more than they’re typing “no-code app builder,” even when they mean roughly the same outcome.

The reason is that the mechanism actually changed. Classic no-code meant assembling an app from prebuilt visual blocks — a real constraint, and one power users hit fast. The current generation of tools generates working code from a natural-language description, which is a genuinely different capability and, for a lot of buyers, a genuinely different (and higher) set of expectations about what the tool can do unassisted. Calling both things “no-code” undersells the newer category and oversells the older one — so the language is splitting to match.

Why this matters if you’re evaluating build options

If a vendor or agency is still pitching in “no-code platform” terms, it’s worth checking whether they’ve actually kept pace with what AI-native tools can and can’t do, or whether the pitch is running a generation behind the product. The gap matters commercially too: tools in this space are excellent for prototypes and internal tools, and still consistently fall short on the things that make software commissionable at scale — proper data architecture, security review, integration with existing systems, and a codebase a human team can maintain once the AI-generated first draft needs to evolve.

So what

A language shift like this is a useful prompt to re-check your own assumptions about what a fast AI-built prototype can carry into production. If you’ve got something built with an AI app builder that now needs to scale, harden, or integrate properly, see our custom software development work, or get in touch to talk through the gap between prototype and product.

← All research

More research.

GitHub Copilot SDK is becoming the Microsoft Copilot SDK: what builders of AI products should know

On 28 October 2026 GitHub said its Copilot SDK is being renamed Microsoft Copilot SDK, the programmable layer for the shared Microsoft and GitHub agent harness. No immediate action is needed.

Read ›

GitHub Agent Merge: Copilot now watches your pull requests and fixes what blocks the merge

On 28 October 2026 GitHub added Agent Merge to pull requests: a 'Watch and fix' option where Copilot repairs failing Actions workflows and merge conflicts in the cloud, optionally with auto-merge.

Read ›

Claude Code 2.1.314 adds a setting that blocks AI file writes outside the project folder

Claude Code 2.1.314 (30 October 2026) adds permissions.blockWritesOutsideWorkingDirectories, so Claude's file-editing tools refuse any path outside the project in every permission mode.

Read ›

GitHub Enterprise now includes Copilot: seats are bundled, AI usage moves to your budget

From 28 October 2026 account-team customers can get Copilot included with every GitHub Enterprise licence, with AI usage metered against an enterprise budget from the first request. Standalone Copilot is $10 per user per month.

Read ›

GitHub Copilot Fusion goes GA: one pick, many models, and a 30% launch discount

On 28 October 2026 GitHub made Copilot Fusion generally available: instead of choosing a model, developers pick an effort level and Copilot routes each task across models. Paid plans get 30% off model costs for a limited time.

Read ›

GitHub Agentic Workflows is generally available: automations written in plain Markdown

On 28 October 2026 GitHub made Agentic Workflows generally available: AI agents that triage issues, analyse CI failures and update docs, defined in Markdown and run inside GitHub Actions with read-only defaults.

Read ›

Start a project

Building with AI? Let's talk.

Tell us what you are building. We'll give you an honest view of the right approach.

Start a projectSee our work