0 views collected around this technical thread.
The article presents a modular framework for Mobile Taobao that unifies data protocols, rendering, layout, and lifecycle management through core engines (DataEngine, LayoutEngine, StateCenter, etc.) enabling rapid, extensible construction and updating of dynamic UI pages across multiple protocol versions.
The article describes the design and development of a low‑code form generation platform built on VueFormMaking, detailing its drag‑and‑drop interface, JSON‑driven component architecture, template configuration and rendering, as well as maintenance practices such as flat configurations, style optimization, testing, and deep‑copy handling for scalability and reliability.
By adopting LiteFlow’s lightweight low‑code workflow engine with a workbench‑component‑rule architecture, the team replaced repetitive custom code with configurable pipelines, achieving high decoupling, flexible orchestration, reduced development cost, and improved extensibility for complex business processes, while planning a visual backend platform.
This article presents comprehensive Vue.js and Element‑plus coding standards, covering enum naming, directory and file naming conventions, component file structure, attribute and directive usage, boolean, function, class, constant, and enum naming rules, emphasizing consistency to improve readability and maintainability.
The article presents a comprehensive guide to large‑scale video‑streaming system refactoring, combining theory on continuous improvement, architectural evolution, code‑quality criteria, and challenges with a practical roadmap that leverages automation, systematic analysis, engineering safeguards, static‑analysis tools, and design patterns to safely transform legacy monoliths into modular, containerized platforms.
The article describes MPX’s partial runtime capability‑enhancement design, which adds modern web‑framework features such as props, default slots and event forwarding to Didi’s recompilation‑based mini‑program framework by enabling on‑demand runtime rendering for selected components, generating minimal base templates, respecting the native dual‑thread event model, and exploring server‑component‑inspired mixed rendering while keeping performance overhead low.
This article provides a systematic overview of drag‑and‑drop low‑code platforms, covering their advantages and drawbacks, core architecture (protocols, material area, canvas, property panel, top bar), implementation details with code examples, and best practices for extensibility, sandboxing, and code generation.
This article explains how the LiteFlow component-based rule engine is used to design, configure, and execute flexible lightweight inspection reports, highlighting its modular architecture, real‑time component management, data context handling, and integration with configuration centers to reduce development overhead.
This article explains the concepts, design of JSON configuration structures, component container patterns, editing side form generation, remote component store integration, static publishing, version management, and inter‑component communication for constructing a data dashboard platform using modern frontend technologies.
The article presents a comprehensive case study of Ctrip's 2022 PC homepage redesign, detailing the motivations, requirement analysis, island‑style architecture, cross‑team component development, server‑side rendering, public component challenges, and the dynamic data‑configuration platform that together enable fast, maintainable, and scalable web delivery.
The Yanxuan app home page has progressed from a layered native architecture using Tangram and TAC to a component‑based system with compile‑time cell registration and asynchronous loading, and finally to a VirtualView‑driven dynamic UI that enables fast, cross‑platform updates, improved performance, and reduced release overhead.
This article outlines the design, implementation, and open‑platform strategies of Ctrip’s Legao system, covering component openness, custom build processes, dynamic loading, development tooling, static libraries, and dynamic form capabilities to enable reusable, low‑code, SSR‑ready frontend components.
The article explains Web Components and their three core technologies—Template, Shadow DOM for CSS isolation, and Custom Elements—demonstrates building a dynamic HTML5 video component with lifecycle callbacks, and discusses use cases such as component libraries, cross‑platform development, micro‑frontends, and the feature‑rich Quark library.
The AirForce platform unifies component architecture, baseline and release management, and automated packaging for a large Android app, eliminating information silos and cumbersome configuration files by enforcing hierarchical dependencies, tracking component metadata, providing fine‑grained conflict detection, and enabling shuttle releases that streamline coordination, improve traceability, and reduce manual effort.
This article explains how to build an e‑commerce SaaS shop‑decoration system from scratch, covering overall design, template‑protocol structure, the three core designer tools—component selector, renderer, and property editor—and considerations for cross‑platform, dynamic components, user experience, ecosystem, and productization.
This article explores the inefficiencies in modern web development, focusing on collaboration challenges between UI/UX and frontend teams, data interaction issues, and code management difficulties, proposing solutions like component-centric development and improved data binding tools.
The article details the design and implementation of a dedicated pricing calculation engine that decouples complex e‑commerce promotion logic from transaction services, using componentized rules, configurable pipelines, multi‑level caching, and lane‑based simulations to achieve high extensibility, low latency, and accurate pricing across browsing and checkout scenarios.
The NetEase News iOS team adopted a three‑layer componentization strategy—foundation, common, and business—standardizing code conventions, Git workflow, and CI‑driven reviews, encapsulating third‑party libraries, managing dependencies via injection and mediators, and distributing binary pods, which reduced the main project to a single file while expanding reusable components to over 250, achieving low coupling and high cohesion.
The Activity Open Platform, evolved from the Activity Self-Service Platform, provides a company‑wide component sharing and co‑creation environment with standardized processes, cross‑team collaboration, and high scalability, delivering Pro‑code, Low‑code, and No‑code capabilities that have already boosted development efficiency by 40% across multiple departments.
This article presents a comprehensive experience of UI componentization in Android projects, covering the background, goals, engineering and component architectures, detailed implementation steps for reusable UI components such as FlatButton, and practical Gradle configurations to achieve modular, decoupled, and scalable UI development.