Unit 20 · Language valence: Rust under policy · q27b

**Gut Reaction:** This is a "resume builder" project, not a product launch. You are fighting the ecosystem, the hardware, and your own architecture simultaneously. Rust is excellent for the backend and core logic, but forcing it to be the *sole* UI layer for both desktop and mobile while handling 3D rendering and plugin systems is a massive over-engineering trap. You will spend 80% of your time fighting winit/egui/tauri limitations and 20% building features. **Top 3 Technical Risks:** 1. **The UI/3D Convergence Nightmare:** Rust lacks a mature, unified, high-performance UI framework that seamlessly integrates with 3D viewports (WGPU/Vulkan/Metal) across desktop and mobile. You’ll likely end up stitching together `egui` or `iced` with a custom WGPU renderer. This creates a brittle abstraction layer where UI state and 3D state desync, leading to janky performance and complex synchronization bugs. Mobile support in Rust UI frameworks is (greedy generation)

**Gut Reaction:** You just turned a "hard" project into a "hostile" one. 120 FPS on mid-range Android in Rust is not a UI problem; it’s a thermal and memory management problem. The "cheap Linux CI" constraint means you cannot rely on native cross-compilation toolchains for Android (NDK) or iOS in your CI pipeline without massive caching overhead. You are now optimizing for the lowest common denominator of mobile hardware while maintaining a complex plugin system. This is a performance trap. **What Breaks First:** **The Plugin System + UI Thread Bottleneck.** End-user scriptable plugins (likely Lua, Python, or a custom DSL) will run on the main thread if you’re not careful. On mid-range Android, any frame drop below 8.3ms (120 FPS) causes stutter. If a plugin does I/O, heavy computation, or even GC pauses, your 3D viewport will tear. Rust’s async runtime won’t save you if the plugin execution blocks the render loop. ** (greedy generation)