Local-First App Platform

Browser-based apps became the default deployment target, but browsers carry real CPU and memory overhead native apps don’t. Cloud-hosted apps solve that but require accounts, lose data if the service shuts down, and send everything off-device. Native desktop apps avoid both problems but demand real UI engineering — a genuine barrier for someone who’s strong on data modeling and logic but not on interface design. Nothing lightweight and privacy-respecting currently treats UI as optional rather than a prerequisite.

The idea: self-contained app bundles that are really just a data schema plus optional logic and optional custom UI. A native runtime reads the schema alone and auto-generates a working form-style interface — so a developer can ship something usable by providing only a data model. Custom UI can override the default but is never required. A first version would be a narrow proof of concept: can a schema alone really generate a form good enough to be useful, before any of the more ambitious later ideas (a personal data model shared across installed apps, composable app orchestration) get anywhere near real investment.

Two eventual audiences: privacy-conscious people who want their apps local and offline-capable, and developers who can model data but don’t want to build a UI from scratch.