[verdict][curated prompt][source: snapchat.com]
Can I vibecode Snapchat?
// the value is the network, the data or the infrastructure
The mechanics one-shot fine: ephemeral photo messages, 24-hour stories and streak counters are CRUD plus a delete timer. None of that is the product. Snapchat is where your friends already are · the value of a disappearing photo is who is on the other end, and a self-hosted clone with two users is a group chat with extra steps. Add the AR lens stack built on years of face-tracking models, screenshot detection that needs OS-level app privileges, and media infrastructure moving billions of snaps a day, and the honest verdict is that the network is the app. The prompt below is the consolation build: a private snap relay for one friend group that opts in.
confidence: high
what it is: Camera-first messenger where snaps, stories and streaks disappear · the app is the friend graph
Buildability index · an editorial game
- Price 3.99 $/month weight: zero
- Time closest consolation build: one sitting weight: minus 1
- Category social media no weight
- Moat network effects · proprietary models · infrastructure scale weight: minus 6
- Confidence high weight: plus 1
- What you lose 5 items weight: minus 2
- Site snapchat.com (si apre in una nuova scheda) no weight
It is not close. The prompt below rebuilds a piece, not the product.
Gioco editoriale: il verdetto dice se un agente può, l’indice se conviene.
What you build
Snap a photo with a caption overlay and send it to an invited friend group; each snap deletes after one timed view, with daily streaks and 24-hour group stories.
what you need
- a small VPS or free-tier Node host with HTTPS (camera and push APIs require it)
- friends willing to install the PWA and actually use it
Comparison targets Snapchat+, the optional paid tier of a free app · recheck price before merge.
The prompt
The verdict is NOT REALLY, and the prompt stays anyway: it does not replace the app, it rebuilds the part that really is code. The rest is the moat.
Build me a private ephemeral photo-messaging app, snaps for one friend group that opts in. Requirements:
- Node 22 + Fastify + better-sqlite3, and a vanilla-JS installable PWA served from
/public with no build step: manifest, service worker, an offline shell that caches
the UI but never caches snaps.
- Core loop: open the camera with getUserMedia, capture a photo, type or draw a
caption overlay on a canvas, send it to one or more friends.
- A snap is viewable exactly once for up to 10 seconds; the server deletes the image
file immediately after the view and keeps only a minimal sent/opened log row.
- Accounts are invite-code only: the admin seeds codes with a CLI script, signup is
username plus passcode, sessions are httpOnly cookies.
- Per-pair daily streaks tracked server-side, shown next to each friend.
- Group stories: a snap posted to my story is visible to all members and hard-deleted
after 24 hours by a sweep job.
- Media lives as files on disk outside the web root; metadata in SQLite with WAL mode.
- Web push for new snaps behind a permission prompt; the app must work fully without
it, and the README says iOS web push is best-effort. VAPID keys and session secret
in .env, with a documented script that generates them and a .env.example.
- HTTPS is required for camera and push: document local dev with a self-signed cert
and production behind Caddy on a cheap VPS.
- Be honest in the UI: label view-once as deleted from our server, and state plainly
that screenshots cannot be detected on the web.
- Tests for delete-after-view, the 24-hour story sweep, and streak day-boundary math
with a fake clock.
- Out of scope: AR lenses and face filters, Snap Map, Discover or Spotlight feeds,
video calls, screenshot detection, analytics, and third-party auth.
- README: setup, deploying, where data lives, how deletion actually works, and how
to invite the first two friends.Curated prompt: written and reviewed by hand for this app. In English on purpose — it is the language coding agents work best in.
What you lose
- the people: everyone you snap with is on Snapchat, not on your server
- AR lenses and filters backed by years of face-tracking models
- screenshot detection · a web app cannot see or stop screenshots
- Snap Map, Discover, Spotlight and the creator ecosystem
- reliable mobile push · web push on iOS is best-effort, not messenger-grade
Why people still pay
Almost nobody pays for Snapchat itself · the app is free and the subscription sells cosmetics and vanity telemetry: pin a #1 BFF, see who rewatched your story, wear a badge. People pay 3.99 USD because the network underneath is where their friends live, and status inside a graph only matters in a graph with people in it. That is also exactly why a rebuild is pointless: you can clone every feature and you will have cloned none of the value.
moat: Network effects Proprietary models Infrastructure scale what a moat is
the graph is the product; lenses are frontier computer-vision models; snaps ride a global media pipeline
Who has already built it
Starting from here is still vibecoding: the prompt is for when you want it exactly your way.
- Signal (opens in a new tab) — open-source messenger with disappearing messages and view-once media, minus the social layer
- Pixelfed (opens in a new tab) — federated photo sharing with ephemeral 24-hour stories
Do you agree?
The vote balance
Ancora nessun voto: il tuo è il primo.
Nessun voto ancora — il primo pesa.
