Evolution of Gaode (Amap) Front‑End Technology from 2015 to Present

From 2015 to 2020 the Gaode Maps application‑development front‑end team grew from a handful of engineers handling short‑term operation activities to a 100‑plus‑person team covering five major business lines and hundreds of modules. This article shares the technical evolution of the team, the practice of dynamic‑technology adoption, and future directions.

Timeline of development

2015 – Rapid growth of operation‑activity development, heavy focus on engineering efficiency.

2016‑2017 – Business acceleration demanded cross‑platform consistency and efficiency, leading to the first attempts at dynamic technology.

2017‑2019 – Dynamic technology fully deployed, front‑end role became critical and business scope expanded.

2019‑present – Emphasis on stability, extensibility and long‑term sustainability.

2015: “Small buds”

The surge in user‑acquisition activities required “short‑fast‑quick” development cycles (often under a week). The team focused on three efficiency improvements:

Componentization – building reusable activity components together with operation teams.

Templating – using a “puzzle” approach to assemble simple pages.

Workflow automation – a CLI to accelerate the development process.

These foundations later enabled rapid delivery of large‑scale events such as the 2015 “National Travel Day” treasure‑hunt, where performance, audio/voice interaction and large‑game best practices were explored.

2016‑2017: “A sudden spring breeze”

Business diversification (scenic spots, hotels, banks, charging stations) raised UI complexity, performance demands and the need for fast iteration. Key pain points were:

Rapid release and trial‑and‑error cycles.

Insufficient R&D resources to keep up with growth.

To address these, the team investigated a custom dynamic‑rendering solution, asking critical questions about layout engines (Yoga, absolute layout, RelativeLayout), runtime placement (C++ vs. JavaScript), module system (Node require vs. Webpack), and communication/animation strategies.

Core design

The chosen architecture placed the dynamic engine (written in C++) at the bottom, inspired by WebKit and Node, allowing developers to write native‑like applications with HTML, CSS and JavaScript while retaining file‑system access. A JSX‑based framework provided component‑level CRUD, and a web‑SDK with mock capabilities enabled preview and debugging of POI pages in browsers.

2017‑2019: “Blossoming”

The successful rollout of dynamic technology in the POI (Point‑of‑Interest) business proved the solution’s stability. The team grew rapidly, codebase expanded from 30 k to 600 k lines, modules increased from 1 to over 60, and release cadence shifted from monthly to bi‑weekly. Infrastructure improvements (IDE integration, CI/CD, monitoring) supported this scale.

2019‑present: “Building on solid ground”

Future work focuses on five pillars:

Fine‑grained (精细化) – targeting pain points with systematic solutions.

Standardization (标准化) – aligning with corporate and industry standards.

Differentiation (差异化) – extending Amap‑specific capabilities on top of standards.

Intelligent low‑code (智能化) – material reuse, UI auto‑generation.

Platformization (中台化) – moving common front‑end capabilities to a shared platform.

Key upcoming directions include stabilizing the toolchain, centralizing platform capabilities, full‑link monitoring, material pipeline optimization, and advancing low‑code/zero‑code development.

Overall, the past five years illustrate how Gaode’s front‑end team transformed from a small “front‑end” to a large, robust “big front‑end” capable of supporting the entire Gaode ecosystem.