I've been working on an idea and I'd like to know if it's useful or just a nice metaphor.
You don't ship a person, you ship a genome, and the same genome grows differently depending on where it lands. DNApps tries the same with software. A capsule is one text file that says what the app does, which decisions are fixed and which can adapt, and the order to build it in. You hand it to a coding agent (Claude Code, Codex, Cursor) and it grows the app in your environment: whatever language, OS and devices you're on, your preferences, and the hosting you already pay for.
The second idea is the one I'm least sure about. A capsule works like a new kind of compression. Source code is text and zips fine, I know. But a capsule keeps what the app must be (the spec, the intent, the connections between parts) and drops how one copy happens to be written. My example, Plate, is a 15 KB capsule, and the app grown from it is 75 to 95 KB of code. That's about five times, on a small app. I don't know yet what happens on a big one.
It also means there could be several levels. A detailed capsule that pins the stack and deployment, and a much smaller one that leaves those out, because the agent can work them out when it reads what the app needs. You could even keep a finished app you no longer maintain as one file with its key decisions and structure, and grow it again later with whatever tools exist then.
So, honest question: is this a format worth having, or does it fall apart as soon as the app gets real? Have you seen something like it?
There's a one-page overview at https://meshkore.com/dnapps?ref=devto, and the spec itself is a v0.1 draft on GitHub, open for comments until January 10, 2027: https://github.com/asimovia/dnapps
I wrote this with help from an AI writing assistant, and the cover image was made with AI.
Top comments (0)