Exploring Lowcode and Micro‑Frontend: Towards the Next Generation Front‑End Framework

The article reviews the evolution of front‑end development since the rise of Angular, React, and Vue, and examines why no new front‑end framework has yet captured widespread attention.

Lowcode is described as a GUI‑driven, configuration‑based approach that replaces hand‑written code. Its recent popularity is attributed to mature front‑end engineering, a shortage of front‑end developers, and the commercial push from large enterprises.

Key reasons for the lowcode surge:

Established front‑end tooling and engineering practices enable higher productivity.

Continued scarcity of skilled front‑end engineers.

Enterprise demand for B‑side business platforms.

The article contrasts historical lowcode attempts with current platforms, noting that modern solutions aim to solve ordinary users' programming needs rather than merely improving developer efficiency.

Domestic lowcode platforms such as 易企秀, 淘宝天马, 阿里云凤蝶, and 百度爱速搭 are listed, highlighting their template‑based page building and component configuration capabilities.

The author questions whether lowcode can solve all problems, raising concerns about decision‑making on platform selection, scope of use, and handling of edge cases where the platform cannot meet 100% of requirements.

A concrete scenario is presented: building a simple promotional page for an app with a download button, then encountering a new requirement to open the app directly if already installed. The dilemma of extending the platform with custom actions versus developing a bespoke solution is discussed.

The article then shifts to micro‑frontend , explaining that it borrows concepts from back‑end micro‑services to split large applications into independently deployable front‑end modules. Challenges include unified technology stacks, coupling of development and deployment, and the risk of a single module failure affecting the whole system.

It argues that the rise of micro‑frontend reflects increasing front‑end complexity and the need for higher‑level architectural frameworks.

Next, the piece analyzes traditional front‑end frameworks (jQuery, React, Vue) and their focus on the view layer, followed by a discussion of front‑end engineering (modularization, componentization, standardization, automation) as a means to improve productivity.

The author proposes a next‑generation front‑end application framework that emphasizes highly engineered, JSON‑driven page composition, separating generic component development from page configuration. The framework aims to simplify component creation, enable rapid lowcode/procode and micro‑frontend solutions, and support automated testing, hot updates, and modular isolation.

Key framework details include:

Naming conventions for component properties (e.g., data, children, label) to enable validation and pre‑compilation.

Support for custom components (deployed independently) and custom actions (event‑driven, centrally managed).

Data interaction workflow: write an action → trigger from component → fetch data → mount → component subscribes and updates.

Advantages highlighted are modularity, easier automation and standardization, extensible component design, and improved engineering practices for JSON‑based configurations.

The vision is to balance lowcode efficiency with traditional development flexibility, ultimately incubating a new generation of application frameworks that address architectural and engineering challenges.

At the end of the article, a recruitment notice from Baidu Live’s R&D department is included, inviting candidates to apply via email and providing links to related technical articles.