Cubacadabra to unify iOS, Android and web apps around a shared Rust core
Cubacadabra's developers plan to rebuild the product's iOS, Android, and web clients as thin native shells that delegate application logic to shared Rust crates rather than reimplementing features separately in Swift, Kotlin, and JavaScript. The goal is to move business rules like form validation, save logic, and error handling into one Rust codebase that all three platforms call into, citing Litter's Rust-core approach with UniFFI bindings as a precedent.
GoKawiil's interpretation of the reporting above, not reported fact.
Maintaining three separate implementations of the same logic causes behavioral drift between platforms as bug fixes and features land inconsistently across teams and timelines. Centralizing logic in Rust reduces duplicated engineering effort and makes cross-platform consistency a structural guarantee rather than a coordination challenge, a pattern already validated by other cross-platform apps.
- Cubacadabra will move core application logic into shared Rust crates instead of duplicating it per platform.
- Native UI layers in Swift, Kotlin, and JavaScript will remain but only handle platform-specific rendering and device integration.
- The approach follows precedents like Litter, which uses a Rust core with UniFFI bindings for iOS and Android.
Programming Rust" by Jim Blandy (O'Reilly) — If the article's pitch of collapsing three codebases into one shared Rust core sounds appealing, this O'Reilly guide is the standard deep dive into the language's ownership model, traits, and concurrency. It's a great companion for anyone building a cross-platform core that iOS, Android, and web clients can all wrap thinly.
See Programming Rust" by Jim Blandy (O'Reilly) on Amazon → Affiliate link — we may earn a commission on purchases, at no extra cost to you. Product picked by AI based on this article; it is not a tested recommendation.Source: andrewarrow.dev, 2026-09-10
Published there as: “The Magic Behind Cubacadabra”
Read the original report → The summary and analysis above are GoKawiil's own, written from reporting by the source above. Facts and quotes belong to the original publisher.