Quorum Manifestation: the path from imagination to a deployed, federated app, in dialogue between humans and language models.
01Brainstorming
From pure imagination to mockup screens, quickly. Existing sites and references bootstrap the look; the aim is not to linger, because hallucinated mockups don’t feel real and upfront specs run into real constraints during development.
Go big first, design the ultimate version, then find the vertical slice to build: the MVP. Any real design elements become sacred patterns the code reuses.
02Prototyping
Proton Switch, a Rails app that turns HTML mockups into live, templated web apps with real logins and uploads. A frankensite, never the real app, but a more realistic lump of clay for working out the app’s flows.
03Building the backend
WWWW: WUIs in Wails with Wanix.
A WUI is a web UI that leans on the backend for application logic and template rendering, using JavaScript sparingly for plumbing. Closer to building web apps in the early 2000s, updated with modern technology and scaling lessons.
The application is written in one optimal, human-maintainable language. Go, designed for federated network services, with Datastar on the frontend and Wails for simpler apps. The goal: the Quorum app, its end-to-end-encrypted sibling, and Garden, all on the same composable framework.
04Refining the frontend
No single environment covers the full stack: live streaming events on the website, and mobile and native apps for music and video. Web Components with their own channel can sit inside a Datastar page; Buds needs a native or cross-platform UI that talks to Quorum as a sidecar.