The device is the wrong place for software to live.
A phone should be a sensor package and a pane of glass. Compute, state, memory, and intelligence belong on machines you control — where apps can be created, reshaped, and retired as fast as your life changes.
Ship one shell, once. After that, "installing an app" is just the server learning a new trick — and every screen you own gets it instantly.
A thin-client operating layer
Android WebView shell + FastAPI plugin hub + WebAuthn biometric auth + reverse-proxied edge, with a fleet of home-lab machines doing the heavy lifting.
33 server-side apps
Live transcription with speaker labels, AI receipt filing, voice navigation, a baby monitor, a call copilot, remote desktops, games, and a fleet-control brain — all tiles in one hub.
An AI that writes the apps
A built-in Claude build engine emits versioned file writes; the plugin registry hot-reloads and every connected device is told about the new app over WebSocket.
Where this goes
Why thin clients win the AI era: disposable apps, interfaces that reshape themselves per moment, and a managed "LumenBook" fleet model with a NIST-mapped control plane.
Engineering lessons
What a year of running your whole digital life through one hub teaches you about WebView bridges, foreground services, biometric auth, and versioning every write.
Operational evidence
Lumen runs daily as the author's primary phone environment: a ~2,000-line FastAPI hub, 33 plugin apps, 11 iterated APK builds of the shell, GPU speech/vision pipelines, WebAuthn fingerprint login, and a documented device-management protocol for thin-client laptops.
Portfolio-safe presentation
This case study uses representative descriptions and omits real hostnames, addresses, credentials, and private infrastructure details. Concept apps in the Vision section are clearly labeled as designs, not shipped software.