Capsule: "Documents That Run Like Apps" — Single-File SQLite Apps and the Portability-vs-Multiplayer Wall
Show HN (98 points): Capsule packs an entire app — HTML UI, schema, and its SQLite data — into one portable .capsule file. "No cloud. No accounts. Just share it." Send it over WhatsApp or AirDrop like a PDF; the recipient opens it in a Tauri-based host app (10MB on Mac, using the OS webview rather than bundled Chromium) and it launches with state intact. The pitch leans into the AI moment: prompt → complete self-contained desktop app, iterate via prompts or MCP coding tools. The creator's framing of the lineage is the Excel document: "a Excel spreadsheet is also just UI + data in a single file" — bashtian.
The core objection: stateful files don't multiplayer
The sharpest critique came from jawns:
"Any time the state changes, you need to email a new Capsule file to whoever else is using the app. And one would think the state would change at least occasionally, because otherwise there's little reason to use a DB." — jawns
The creator's answer defines the product's actual scope: this is for the personal document-like app — "You create a capsule, move it to an USB stick, save it in your cloud storage and it's still the same document. Nothing has changed, not the UI, not the data" (bashtian). latexr's rebuttal to jawns names the value being traded: "You're glossing over the recurring cost and annoyance of dealing with the hosting and having to secure the data. This way you just share and it's local." The use case that convinced the thread: "If try to do data management in Excel or need to download an app just to save some recipes, this could be an alternative" (bashtian) — and dgf18 spots the agentic angle: workflows too small to justify a maintained web backend, generated by the coding agents companies are already deploying.
The browser sandbox is the real antagonist
The thread's technical meat is why this product has to be a native app at all: Dwedit — "web browsers are downright lobotomizing the ability for local HTML files to run any meaningful javascript code. Want to run a JS file from the same directory? CORS ERROR!!!! Hence 200MB applications that are complete copies of the Chromium browser to run under 1MB of actual web code." yoz supplies the state of the art: the File System Access API can let a local HTML file persist into itself, but only in desktop Chromium — so every other browser is back to manual "Save" buttons. The security question was immediate ("This seems ripe for an injection attack. Can it be inspected before running?" — redog; one user's Mac download flagged as "damaged" — dzink), answered by the sandbox argument: the capsule HTML "does not have any permission to access anything on the file system" (bashtian).
Why it matters
Capsule is the newest entry in a lineage the thread itself named — TiddlyWiki, Lotus Notes, MS Access, "So, let's do Visual Basic again, but this time with LLMs and web stuff" (fdeth). It matters because it's a clean test of the local-first thesis (see Sovereign Infrastructure: Private Search, Local-First Smart Homes, and the Gatekeeping of Walled Gardens): the failure mode isn't technical, it's the sync boundary — the moment two people need the same state, the single file becomes a merge problem, and you've rebuilt a backend with worse tooling.