(Generated by M365 Copilot, and you are welcome to do quick research using different prompt and AI engine)
In the late 1970s through the 1990s, “application generator” was a well‑defined and heavily marketed category of software, especially for business applications on mainframes, minis, DOS PCs, and early Windows. What has changed is the label, not the ambition.
Below is a concise breakdown of what those earlier “application generators” were, how they worked, and why the term has been eclipsed today.
In that era, an application generator usually meant:
A tool that generated large amounts of working business application code (screens, database I/O, reports, menus) from high‑level specifications, not hand‑written source code.
They were tightly associated with:
James Martin popularized this vision in his 1981 book Application Development Without Programmers, which formalized the idea of non‑procedural, specification‑driven software building. [en.wikipedia.org]
These were heavily advertised and extremely expensive tools aimed at insurance companies, banks, and governments.
Example: TELON / CA‑TELON (1981)
Other examples:
These systems made “application generator” a credible, mainstream term by the early 1980s.
As PCs became powerful enough, similar ideas moved to DOS.
Developers routinely built full CRUD systems with minimal hand coding. By the early 1990s, xBase tools dominated PC business application development. [en.wikipedia.org]
FoxPro’s screen builder and report builder (1991) are classic examples of high‑productivity application generation tooling. [landley.net]
By the late 1980s, “application generator” was increasingly folded into CASE tooling:
Many CASE tools explicitly advertised automatic code generation features for COBOL, C, or Pascal from design diagrams. [archivesit.org.uk]
By the early 1990s, studies showed:
This damaged the credibility of the phrase application generator.
The same ideas survived under new names:
| Old term (1980s) | Modern equivalent |
|---|---|
| Application generator | Low‑code / no‑code |
| 4GL | DSLs, ORM‑centric frameworks |
| Screen/report generator | UI builders |
| CASE tool | Model‑Driven Development (MDD) |
Even Microsoft Access, Visual Basic, and later Ruby on Rails inherited much of this philosophy.
Today, “application generator” is:
So modern vendors intentionally avoid the phrase—even when doing essentially the same thing.
Modern AI builders:
Conceptually, they are descendants, not inventions.
What is new:
But the core dream—“describe the business problem, get a working application”—is the same one being sold in glossy ads in the 1980s.
If you’d like, I can:
Just say which direction you’d like to go.