Mobile Development 23 min read

Reimagining Mobile Development: Unified Cross-Platform Containers and the KUN Strategy

This article outlines the evolving trends in terminal devices and software architecture, argues for unified cross‑platform containers, proposes a streamlined organizational model with fewer, more versatile roles, and introduces the KUN project—a high‑performance, extensible Flutter‑based rendering engine aimed at boosting mobile development efficiency.

Alibaba Terminal Technology

Oct 19, 2022

Reimagining Mobile Development: Unified Cross-Platform Containers and the KUN Strategy

Preface

The author shares personal views on future terminal R&D trends and talent structure, introducing the goals of the Xianyu technology team: driving core business competitiveness through continuous technical innovation and exploring new technology fields for long‑term efficiency gains.

Trends in the Terminal Industry

Device Trends

Smartphones remain the key traffic entry for the next three years, as no other device matches their rigid demand, high‑frequency usage, and open ecosystem.

Software Architecture Trends

Cross‑device development is a business necessity. The evolution has moved from native+Web hybrids to JS‑runtime driven native rendering (ReactNative/Weex) and now to Flutter’s self‑drawing approach, improving performance and consistency across devices. Mini‑programs further accelerate cross‑platform adoption.

Organizational Collaboration Trends

Job roles are merging to reduce ineffective coordination. Xianyu shifted from separate iOS/Android roles to business‑line‑oriented roles, emphasizing one‑person, high‑quality delivery. Similar role fusion is observed in major domestic and overseas tech firms.

Future R&D Model and Path

Reallocation of Terminal‑Side Functions

The current landscape includes many specialized roles (iOS, Android, Web, Flutter, RN, mini‑program). To lower coordination cost and raise talent ceilings, the proposal defines fewer, more versatile roles.

Application Development Engineer (Multi‑Role Fusion)

This role should understand front‑end, back‑end, data, and basic algorithms, enabling a single engineer to collaborate with product and design, dramatically reducing information loss and hand‑off costs. Flutter’s rise allows most development to be done in Dart, lowering the skill barrier for iOS/Android.

Infrastructure Development Engineer

Responsible for core platform capabilities such as terminal containers (Flutter/RN/Weex), build pipelines, IDEs, and workflow tools. Deep knowledge of C++, Swift, Java, compilation, and rendering is required to provide the abstractions that let application engineers focus on business logic.

Upgrading Supporting Capabilities

Unified Terminal Container

Define a single container (e.g., Flutter) to handle >80% of code and scenarios, reducing architectural complexity, improving performance, and easing maintenance. Examples include Alibaba’s Kraken and Tencent’s MXFlutter.

Unified Programming Plane

Provide a consistent API/component library for both Dart and TypeScript, allowing developers to use the same component across Flutter and web stacks, with shared documentation and tooling.

Unified Development Workflow

Adopt a fast, online‑centric workflow (DailyBuild) for application engineers and a weekly cadence (WeeklyBuild) for infrastructure updates, integrating CI/CD, automated testing, and rollback mechanisms to boost delivery speed while preserving stability.

Terminal Container KUN: Empowering Xianyu’s Next Leap

KUN is a high‑extension, high‑performance cross‑platform rendering engine built on a W3C‑subset and Flutter. It aims to provide a single container covering most business scenarios, reducing the overhead of multiple containers.

High Extension : Maps Flutter widgets to custom components, offers documentation generation tools, and plans an ecosystem similar to FishDesign.

W3C‑Based : Supports JS/TS development with a subset of W3C standards, enabling React/Rax usage.

High Performance & Multi‑Device Consistency : Leverages Flutter’s engine for consistent rendering and lower memory/CPU costs compared to mixed‑container approaches.

KUN has already been applied in major Xianyu scenarios (e.g., product recommendation) and will be further expanded to complex cases such as Xianyu accounts. The project will be open‑sourced after large‑scale validation.

Conclusion

The article emphasizes that future terminal development should focus on unified containers, streamlined roles, and efficient workflows to enhance agility and innovation. By adopting KUN and the proposed organizational model, Xianyu aims to maintain a competitive edge in the evolving mobile ecosystem.