Lofigui Research
Design philosophy, trade-offs, and technical deep-dives.
Research Pages
| Page | Description |
|---|---|
| Philosophy | Design philosophy, the interactivity spectrum, and where lofigui sits |
| Charts | Charting options — Go SVG vs JavaScript libraries |
| Layouts | Page layout complexity progression — single page to three-panel |
| Technical | Architecture overview, polling mechanism, task scheduling |
| Bugs | Known bugs, interaction analysis, and root causes |
| Python | Python implementation — API reference, installation, development |
| WASM Service Workers | Go WASM in service workers — routing, HTMX, static hosting |
| WASM External APIs | Calling external HTTP APIs from a WASM service worker — routing loop, CORS, JS proxy patterns |
| WASM TinyGo | TinyGo for WASM — blockers, compression as alternative, research proposal |
Overview
lofigui is for single-process, small-audience tools. The sweet spot: 1-10 users, one real object (a machine, a simulation, a long-running process) with a few pages showing different views of it.
Web applications sit on a spectrum from static sites to full SPAs. lofigui covers levels 2-4 (static+forms through HTMX partial updates). See Philosophy for the full interactivity spectrum.
Layout progression
| Layout | Built-in | Use case |
|---|---|---|
| Single page | LayoutSingle |
Quick tools, WASM apps |
| Header (fixed) | LayoutNavbar |
Dashboards, monitoring |
| Three-panel | LayoutThreePanel |
Multi-page apps, CRUD |
See Layouts for details and examples.