Lumos Hybrid Stack: A Cross‑Platform Solution to Boost Mobile Development Efficiency

Background : As the business scenarios of the HaLo mobility platform expand, the demand for mobile development has grown. The team seeks to improve development efficiency by using a cross‑platform engine that allows business logic to be written once and run on both iOS and Android, reducing duplicated effort and shortening debugging time.

Current Situation : Many features such as in‑app push handling, message filtering, payment decision logic, and login flows are implemented separately on each platform, leading to roughly double the manpower and higher error probability.

Lumos Hybrid Stack Efficiency Solution : By adopting Dart as the cross‑platform language, the team can share business logic across iOS and Android. The key benefits are:

Only one implementation for the same business scenario (person‑day reduction *1).

Consistent design ensures robustness, extensibility, and reusability.

Unified implementation simplifies troubleshooting.

Decouples business logic from UI, reducing tight coupling.

The name “Lumos” is inspired by the illumination spell in *Harry Potter*, symbolizing a brighter future.

Solution Design

Architecture (business view) :

Business UI – developers focus only on UI for both platforms.

Lumos Business Logic – provides a unified communication protocol, data format, and extensible common capabilities.

Supporting Tools – reuse existing CI pipelines.

Monitoring Platform – performance and log monitoring for runtime issues.

Sequence Diagrams :

Native calls Flutter:

Flutter calls Native (reusing existing native capabilities):

Performance Monitoring & Exception Capture

Method call efficiency – sampled monitoring of API entry points.

Data transmission efficiency – layered evaluation based on data size, attribute count, and length.

Memory & CPU usage – leverage Flutter APM to track changes caused by Lumos.

Exception capture – use Flutter APM to report and respond to runtime errors.

Communication Protocol

The protocol follows the pattern action/moduleName/methodName . Example definition:

action moduleName methodName                        (Lumos定义）

__|__   __|__   ____|__

/     \ /    \  /         \

action:/login/getUserName/

Parameter table:

Field

Type

Example

Required

Note

action

string

action

Yes

Fixed

moduleName

string

login

Yes

Target module

methodName

string

getUserName

Yes

Target method

Practice

Frequent‑iteration modules such as User Platform and Payment Platform benefit greatly from the Lumos container, enabling rapid iteration with minimal validation cost.

Technical Architecture includes:

Dart text, parameters, callbacks, error handling, and data models as input.

Communication protocol between native and Dart.

Common capabilities (network, data conversion, timers) wrapped in Dart.

Container capabilities for parsing, state management, model conversion, and callbacks.

MethodChannel for cross‑platform communication.

FlutterEngine shared across UIEngine to reduce resource usage.

Case Studies (efficiency statistics):

Order Center refactor – 6 person‑days saved (100% efficiency gain).

Message Platform IM push – 6 person‑days saved (60% efficiency gain).

Various ratios of logic vs UI development show 25‑50% reduction in effort when using Lumos.

Including integration, testing, and instrumentation phases amplifies the efficiency gains.

Future Outlook

Lumos will evolve beyond logic sharing to become a centralized state‑management hub, handling domain data, workflows, and rules. By encapsulating state transitions, the system can operate independently of the presentation layer, enabling clearer app architecture and faster, higher‑quality iterations across platforms.

The End