What Is Low-Code? Origins, Types, and Building Better Platforms

1. Origin of Low-Code Concept

Low-code emerged from the evolution of software development as enterprises sought faster application delivery beyond manual coding.

Programming language generations (1GL‑6GL) show that the fourth generation hinted at low-code ideas.

Generation

Name

Characteristics

Expression

Advantages

Disadvantages

1GL

First‑generation language

Machine language directly understood by hardware

Binary code (0 and 1)

Fast execution, high efficiency

Difficult to write and maintain, error‑prone

2GL

Second‑generation language

Assembly language using mnemonics

One‑to‑one with machine language

More readable than 1GL

Requires deep hardware knowledge, poor portability

3GL

Third‑generation language

High‑level language close to natural language

Syntax and semantics

Easy to learn, readable, portable

Slower execution, often needs compilation or interpretation

4GL

Fourth‑generation language

Higher‑level, often for databases and applications

Closer to human language

High development efficiency, GUI support

Less flexible, unsuitable for complex systems

5GL

Fifth‑generation language

Problem‑oriented, used for AI and logic programming

Declarative problem description

Handles complex problems, fits AI

Steep learning curve, limited application scope

6GL

Sixth‑generation language

Emphasizes automation and intelligence

May combine NLP and machine learning

Higher automation, potential for intelligent programming

Theoretical stage, characteristics not yet clear

In 1982 James Martin coined “low‑code” predicting a future where most computers would operate with little or no programmers.

In 2014 Forrester formally introduced the term, and low‑code platforms enable non‑technical business users and developers to build applications via graphical interfaces.

2. Different Types of Low‑Code

2.1 By Code Quantity

Three modes: Pro Code (full code), Low Code, No Code.

Pro Code offers flexibility and extensibility but requires high technical skill.

Low Code combines configuration (C), arrangement (A), and textual DSL (T) with a typical composition: Low‑Code = 50% C + 5% A + 45% T. No Code swaps the percentages: No‑Code = 50% C + 45% A + 5% T.

2.2 By Scope

Platforms are either dedicated or generic; generic platforms provide a technical base and plugin ecosystem to extend functionality.

2.3 By Business Type

Typical business categories include workflow‑driven, form‑driven, model‑driven (ORM), BI analysis, and component‑driven.

Application Scenario

Interaction Complexity

Data Complexity

Workflow‑driven

★★★☆

★★★☆

Form‑driven

★★☆

★★★

Model‑driven

★★★★☆

★★★★★

BI analysis

★★★★★

★★★★★

Component‑driven

★★★★☆

★★★★☆

2.4 By User Type

Users are professional developers, business technicians, and non‑technical staff.

3. Composition of Low‑Code Platforms

Examples: Alibaba Low‑Code, Wujie Low‑Code, Moka Low‑Code.

3.1 Alibaba Platform

Architecture: protocol → engine → ecosystem → platform, with plugins extending functionality.

3.2 Wujie Low‑Code

Starts from data source, builds form mapping, then visual drag‑and‑drop driven by data models.

3.3 Moka Low‑Code

Based on MagicCube editor, adds a code generator to produce page configuration files.

Code generator maturity levels range from Level 1 (no generator) to Level 4 (plugin system).

function f() {
    // ...
    if (xxx) {
        return 1;
    }
    // ...
    if (yyy) {
        return 2;
    }
    // ...
    if (zzz) {
        return 3;
    }
    // ...
    return 4;
}

4. Three Fundamental Steps of Program Development

4.1 Layout

Layout arranges UI components according to design specs; low‑code editors provide visual drag‑and‑drop layout tools.

4.2 Interaction

Visual logic orchestration uses event‑driven actions and flow diagrams to define component interactions.

4.3 Data

Data handling defines how components fetch and render information, often abstracted in low‑code platforms.

5. Building a Better Low‑Code Platform

A good platform offers fallback strategies, allowing pure code for the 20 % of edge cases where visual development is insufficient.

Additional value‑added features include UI alignment, design‑to‑code conversion, analytics, security, performance, and compliance governance.

6. References

Low‑Code Methodology, Programming Language Generations, articles from Juejin, GeekTime, and other sources.