Amap Lowcode Platform: Architecture, Serverless, and AI Applications in Frontend Development

In recent months, the Amap (Gaode) Map App front‑end team has been exploring front‑end low‑code building and deployment technologies. The solution has been applied to multiple client‑side business scenarios, proving that low‑code can accelerate feature iteration.

The low‑code practice revealed that, besides visual drag‑and‑drop building, Serverless and intelligent technologies also help bring low‑code to production.

1. Background

Amap’s client uses a self‑developed cross‑platform framework based on a JavaScript engine, enabling high performance and dynamic capabilities for native mobile apps.

Business lines increasingly need recommendation cards that are heavy on presentation, light on interaction, and require rapid iteration. This puts pressure on front‑end dynamism and introduces challenges such as frequent UI tweaks and high deployment speed.

To address these issues, the team adopted a low‑code building‑and‑deployment (搭投) approach to improve dynamism and reduce development cost.

2. Visual Building

The core of the system is a visual builder that maintains a JSON‑based DSL schema describing the UI. The schema follows a standard protocol and can be interpreted by the rendering engine.

The team leveraged Alibaba’s unified building engine (used in DingTalk’s Yi‑Da and Ant’s Cloud‑Fengdie) as the foundation.

Modules such as component ingestion, style simulator, custom setters, template management, and a client‑side rendering engine were built on top of the self‑developed framework.

Initially the platform targeted professional developers, so the building workflow mirrors typical front‑end development: styling, event binding, and even manual lifecycle code on the canvas.

Later the team realized that the ultimate users could be either professional developers or product/operation staff. For the former, the builder must be more efficient than hand‑written code; for the latter, usability and drag‑and‑drop simplicity are paramount.

3. Deployment

Only building is insufficient; a deployment system is needed to deliver the built schema to the client.

The deployment system binds the built schema to a client API and registers the API with the Amap gateway. When the gateway receives a request, it checks whether the API has an associated low‑code schema and, if so, merges the schema into the response object.

Advantages:

API‑centric control of all in‑app traffic via the Amap gateway.

Low development cost and high stability, fitting the existing gateway architecture.

Limitations:

The gateway only covers in‑app business and does not support external H5 activities.

4. Serverless in Low‑Code

To support richer scenarios, the architecture was upgraded with a Serverless layer. Node.js Serverless functions handle heavy data orchestration, allowing the front‑end to process data without adding backend complexity.

By introducing a FaaS function, the deployment can serve both the original client flow and external H5 operations, and the whole solution was named “Amap Lowcode”.

Benefits of Serverless:

Automatic scaling guarantees stability during peak traffic (e.g., 11th‑day peaks).

Unattended operation reduces maintenance cost; deployment, debugging, and monitoring are streamlined.

Drawback: the longer chain increases the learning curve for business developers.

5. AI‑Driven Enhancements

To further simplify the building experience, AI techniques were integrated. Designers can use a plugin to automatically annotate components in design drafts, generating a digitized design file with component metadata.

Developers can then jump to the Lowcode platform, where layout and styles are auto‑generated, eliminating most manual reconstruction work.

After data orchestration and FaaS deployment, the resulting recommendation cards appear on the Amap home screen.

A “schema‑to‑code” feature also allows developers to export the built UI as code when the low‑code deployment path is not suitable.

Additional AI‑driven features include:

Smart preview that selects appropriate context and environment based on design data.

Standard placement containers that require only a unique ID and minimal configuration, enabling rapid integration without additional client code.

6. Summary

The Amap Lowcode platform has four major characteristics:

Designed for consumer (to‑C) clients from day one.

Serverless enables support for both the self‑developed framework and H5 stacks.

A simplified building flow serves both professional developers and operation staff.

AI‑driven design‑to‑code and preview capabilities add intelligent features.

These strengths place the platform at a leading position in the low‑code domain.

We welcome readers interested in low‑code to join the team. Contact: [email protected] (subject: Name – Technical Direction – From Amap Tech).