Vibeapp

Share apps like files

[Vibeapp @dotvibeapp]

For prototypes, demos, and internal tools that need to leave your laptop.

https://t.co/8i05x9tEQV

[Vibeapp @dotvibeapp]

AI can now build the app. The bottleneck is handing someone a thing they can actually run.

Vibe turns an AI-built app into one shareable .vibeapp file: double-click on Mac, no repo clone, no terminal, no dev stack.

[Vibeapp @dotvibeapp]

https://t.co/80HxtIe9BK

[Vibeapp @dotvibeapp]

AI made it much easier to build a working app.
The next bottleneck is sharing it.

A generated prototype still often needs a repo, env setup, terminals, package installs, ports, and “it works on my machine” debugging before anyone else can try it.

[Vibeapp @dotvibeapp]

Vibe is for that handoff: package an AI-built app into one .vibeapp file, send it, and let someone open it on their Mac without setting up the dev stack.
Build with agents. Share like a file.

[Vibeapp @dotvibeapp]

@kmeanskaran Templates help a lot for production deploys. There’s also a lighter-weight path before production: package the prototype so testers or teammates can run it locally. That’s where Vibe fits: one .vibeapp file instead of a repo plus setup instructions.

[Vibeapp @dotvibeapp]

AI app builders are getting good at the first 80%: a working local prototype.

The last mile is different: package it, preserve state, sign it, and let someone open it without npm, Docker, env vars, or a README.

That’s what Vibe is for: AI-built apps as shareable .vibeapp files.

[Vibeapp @dotvibeapp]

I’m building Vibe: a Mac tool for sharing vibe-coded apps.

It turns a working app into a signed .vibeapp file someone else can open locally, without cloning a repo or deploying.

Repo: https://t.co/vm3GJyYcvZ

What’s hardest when sharing an AI-built app?

[Vibeapp @dotvibeapp]

@DamiDefi Shipping 10 apps with Claude Code is a real signal. Curious how you think about the handoff step: App Store, hosted web app, or local builds? From Vibe, we’re betting there’s a missing lane for AI-built apps that should be shared as signed local files, not always deployed.

[Vibeapp @dotvibeapp]

@fayazara This is a good direction. Skills help agents build the app; the next useful layer is helping agents package the result. We maintain a Vibe skill for creating/validating .vibeapp manifests so AI-built apps can become shareable local Mac app files.

[Vibeapp @dotvibeapp]

@iam_chonchol Exactly. npm run dev working is a great moment, but it’s not the same as something another person can safely open. That last mile is what we’re building Vibe for: package the working app into a signed local file instead of turning every prototype into a deployment project.

[Vibeapp @dotvibeapp]

AI can build a prototype fast. The hard part is getting it into someone else’s hands without saying “clone this repo, install these tools, set env vars, run three terminals.”
That’s what Vibe is for: package an AI-built app into one .vibeapp file, send it, and let someone open it

[Vibeapp @dotvibeapp]

@code_codeforge https://t.co/80HxtIe9BK

[Vibeapp @dotvibeapp]

@FlippedRay https://t.co/80HxtIe9BK

[Vibeapp @dotvibeapp]

@aryanlabde https://t.co/80HxtIe9BK

Share your vibe coded apps like files.
Open source.

[Vibeapp @dotvibeapp]

@pmitu https://t.co/80HxtIe9BK

Share your vibe apps with anyone as files.
Open source.

[Vibeapp @dotvibeapp]

@vercel Next time, instead of uploading your app to a third party, just share it securely as a file with your friends. Visit https://t.co/80HxtIe9BK

[Vibeapp @dotvibeapp]

you vibe-coded an app. now you want to send it to someone.

not deploy it.
not explain Docker.
not walk them through npm install.

Vibe turns it into one .vibeapp file they can open on a Mac.

open source. MIT licensed. try it: https://t.co/DOZGb3s8sI