How nightcode42/plux3 works
Plux is a server-driven Flutter UI and plugin platform. The documented workflow is: teams author screens in Studio (or use the CLI), the server validates and compiles them into signed FlatBuffers bundles and deltas, and the Flutter runtime syncs and renders updates as native widgets. The README describes additional security, governance, and function capabilities, but this tree is at Phase 0 and sampled source does not show those implementations. Those branches are therefore shown as documented capabilities, not verified internal call paths.
Main entry points: backend Plux Server · plux_flutter Flutter runtime · studio Plux Studio · plux Plux CLI
Components 18
Authoring
- Plux Studio
studio - Plux CLI
backend/cmd/plux
Server delivery
- Plux Server
backend - Validation
backend - Bundle compiler
backend - Bundle signing
backend - Delta generation
backend - Shared contracts
schema - RPC contracts
proto - Bundle storage
Flutter runtime
- Flutter runtime
packages/plux_flutter
Platform capabilities
- Device security
packages/plux_flutter - Release governance
backend - Plux Functions
backend
Other components
- Product team
- Host Flutter app
- App user
- WASM compute
Connections 16
- Product team → Plux Studio: authors screens
- Plux Studio → Plux Server: sends documents
- Plux CLI → Plux Server: submits changes
- Plux Server → Validation: validates
- Plux Server → Bundle compiler: compiles bundles
- Plux Server → Bundle signing: signs bundles
- Plux Server → Delta generation: computes deltas
- Plux Server → Bundle storage: stores bundles
- Plux Server → Flutter runtime: serves manifests and deltas
- Flutter runtime → Plux Server: syncs with DPoP
- Flutter runtime → Device security: verifies updates
- Flutter runtime → Host Flutter app: renders widgets
- Host Flutter app → App user: shows UI
- Plux Server → Release governance: supports governed releases
- Plux Server → Plux Functions: runs functions
- Plux Functions → WASM compute: executes as WASM