Stop Blindly Copying Flutter: The Four Cost Ledgers That Decide Cross-Platform Architecture in 2026
The analysis gives Western teams a concrete framework for cross-platform decisions, especially when China's mini-program and HarmonyOS ecosystems enter the picture. It shows why "shared code" is a red herring and makes the case that any project with real hardware needs a native layer from day one, no matter which framework is chosen.
A detailed 2026 cost analysis for Android, iOS, and mini-program architecture selection argues that the "one codebase, three platforms" promise is usually a trap. The real decision is where you draw the cross-platform boundary — UI, business logic, or full compile-to-everything — because each changes how the four ledgers (custom components, hardware, performance, maintenance) are calculated.
The article systematically compares Flutter, React Native, Kotlin Multiplatform, and mini-program frameworks (uni-app, Taro, containers) across each ledger. Key findings: hardware SDKs (only `.aar`/`.framework`) force native modules anyway, so framework choice becomes secondary; the performance gap between major frameworks has narrowed to within 10% of native, making hot-reload quality more important than engine speed; and React Native's breaking-change history is its biggest long-term cost, mitigated by Expo.
The author's conclusion is to avoid committing to a single framework and instead adopt a five-layer architecture (design tokens, pure logic in Kotlin/TS, platform capability abstraction, per-platform UI, and native hardware layer). This lets each layer be decided and replaced independently. The article also treats HarmonyOS as an unavoidable fourth platform in China, warns against betting on early third-party multi-platform frameworks for it, and provides a quick-reference table for selection based on team background and hardware requirements.
The post's central claim that hardware inevitably forces a native layer effectively neutralizes most cross-platform selling points for any project with serious device integration; teams should verify this before evaluating UI frameworks.
The comparison of code reuse expectations (30–50% normal, 60% good, 70% means compromise) is a useful sanity-check metric that senior engineers can apply to any vendor's "one codebase" pitch.
The author's layered architecture (design tokens, pure logic, capability abstraction, UI, native) is not new, but applying it to the China-specific constraints of mini-programs and HarmonyOS gives it a practical edge that generic cross-platform advice often misses.
The claim that Flutter's hot reload is more valuable than raw performance reflects a shift in the cross-platform debate: the bottleneck for most teams is iterative debugging, not runtime speed.
The article's treatment of HarmonyOS as a separate platform with its own maturity risks suggests that the Chinese market is effectively forcing teams to bet on either official (ArkTS) or community-led (KMP) paths, and that third-party universal frameworks carry high uncertainty in that context.
We're all going AI now, why bother with unified development? Just do native development everywhere. That way, for AI, it's actually easier — each side decoupled, no conflicts.
But in reality, managers who don't understand pretend to know, then blindly direct the experts below to achieve their own goals, like having Android implement a feature that already exists on iOS and also keep performance consistent [facepalm]
For consistency, an HTML wrapper is the ultimate answer.