From Von Neumann to Flutter: Tracing the Evolution of Cross‑Platform Development

1. Introduction

Since the invention of computers, the growing diversity of platforms and terminals has driven a strong demand for cross‑platform applications. This article reviews the historical evolution of cross‑platform development and analyzes the design ideas behind current mainstream solutions.

2. Programming Languages and the Von Neumann Architecture

The first computer, ENIAC, led to the Von Neumann architecture, which stores program instructions and data together in memory and executes instructions sequentially. Early programmers wrote machine language directly for hardware.

In the 1950s, assembly language emerged to improve productivity, but it remained hardware‑specific. The first high‑level language, Fortran (1957), introduced hardware‑independent abstraction. Compilers split into front‑end (lexical, syntactic, semantic analysis) producing an architecture‑neutral intermediate representation (IR) and back‑end (optimization, code generation) that translates IR to target machine code, enabling portability.

2.1. About Abstraction

Abstraction extracts essential features while discarding non‑essential details. In computing, operating systems abstract hardware (processes, file systems, drivers, sockets), and object‑oriented classes abstract real‑world entities. High‑level languages abstract away instruction‑set differences, allowing the same source code to run on multiple architectures.

Cross‑platform development essentially leverages abstraction to hide differences between platforms.

3. Web Becomes the Mainstream Cross‑Platform Medium

From the 1990s, browsers became the universal carrier for HTML, CSS, and JavaScript. Standardization eliminated compatibility problems, making the web a natural cross‑platform environment. Rendering engines (Blink, WebKit) and JavaScript engines (V8, JavaScriptCore) provide platform‑independent interfaces, though performance and functionality limitations remain.

4. Hybrid Development in the Mobile Internet Era

With the rise of smartphones, developers need to support both Android and iOS. Hybrid approaches embed a WebView in native apps, using frameworks like Cordova to expose native capabilities via JavaScript bridges. While cost‑effective, hybrid apps suffer from performance, capability, and security drawbacks.

5. The Rise of Mini‑Programs

Mini‑programs blend web and native advantages, offering richer APIs than pure web while remaining lightweight. Platforms like WeChat provide a container with a rendering layer (WebView) and a logic layer (JS engine). Cross‑mini‑program frameworks (Taro, uni‑app, morjs) use static compilation or dynamic adaptation to achieve “one code, many platforms”.

6. Native‑Centric Cross‑Platform Solutions

Frameworks like Flutter and Kotlin Multiplatform + Compose avoid WebView overhead by rendering UI directly with cross‑platform graphics libraries (Skia). Flutter compiles Dart to native code on mobile and to WebAssembly (CanvasKit) on the web, while Kotlin Multiplatform shares business logic across Android, iOS, and JavaScript, with Compose providing a unified UI layer.

7. Conclusion

The core of cross‑platform development is adding abstraction layers that hide platform differences and expose uniform interfaces. Choices of UI language, logic language, abstraction point, rendering engine, and execution model lead to various solutions—React Native, Electron, Taro, Flutter, Kotlin Multiplatform, etc. Selecting the right tool balances user experience, consistency, and development cost; there is no universal silver bullet.