Evolution of Xianyu's Flutter Architecture and Mobile Development Journey

InfoQ interviewed Yu Jia (Zongxin), the client architecture lead of Alibaba’s Xianyu, to discuss why and how Xianyu adopted Flutter for its main client.

Initially Xianyu used native and Weex solutions, but they could not meet the performance and stability requirements of the main business line. After a series of investigations starting in 2017, Xianyu began a three‑stage migration: research in 2017, business validation in 2018, and large‑scale rollout in 2019.

The migration required a modular architecture similar to Spring IoC, enabling each module to expose interfaces and be packaged as binary bundles, which greatly reduced integration cost and improved build efficiency.

Key challenges were lack of prior Flutter integration experience, performance and stability issues on low‑end devices, and scaling the framework to thousands of developers. Xianyu addressed them by creating the Flutter_Boost hybrid‑stack framework, extending the engine for texture‑based rendering, and evolving Fish‑Redux to provide component‑level isolation.

After adoption, development efficiency roughly doubled, code sharing reached about 80 % of client code, and performance on low‑end phones surpassed the previous native implementation. Quality metrics such as crash rate and memory consumption were brought within Alibaba’s standards through engine customizations.

Future plans include contributing the solution to the Alibaba‑wide “AliFlutter” initiative, unifying client‑cloud programming models, and exploring related technologies such as CEP engines, lightweight game engines, and AR/VR.