The Magic Behind Cubacadabra

summary

To avoid the maintenance nightmare of duplicating application logic across iOS, Android, and web platforms, cubacadabra uses a shared Rust core that manages all portable logic and state. By treating native platforms as thin shells that only handle UI and device-specific services, the developer ensures that business rules and game engine behavior are implemented once and remain consistent across all clients. This architecture reduces bugs, simplifies updates, and allows the the product to scale without requiring coordinated changes across three different codebases.

key points

1. The system uses a shared Rust engine for critical logic like multiplayer sessions and account management, while native hosts (Swift, Kotlin, JavaScript) only handle the visual interface and platform-specific APIs.
2. A structured communication pattern where Rust emits 'effects' and the native host executes them ensures that the meaning of requests remains shared while the technical execution stays native.
3. The engine leverages wgpu for cross-platform rendering and a data-driven 'morph' system to allow asset updates and character customization without needing to modify the core engine code.

who should read it

Software architects and game developers interested in cross-platform development, Rust integration, and reducing code duplication across mobile and web environments.

discussion skeptical