Improving Development and Release Efficiency through Standardization, Cross‑Platform, and Dynamic Frameworks in a Large Front‑End Team

The front‑end team serving the entire group’s business units aims to deliver requirements both well and quickly, but faces growing efficiency challenges in development and release due to fragmented UI styles, heavy reliance on native iOS/Android development, and dense release windows.

Standardization

To reduce duplicated work, the team standardized basic and business components, unified interaction design, and introduced a configuration‑driven approach. Examples include a unified cargo‑detail component and page framework that split pages into reusable functional components, allowing the server to drive most business logic and reducing client‑side rendering effort to a 1:7 developer ratio.

Cross‑Platform and Dynamic Development

After standardization, the team explored cross‑platform development, choosing React Native (MBRN) as the primary solution. MBRN evolved through three phases—initial adoption, expansion, and optimization—addressing performance, stability, and monitoring challenges while adding dynamic routing and global dialog systems.

Recognizing limitations of React Native, the team also built a Flutter‑based dynamic framework called Thresh, which parses TypeScript bundles at runtime, converts them to Flutter widgets, and provides a high‑performance, consistent UI across platforms.

Dynamic Upgrade Platform (XRay)

XRay offers unified offline resource management, fast and reliable downloads, gray‑release strategies, minute‑level monitoring, and support for combined upgrades of inter‑dependent business packages.

Configuration‑Based (DaVinci) Development

DaVinci enables visual page building via a DSL that describes UI for web, iOS, and Android. It reuses Thresh’s JavaScript engine for dynamic logic, allowing rapid page creation with a PPT‑like experience and improving development speed by over 100% for certain pages.

Release and Code Management

The team introduced a “dynamic‑static combined” release rhythm: 1–2 dynamic upgrades per week and a monthly static app “shuttle” version. Automated tools synchronize feature branches to master, static, and dynamic branches, cutting manual effort by 75% and ensuring correctness.

Conclusion

By driving standardization, adopting cross‑platform and dynamic frameworks, and automating release workflows, the front‑end team significantly improved development and release efficiency, meeting business demands with fewer resources while maintaining high quality and stability.