Scaling Large Organisations: Empowering Independent Teams with Crux Micro‑Frontends
summary
Proton uses Rust and the Crux framework to put business logic into sharable Rust “cores” that run on iOS, Android, web and CLI while each shell provides native UI; Crux (0.17 imminent) has ~50 contributors and ~2.5k stars and enables pure testable cores, commands/effects pushed to the edge, and fast integration tests (24 tests run in 16 ms, a sync sync test in 7 ms). The demo composes a Lumo feature into Proton News via FFI-serialized types; teams adopt a monorepo and face serialization, build-system and mindset challenges.
AI-written summary · about
chapters (24)
- 0:00Proton and Crux intro
- 1:10Why Proton chose Rust
- 3:20Scaling independent teams
- 8:00Scalable solution needs
- 11:36What is Crux
- 13:24Crux architecture
- 16:59Crux app structure
- 19:24Async commands in Crux
- 21:50Testing Crux with confidence
- 23:59Scaling Crux across teams
- 27:40Composing team features
- 31:13Lumo feature in News
- 35:05Shell composition
- 39:19Crux benefits at Proton
- 40:23Adoption challenges
- 43:32Rust future at Proton
- 45:04Q&A: Render effects
- 46:53Q&A: Shell-core compatibility
- 48:57Q&A: Update bottlenecks
- 50:42Q&A: Legacy to Crux
- 52:30Q&A: Build systems
- 54:14Q&A: Cores and microservices
- 56:24Q&A: UI abstraction
- 57:51Q&A: Shell capabilities
related talks
29m"High-Level Rust and the Future of Application Development"
46mWrite once, run everywhere: building apps with Dioxus
30mDX in the frontend developer ecosystem
29mMicro Frontends, how to evolve to an extensible frontend
43mClosing Keynote
24mMicrofrontends
27mFacing Frontend's Existential Crisis
38mFrom Microfrontends and back