Can AI replace Snapchat?

NOT REALLY · don't bother

price $3.99/moyou'd save $47.88/yrbuild time closest consolation build: one sittingcategory 🐦 social mediareplaced by 0 peoplebuild unverified

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.

the prompt

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.

$ open in your agent (prompt prefilled, you press enter) or copy it raw

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.

what you lose

xthe people: everyone you snap with is on Snapchat, not on your server

xAR lenses and filters backed by years of face-tracking models

xscreenshot detection · a web app cannot see or stop screenshots

xSnap Map, Discover, Spotlight and the creator ecosystem

xreliable mobile push · web push on iOS is best-effort, not messenger-grade

prior art · use these instead of building, if you'd ratherSignalopen-source messenger with disappearing messages and view-once media, minus the social layer↗Pixelfedfederated photo sharing with ephemeral 24-hour stories↗