H
Architecture
How to Effectively Layer and Split Business Logic in Large React Native Projects
Horizontally layer by technical responsibility, vertically slice by business domain, then use an explicit assembly layer to connect the two.
25 min
Blog
#AI#AST#BFF#CSR#Component#Config Driven#D2C#Dynamic Rendering#Feature Composition#Flow Engine#Harness Engineering#Low code#MPA#Modular Architecture#Modular Design#Multi Instance#Multi Tenant#Protocol#React Native#SSG#SSR#System Design#TaskManager#Virtual Modules#Vite#feature-architecture
Architecture
Task Scheduling Architecture for Batch Downloads in React Native: TaskManager, Queue Layering, and Native Bridging
This article focuses not on the download interface itself, but on the task scheduling, state machine boundaries, and Native coordination behind batch downloads.
18 min
Architecture
FlowEngine: Decomposition and Orchestration of Complex Long Frontend Processes
The background of FlowEngine is to first manage the device addition flow in the existing app, while reserving a reusable scheduling model for other complex flows in the future.
18 min
H
Architecture
How Device Capability Set Affects Remote Configuration Page Rendering
The configuration tree offers a middle path: page structure is described by configuration, node dependencies are declared with `features`, business logic is placed back into fetch and interaction logic, and the rendering layer only consumes the final state.
18 min
W
Architecture
Why Is Another Layer of Feature Needed Under DeviceModule
This step addresses the first boundary: who should manage the device business entity, where its state should be read, and where business actions should enter.
17 min
Architecture
From Manager to Module: A Modular Transformation of a Complex React Native Business
From Manager to Module, the biggest change is not the class name, but the responsibility boundaries have been re-established.
20 min
Architecture
BFF: How Aggregation, Cross-Cutting, and Rendering Are Layered
View the page-oriented BFF as a server-side pipeline. Requests first pass through the static and module layer, then through site-wide middleware, hit a specific page for data aggregation, and finally the rendering template decides how to output HTML, stream, or CSR fallback.
17 min
Architecture
How to Prevent Multi-Merchant Systems from Going Out of Control: A Structured Approach to Managing Differences
Treat merchant differences not as scattered conditional branches, but as objects that need governance.
19 min
Architecture
Why We Abandoned the Component Library and Moved to a Page Platform
No longer "provide more components," but "provide a page production system." "Abandoned component library" is sensational; actually components become basic materials in the platform.
16 min