Snappware apps are reshaped by conversation. Open the chat bubble in the corner, say what you want in your own words, and the app rebuilds itself while you're looking at it. No code editor. No project to set up. Nothing to publish.
Every version of your app is kept. If a change makes things worse, pick the moment you liked and restore it — one click, no jargon, nothing overwritten. Nothing is ever deleted to make room for something new.
Snappware apps live inside Safari today, and they don't all have to be pages. Ask for the shape that suits the task.
Through conversation alone it became an overlay on ⌥⇧1: start typing and every open tab filters down, most recently used first, Enter switches. It works over any page.
Halfway through, the app needed abilities Snappware didn't have yet — switching tabs, knowing which ones you'd used lately. Those were added, and the app absorbed them. The product grew to meet the app.
Snappware is in internal beta. Join and we'll build your first app with you.
Join the betaInstall a small app that does one thing well. Then tell it what to do differently. Every install is a fork you own — describe a change in the chat bubble and it rebuilds itself, in place, for you only.
Snappware is in internal beta. macOS and Safari today, your own AI provider key today. No pricing yet — just early access.
A resident engine in your menu bar runs the agent, the build pipeline and storage. Apps you talk into existence reach tabs, cookies, storage, screenshots and windows through a safe broker — including truthful most-recently-used data the engine maintains itself. No editor, no project, no deploy.
Type to filter every open tab. Most-recently-used ordering from real engine data, not guesswork. Enter switches. Works over any page, including ones that block extensions' UI.
No editor was opened. No file was saved. The two capabilities it needed were added to the broker and the app picked them up in place.
Point Snappware at Anthropic, OpenAI, Google or xAI. Today you bring your own key, which means your usage is your business and your model choice is a setting, not a lock-in.
Rebuilds don't overwrite. Every version of an app stays addressable, so restoring is a pointer move, not a recovery job. No data loss by construction.
internal beta · macOS + Safari today · your own provider key today · Chrome and Firefox on the roadmap · no pricing yet
A single resident runtime lives in your menu bar — agent, build pipeline and storage in one signed Mac app. Everything else is a thin shell attached to it. Today that shell is Safari. Next it's a desktop window, then background services. The apps you make don't get rewritten when the shell changes; they move.
A Snappware app starts small on purpose. It grows in the direction you push it, and when it needs a power the platform lacks, the platform grows too.
Storage is append-only, so a rebuild adds a version instead of replacing one. Restoring is choosing an earlier moment, in the app's own words — never a repository, never a merge. No data loss by construction.
Each shape is a shell contract, not a rewrite. When desktop windows land, an app can take that shape too.
Snappware is in internal beta. One notarized file, a menu-bar engine, and apps that change when you ask.
You work around their decisions all day. The field you don't need. The step you always repeat. The button that moved last Tuesday because a roadmap somewhere said so. You've stopped noticing, the way you stop noticing a stone in your shoe.
Snappware apps take your side. They are made of conversation, so they answer to you: say what's wrong and the app in front of you changes. And because every version is kept, saying "put it back how it was" is a sentence, not a support ticket.
One signed file. A small engine settles into your menu bar and waits. There is no code editor, no project to name, no deploy step, nothing to learn before you start.
Lower right, where you'd expect help to be. Except it doesn't answer questions about the app — it rewrites it. Say the sentence, watch the thing change.
Versions accumulate instead of replacing each other. Restore is choosing a moment you liked, in plain words. Point-in-time restore is coming.
Through conversation alone it became a Spotlight-style switcher on ⌥⇧1: type to filter every open tab, most recently used first, Enter switches, over any page.
Then it asked for something Snappware couldn't do — switch tabs, know which ones you'd used lately. So those became part of the engine, and the app absorbed them. The product grew because one person's tool needed it to. That's the argument on this page, in one story.
Whichever shape it takes, the app gets the browser's real abilities through a safe broker — finding, switching, opening and muting tabs, live tab events, screenshots, cookies, storage, window control, and honest most-recently-used ordering the engine keeps for itself.
Tell us the small thing your software refuses to do, and we'll build your first Snappware app with you.
Join the beta