[ER] Architectural Refactoring Plan

[A-kua]

Engineering Modifications Proposal

Summary:
We need to implement several engineering modifications. The first priority is architecture decoupling, as the current architecture is insufficient to support our future development with multiple flavors.

Plan:
I propose splitting the codebase into three layers, from top to bottom:

• Shell Layer: Integrates different business domains. Applies flavor-specific changes such as package names, permissions, etc.
• Business Layer: Implements business features like mini-widgets, class schedules, online services, and top-up functionality.
• Common Layer: Provides foundational capabilities, such as network requests, network auditing, and security safeguards.

Dependency:
Successfully adopting this layered approach relies heavily on a robust SPI framework.

Call for Contribution:
If anyone has time, please provide an existing solution or consider authoring one.

Reference:
A feasible reference: https://github.com/yanglw/android-spi

[A-kua]

Oh, fuck the stupid Github.... 🔪
Every time I press Enter, it sends instead of creating a new line.

[A-kua]

20260105

New Ideas:

• Let arch be Rust as a service, RAAS.
• Maintain transparency, auditable.
• Privacy by design. Use system API with privacy friendly wrapper.

[A-kua]

For the interaction modules between HarmonyOS and Android with the Rust Server, we use KMP. For the interaction module between iOS and the Rust Server, we adopt a native implementation.
In other words, the Rust Server is cross-platform for three systems, while KMP is cross-platform for two systems. This technical architecture puts us on par with top-tier apps in the industry.

Division of labor

• Rust Server: @Yukon163 & @Can4ry
• KMP: Stub...
• iOS: @Kyant0