Alipay tackled exploding bundle sizes, code‑reuse pain, and architectural complexity by redesigning its engineering stack into a standardized, plug‑in component system that reduced the main app by 47 MB, the pre‑install package by 127 MB, and cut baseline‑sync modifications from dozens to single‑digit numbers.
This article explores how DeWu's community activity platform evolved from ad‑hoc implementations to a componentized, event‑driven backend using OOP principles, modular design, rule engines, and observer‑hook mechanisms, while also outlining future AI‑driven optimizations and system‑wide standardization.
The article details a three‑phase redesign of Taobao’s marketing venues—convergence to simplify content, unification to ensure consistent experience, and efficiency to accelerate iteration—covering design principles, componentization, navigation overhaul, dynamic headers, and visual diversity that together improve user comprehension and conversion during major sales events.
Xilem is an experimental Rust native UI framework that combines concepts from Flutter, SwiftUI, and Elm, featuring lightweight view objects, diff‑based updates, strong typing, componentization, memoization, and optional type erasure, with a core built on xilem_core and Masonry crates.
This article details how SoulAPP reduced its iOS clean‑build time from around 30 minutes to just a few minutes by applying precompiled headers, Xcode build‑setting tweaks, component‑based architecture, binary caching with Rugby, and targeted CI optimizations.
This article explains why component‑based architecture is essential for medium‑to‑large mobile applications, outlines common problems and benefits, and provides concrete guidelines on component granularity, dependency management, communication, quality assurance, and migration strategies.
The Bilibili video template system combines theme‑based editing, a layered architecture, and a cross‑platform Protobuf protocol to enable PGC and UGC creators to produce, review, distribute, and consume richly‑featured videos with standardized media formats, modular plugins, AI integration, and robust quality assurance.
This article examines componentization as a project architecture for medium to large mobile applications, outlining its motivations, common challenges, design principles, component granularity, dependency management, communication methods, quality assurance practices, and the trade‑offs involved in adopting a component‑based approach.
This article explores the motivations, benefits, challenges, and practical guidelines for adopting a component‑based architecture in medium‑to‑large mobile applications, covering topics such as modular granularity, dependency management, communication patterns, version compatibility, quality assurance, and the trade‑offs of componentization versus monolithic projects.
CI quality checksComponentizationDependency Management
This article explores the design of a promotion middle platform that abstracts discount rules, componentizes promotion elements, and introduces a schema-driven configuration approach to enable reusable, extensible, and business‑agnostic promotion activities across multiple product lines.
This article recounts a former Ant Group front‑end engineer's year‑long journey building a low‑code platform for Ant Insurance, detailing challenges of high‑complexity insurance scenarios, platform design decisions, component‑based architecture, real‑world experiments, and lessons learned for future low‑code adoption.
To overcome massive build times, bloated Xcode projects, and tight coupling in its 8‑million‑line iOS codebase, Enterprise WeChat re‑architected the app into four layered, C++‑based common layers and Objective‑C UI components, introducing a Component Management Center, AST‑driven dependency analysis, and a plugin‑friendly shell framework for modular feature integration.
This article details NetEase Yanxuan's Android team transition to a component‑based architecture, identifies inherent problems such as version control, quality assurance, semantic versioning and binary compatibility, and presents the YAC engineering solution—including standardized processes, Gradle plugins, CI/CD pipelines, and tooling—to streamline component development and improve productivity.
This article introduces iOS componentization using CocoaPods, detailing the drawbacks of manual code copying, explaining the creation of local podspec libraries, configuring source files, resources, access levels, and integration steps, while also covering sub‑specs, resource bundles, and practical code examples for Swift projects.
This article explains how to split Android components based on business functionality, handle strong and weak component dependencies, configure multiple UI themes, manage key‑value storage safely with MMKV‑KTX, and use routing frameworks judiciously to keep modular apps maintainable and scalable.
This article explains why monolithic Android projects suffer from long compile times, high coupling, and merge conflicts, and demonstrates how componentization—using a four‑layer architecture, unified Gradle dependencies, plugin switching, code isolation, ARouter routing, decentralized APIs, and AndroidX App Startup initialization—can solve these problems with concrete Kotlin and XML examples.
This report details how the Huolala freight iOS client was re‑architected through componentization, systematic pod version control, a new routing framework, and a multi‑repo strategy, resulting in higher development efficiency, reduced version conflicts, and more stable, scalable codebases.
The B‑Cut video‑editing app was transformed from a monolithic single‑project codebase into a component‑based modular architecture—introducing clear layers, Gradle‑driven unified configuration, independent library/application modules, strict dependency and resource conventions, and a fast‑compile system—thereby cutting build times, eliminating merge conflicts, and enabling reusable components across teams.
This article details the systematic analysis and optimization of the 58.com Android app’s startup process, covering profiling, componentized task framework, delayed initialization, merging launch and home activities, layout improvements, monitoring tools, and results that achieved roughly a 50% reduction in cold‑start time.
This article details how the CTrip iOS team streamlined componentized development by introducing binary debugging, automating source‑code linking, solving M1 simulator clipboard issues, and building a visual ZTPodTool that reduces pod install time and accelerates test‑package generation.
The QianNiu PC cross‑platform framework adopts a COM‑style component architecture—defining interfaces, implementations, and MVP‑based UI modules, with automated code generation and lifecycle management—to achieve consistent Windows/macOS features, improve extensibility and reusability, lower development cost, and boost maintainability and efficiency.
To combat rapid iteration‑induced code bloat and tangled dependencies in live‑streaming apps, the article proposes a lightweight component architecture centered on an IComponent lifecycle, dynamic registration via IComponentRegister, nested components, LiveData communication, and ViewStub‑based on‑demand loading, delivering unified style, better readability, maintainability, and performance.
This article outlines a four‑step, low‑impact migration strategy that transforms legacy Java‑based Velocity template systems into a hybrid Velocity + MVC + MVVC architecture, introduces single‑file componentization, builds a local sandbox with hot‑module replacement, and ultimately achieves full frontend‑backend separation using Vue.
This article systematically explores frontend componentization, covering its motivations, definitions, design principles, component types, implementation strategies, code examples, and the challenges faced during adoption, aiming to help developers achieve higher cohesion, lower coupling, and improved maintainability in web projects.
This article details the evolution of JD.com’s HarmonyOS app from a monolithic project to a modular componentized architecture, describing the existing structure, encountered build and resource issues, the Android plugin reference solution, the proposed HarmonyOS componentization scheme, implementation steps, and release packaging.
AirForce is a platform that centralizes Android component management and release processes by enforcing layered dependencies, tracking baselines with public and private states, detecting conflicts via component version numbers, automating build and packaging through a plugin that validates API changes, and notifying stakeholders, thereby improving stability and efficiency.
This article explains the concept of routing in Android applications, discusses why third‑party routing frameworks are often needed for large, componentized apps, outlines the essential features of a routing framework, and details the implementation techniques such as annotation processing, AOP injection, and service routing with concrete code examples.
The article examines ByteDance’s terminal technology team, outlining current front‑end trends, the challenges of complex processes, component chaos, and massive architecture, and presents their veMARS solutions for DevOps, component management, and application frameworks to improve platform development efficiency.
This article analyses the rise of lowcode and micro‑frontend approaches, examines their current challenges and use‑cases, and proposes a next‑generation, highly engineered front‑end framework that leverages JSON‑driven configuration to balance developer productivity with platform flexibility.
The article outlines the Douyin front‑end team's engineering philosophy, covering the need for modularization of HTML, CSS, and JavaScript, component systems, dependency handling, build tools, loaders, and performance‑focused tooling to improve development efficiency and browser runtime speed.
This article explains the component‑based architecture of modern frontend frameworks, compares their three update granularities—node‑level, component‑level, and application‑level—and illustrates the differences with Svelte, React, and Vue, while also including a brief job‑seeking note from the author.
This article explains why large Android projects need componentization, describes the concepts of modularization and componentization, presents a detailed component architecture, and provides step‑by‑step solutions for independent debugging, routing, inter‑component communication, fragment retrieval, application lifecycle distribution, and migration of legacy projects, complete with Gradle and ARouter code examples.
This article analyses the evolution of Baidu's search result page front‑end architecture, identifies scalability, coupling, and technology‑stack problems, and presents a three‑layer strategy—foundation, modular middle layer, and componentized top layer—along with concrete implementation steps such as TypeScript adoption, service‑oriented modules, dependency‑injection containers, and SSR performance optimizations.
This article analyzes Baidu's mobile search front‑end architecture evolution, identifying scalability and maintainability challenges, outlining a three‑layer redesign strategy, and detailing concrete modularization, componentization, and SSR techniques that other large‑scale web teams can apply.
This article examines Baidu's mobile search front‑end architecture, identifies scalability and maintainability challenges such as massive codebases, unclear responsibilities, tight coupling and outdated tech stacks, and explains the three‑layer solution—foundation, modular middle layer, and componentization—along with implementation details, dependency injection, SSR adoption, and performance optimizations.
The article examines the evolution of front‑end architecture using Baidu's mobile search result page as a case study, outlining challenges such as massive codebases, coupling, and outdated tech stacks, and presenting a three‑layer solution involving foundation, modularization, and componentization with SSR optimization.
This article examines Baidu's mobile search front‑end architecture evolution, detailing the challenges of massive codebases, unclear responsibilities, and outdated tech stacks, and explains how a three‑layer modular design, dependency‑injection container, componentization with San, and optimized server‑side rendering were employed to improve scalability, maintainability, and page performance.
This article examines the evolution and challenges of large‑scale front‑end architecture, using Baidu's search result page as a case study to illustrate problems such as massive codebases, unclear responsibilities, and outdated tech stacks, and describes a three‑layer modular, component‑based solution with SSR and DI to improve maintainability and performance.
The article defines componentization (shared JAR) and serviceization (independent service), compares their performance, cost, maintainability, and resource trade‑offs, outlines ideal use‑cases such as high‑throughput, no‑DB calls versus DB‑access or lower‑concurrency needs, and provides Vivo case studies to guide selection.
Facing sluggish Gradle builds for a large Android news app, the team applied componentized compilation, Artifactory caching, minimal compile mode, parameter tuning, and remote compilation via SSH, achieving up to 90% faster non‑incremental builds and 75% faster incremental builds while maintaining stability across the CI pipeline.
The article examines the evolution and challenges of frontend architecture through Baidu’s mobile search case, identifies problems such as vague responsibilities, tight coupling, and legacy stacks, and proposes a three‑tier solution—infra, independent modules, and componentization—implemented via server‑client designs, a Molecule interface, DI container, SSR optimization, and cross‑platform strategies to enable flexible upgrades and business agility.
This article details how iQIYI Knowledge's web frontend team designed and implemented a comprehensive componentization strategy that improves code reuse, development efficiency, and maintainability across numerous independent projects while ensuring product consistency.
The iQIYI Knowledge Web front‑end team built a developer‑oriented component library that splits UI and business logic into reusable basic and business Vue components, enforces clear input/output contracts, uses on‑demand loading and Storybook documentation, achieving high code reuse, maintainability, and consistent UI across independent projects while tackling bundle size and CI/CD challenges.
This article explains how to transform a large Android project into a componentized architecture by modularizing code, configuring Gradle for independent debugging, using ARouter for page navigation and service communication, handling fragment instances, distributing Application lifecycle events, and migrating legacy projects.
To enable Objective‑C and Swift mixed programming in Baidu App, static libraries are converted to static frameworks, module stability is activated, headers are module‑ized and dependencies declared via EasyBox, allowing safe inter‑component calls, proper nullability handling, and encouraging broader Swift adoption across the codebase.
This article outlines Zhenkun's mobile engineering journey from 2020 to 2021, detailing the shift to componentized architecture, the adoption of Flutter hybrid development, CI automation, and real‑time monitoring to boost development efficiency and product quality.
iQIYI Knowledge implemented a three‑layer componentization architecture—base, functional, and business components—combined with protocol‑based service registration, URL routing, and an automated build pipeline, enabling cross‑platform code reuse, independent testing, and faster integration while reducing coupling and maintenance overhead.
The DeWu Android team transformed a rapidly expanding, tightly‑coupled codebase into a modular, stable, and efficient architecture by introducing componentization, CI/CD pipelines, DevOps practices, and reusable services across three evolutionary stages, ultimately delivering business value through open‑source libraries, streamlined processes, and improved developer productivity.
This article explains the principles, advantages, and step-by-step process of component-based development, covering business modeling, software requirements, system and technical design, implementation, and integration within modern microservice and SOA architectures.
The Youzan mobile order module was refactored by separating UI views, turning the monolithic fragment into a ViewModel‑driven architecture, introducing a dynamic router for flexible navigation, and modularizing card components with independent view models, resulting in lower coupling, easier extensions, and a clear gray‑release strategy.
This article details the redesign of the 58 APP Android home page (version 9.0), covering overall UI and data module architecture, component design inspired by fragments, handling of search bar animations, fling behavior, performance optimizations, and lessons learned from the development process.
This article examines the policy-driven rise of internet hospitals in China, compares centralized and decentralized deployment models, and explains how JD Health’s component‑based Aries platform standardizes and accelerates the construction of customized hospital‑grade tele‑health systems.
This article chronicles the step‑by‑step evolution of Android POS SDK integration at Youzan, from quick‑start direct SDK embedding, through componentized hardware abstraction, to slimmed‑down differential packaging, and finally to a clean AIDL‑based service‑APK architecture that reduces coupling, improves extensibility, and lowers maintenance overhead.
This article describes how Alibaba Cloud’s front‑end and marketing platform team tackled frequent urgent requests and front‑end bottlenecks by adopting component‑based development and intelligent Design‑to‑Code tools like imgcook, resulting in significant automation, reduced manual effort, and a scalable low‑code workflow.
This article recounts Tencent Online Education’s front‑end journey—from unifying a chaotic tech stack and adopting component‑driven development to exploring dynamic app solutions, building a Node.js service middle‑platform, embracing serverless, and crafting internal tooling—to share practical insights for scaling front‑end teams.
The article explains the challenges of growing codebases in frontend projects and presents componentization as a systematic approach to achieve modular, reusable, and low‑coupled code, improving development efficiency, collaboration, and maintainability for long‑term, multi‑team applications.
The article summarizes Zhu Qingjie’s presentation on JD.com’s core transaction platform, highlighting its massive scale, stringent high‑concurrency and high‑availability requirements, architectural strategies such as system splitting, caching and componentization, and the use of an autonomous decision platform to ensure rapid, reliable e‑commerce operations.
This article describes the redesign of a large‑scale Android instant‑messaging (IM) module, detailing the shortcomings of the original architecture, the new three‑layer framework, the split‑converter for parallel business‑line development, component‑based UI design, and the design‑pattern techniques used to achieve a maintainable, extensible solution.
The article examines modern frontend engineering by detailing its four‑stage lifecycle—development, testing, deployment, maintenance—and reviewing modularization of JavaScript and CSS, component‑based frameworks and Web Components, code and workflow standardization, automation tools, and a real‑world migration to ES6 modules, Rollup, CSS Modules, Jest, and CI pipelines.
This article explains how Alibaba’s Mobile Taobao homepage handles massive traffic and diverse user groups by using multi‑version isolation, component‑based architecture, dynamic layout updates, and a systematic flow‑operation loop, ultimately improving development efficiency and system stability for large‑scale e‑commerce.
Meituan’s iOS team introduced the CocoaPods sub‑command zsource, which extracts source‑file paths embedded in binary components’ DWARF data and automatically fetches the corresponding code, letting developers instantly replace a binary with its source for fast, source‑level debugging without rebuilding the whole project.
Gaode Map transformed its app architecture by fusing Android and iOS through C++ sinking, dynamic UI floating, and dual‑end alignment, introducing component‑based containers and a unified R&D middle‑platform, which turned a pseudo‑bus into a real bus, cutting build time, crash rate, and release cycles while enabling true parallel development and paving the way for a future feature‑team model.
The article details JD.com’s 618 shopping festival engineering, describing how componentized micro‑services, a unified data platform, and the Archimedes elastic scheduling system enabled billions of requests, real‑time data processing and seamless online‑offline integration without adding new server resources.
JD.com’s R&D team transformed its 618 and 11.11 promotion preparation from a six‑month sprint to a one‑to‑two‑month process by building a unified middle platform that combines component‑based technology and data services, enabling rapid, scalable, and cost‑effective retail operations across multiple scenarios.
This article describes how the Smart Train Ticket Android team adopted a componentization architecture—splitting base libraries and business modules, configuring independent and integrated builds, handling inter‑module communication, and solving manifest and multi‑flavor packaging challenges—to reduce coupling and dramatically improve build performance.
This article examines Android’s architecture—covering the Hardware Abstraction Layer, component‑based design, and interface layers—to show how these technical choices enable rapid hardware integration, flexible system evolution, and a robust foundation for modern mobile applications.
Meituan transformed its monolithic cash‑register apps into a component‑based architecture using WMRouter as the routing foundation and built a strongly‑constrained modular‑event message bus—leveraging annotations, generated interfaces, and LiveData—to ensure type‑safe, module‑scoped communication, improve code reuse, reduce coupling, and simplify maintenance.
WMRouter is an open‑source Android routing framework, originating from Meituan Waimai, that provides flexible URI dispatch and a ServiceLoader inspired by Java SPI, enabling component‑based navigation, dynamic registration, interceptors, singleton management, and decoupled communication for hybrid, multi‑module, and instrumented app architectures.
Andromeda is an open‑source Android framework that unifies local and cross‑process component communication by providing blocking IPC, a global event bus, remote callbacks, and a dispatcher‑based architecture, solving the limitations of existing single‑process routing solutions.
The article reviews the history of native Android development, describes the shift from small‑app architectures to static and dynamic componentization, examines hybrid and cross‑platform solutions such as WebView‑based, script‑DSL, and independent runtimes, and outlines future trends and strategic choices for mobile teams.
This article explains core microservice concepts—including componentization, modularization, centralized vs. distributed systems, and the architectural principles behind microservices—while comparing them to SOA and highlighting practical distinctions that help developers design loosely‑coupled, reusable services.
Meituan Waimai iOS achieved an 84 % code‑reuse rate across its standalone app, Meituan channel, and Dianping channel by progressively componentizing business logic into layered CocoaPods, flattening dependencies, using binary pods for fast builds, and employing a robust toolchain and coordination among PM, RD, and QA.
At the iQIYI Technical Salon in Shanghai, senior engineers from iQIYI, Ele.me, Mushroom Street and others shared practical advances in mobile componentization and webization, including Ele.me’s hierarchical Android modularization, the open‑source CC framework, iQIYI’s Qigsaw dynamic delivery and Utopia web‑SPA, LiteApp performance optimizations, and the Lynx cross‑platform framework, while inviting developers to join iQIYI’s R&D team.
JD.com’s review and share platform combines multi‑dimensional rating, text, image and video content with a modular middleware, MySQL/MongoDB/HBase storage, Solr search, Redis caching and a management backend, detailing its architecture, daily operations, component‑based design, scalability challenges and future enhancements.
This article explains how to build lightweight, reusable custom components in WeChat Mini Programs, covering the evolution from basic template imports to full‑featured custom components, the differences between import and include methods, component configuration, event handling, and popular third‑party frameworks such as WePY and mpvue.
京东游戏精灵 is a component-based game platform that enables businesses to rapidly develop and deploy interactive games by reusing pre-built modules, significantly reducing development time and costs while enhancing user engagement through features like red envelopes and rewards.
This article details how Youku rebuilt its Double‑11 live‑streaming platform with Weex, covering the overall architecture, component modularization, interactive feature support, gesture conflict resolution, screen‑rotation handling, video corner rendering, performance optimizations, and the impressive results achieved during the event.
This article explains the differences between WeChat Mini Programs and H5, details the custom runtime environment, demonstrates performance differences, shows how to wrap callback‑based APIs with Promises, introduces component‑based development, and integrates Redux for state management with code examples.
This article details Didi’s technical solutions for international ride‑hailing, covering the challenges of overseas map selection, roaming network optimization, and a modular SDK architecture that enables flexible map switching and component‑based development for Android apps.
Meituan's Hermes project demonstrates how a large‑scale front‑end team achieved better developer experience and maintainability by adopting front‑back separation, ES6‑based modular and Vue component architecture, automated build pipelines, local mock services, comprehensive monitoring, network and offline optimizations, and outlines future plans for server‑side rendering and service‑worker migration.
The Hermes project at Meituan‑Dianping re‑engineered its overseas vacation front‑end by separating front‑ and back‑ends, modularizing code with ES6, building a Vue‑based reusable component library, automating builds and testing, and optimizing page‑load performance through CDN caching, monitoring, and offline strategies, dramatically boosting developer productivity and user experience.
iQIYI’s iOS team replaced a mediator‑based component system with a registration‑driven engine, allowing independent development, hot‑plug module addition, server‑controlled launches, and full Open‑Closed compliance, while integrating CocoaPods, GitLab, and Jenkins for automated binary delivery and scalable modular architecture.
This article introduces JD's Aura component framework, detailing its origins, four foundational pillars, three supporting systems, key tools, SDK specifications, and the associated portal, CI, and management platforms that enable scalable Android componentization within the Avatar ecosystem.
This article examines the evolution of frontend development from basic library selection through simple build optimization, modularization, and finally to component‑based development and intelligent static resource management, highlighting engineering practices that improve efficiency, scalability, and performance for complex web applications.
The article outlines a comprehensive front‑end architecture for an internet‑finance development team, detailing how component‑based, configuration‑driven design, migration from PHP to Node, and shared services (FMS, AXE, SCENE) address frequent scenario changes, risk‑control requirements, and aim to boost development efficiency and product management capability.
This article details the QQ Membership front‑end team's performance, componentization, and continuous‑integration practices for hybrid H5 pages on Mobile QQ, covering challenges of load speed, development efficiency, high availability, and the solutions they implemented to keep page loading around one second.
This article explains why using Swift or mixed Swift/Objective-C for business logic in componentized iOS projects is discouraged due to ABI compatibility issues, dynamic library loading overhead, and development complexity.
This article explores how front‑end developers can break the cycle of endless revisions by adopting the right mindset, collaborating effectively with product and design teams, embracing component‑based thinking, and developing product‑centric skills that improve efficiency and quality throughout the development process.
This article details the transformation of the HULK private‑cloud platform's front‑end from a PHP‑based MVC system to a modern React SPA using webpack, Redux, SASS and code‑splitting, highlighting the motivations, architectural decisions, and performance benefits of the 3.0 overhaul.
This article outlines the rapid growth of Baidu Takeaway's operations backend, analyzes the limitations of the FIS‑based modular approach, describes the transition to React‑Redux componentization, and presents a third‑generation, model‑driven component sharing platform designed to reduce repetitive development and improve developer happiness.
This article explains how to build enterprise‑grade business components (BC) within a Service‑Oriented Architecture using Web services, OSGi modularity, and an Enterprise Service Bus, covering component models, granularity, loose‑coupling design, interface standards, and J2EE deployment patterns.
This article provides a comprehensive overview of the Avalon2 JavaScript framework, detailing its evolution from Avalon1, performance improvements via virtual DOM, componentization, non‑intrusive design, compatibility features, backend rendering capabilities, and related tools such as Arthur and mmRequest.
This article explains how the Athena toolset addresses growing frontend complexity by introducing standardized project structures, componentization, automated builds, and performance optimizations such as first‑screen rendering, on‑demand loading, resource tables, and static preloading, ultimately improving developer experience and page speed.
This interview with Didi’s iOS platform lead reveals how the app evolved from a simple MVC design to a modular MVCS/MVVM architecture, adopted componentization, tackled real‑time data challenges, and leveraged hot‑fix technologies to support rapid growth.
This article details a practical approach to constructing a large‑scale documentation platform using Athena’s front‑end tooling, component‑based EJS templates, and a three‑state fixed navigation system, while also discussing the pitfalls of over‑modularization and alternative conversion methods.
This article summarizes a March 10 technical session on componentizing iOS and Android applications, describing the challenges of monolithic codebases, the benefits of modular architecture, communication patterns, lifecycle management, version control, CI integration, and practical lessons learned.
In this talk, Alibaba wireless expert Xu Zhao outlines the evolution of the massive Mobile Taobao app—from early webview tools to a component‑based, containerized architecture—detailing challenges such as PC‑mobile migration, device fragmentation, heavy client complexity, and the strategies employed to achieve scalable, flexible, and high‑performance mobile services.
The article recounts a Chinese company's evolution from an IE‑only HTC‑based UI stack in 2007 through a Flex‑driven heavyweight solution and finally to Angular, highlighting the technical, organizational, and strategic challenges of adopting component‑based front‑end architectures across multiple browser generations.