Building a Zero-Login, Ephemeral Chat App with Vue.js and Supabase (feat. QR Invites)
Hey Dev Community! ๐ Have you ever wanted to share a sensitive message, a quick file, or a photo with someone, but hesitated because it required creating an account, sharing your phone number, or leaving a permanent dig
Hey Dev Community! ๐
Have you ever wanted to share a sensitive message, a quick file, or a photo with someone, but hesitated because it required creating an account, sharing your phone number, or leaving a permanent digital footprint?
I've been working on a solution for exactly this. Meet Private Pair โ a temporary, zero-login chat app designed for maximum privacy.
๐ ๏ธ The Tech Stack
- Frontend: Vue.js
- Backend / Auth: Supabase (Anonymous Auth & Realtime DB)
- QR Generation:
qrcodelibrary (Client-side only, no external API)
๐ The New Feature: Instant QR Invites
Initially, users had to share an 8-digit PIN manually. While that's secure, it's not always frictionless. So I added a dynamic QR code feature.
(เช
เชนเซเช เชคเชฎเซ เช
เชชเชฒเซเชก เชเชฐเซเชฒเซ เชซเซเชเซ เชเชตเชถเซ)
How it works under the hood:
- The host clicks "Create a PIN room".
- Supabase generates a temporary room ID and a PIN.
- Vue generates a QR code encoding an absolute URL (e.g.,
https://yourdomain.com/private-room?pin=88994766). - When the guest scans it, the app reads the URL parameter, authenticates them anonymously via Supabase, and triggers the
join_private_chat_roomRPC. - The guardrail: The auto-join function is designed to fire only once per session to prevent spam and handle manual PIN entries gracefully.
๐ Why "Zero-Login" matters
When building this, I asked myself: "What does an account get you that a PIN doesn't?"
The answer is usually: data liability.
By using Supabase's Anonymous Sign-in, we don't collect emails, passwords, or phone numbers. The room is ephemeral. Messages and images are routed through a system that self-destructs after 24 hours. Even the image compression happens client-side before uploading to keep the payload small and secure.
๐ง Challenges Faced
- State Management: Ensuring that the real-time websocket connection doesn't disconnect when the user navigates away or switches tabs.
- Auto-join Logic: Preventing duplicate RPC calls when the page reloads while the invite URL is still in the address bar.
๐ฎ What's Next?
I'm currently exploring WebRTC to add peer-to-peer Video and Voice calling capabilities. The goal is to allow two people to talk face-to-face without a central server recording the stream.
I'd love to hear your thoughts on this! Would you use a chat app that relies purely on QR/PINs and disappears in 24 hours? How would you have implemented the auto-join logic differently?
Originally published by Dev.to WebDev. Aggregated on AIWithGhost for educational purposes โ full credit and traffic to the original publisher.
