?
The problem
Event hosts usually rely on group chats, shared folders, or guests remembering to send photos later. That creates scattered media, missing moments, and no clear way to approve what gets shared.
Back to work
Event-Cam
A guest photo and video collection product where hosts create an event, share one QR code, moderate uploads, and publish a protected album.
Event Media PlatformProduct buildPublic product
Services
Product strategy, Guest upload flow, Payments, Media moderation
Stack
Next.js, Supabase, Stripe, Storage workflows
↗
What changed
We shaped the experience around one obvious action: create an event, give guests a QR code, collect uploads safely, then review and share the final album.
✓
What shipped
A public product with host accounts, event setup, guest QR upload, paid activation, upload moderation, private album controls, and email/payment handling behind the scenes.
Private details protected
Only the product flow is described. Real event names, guest media, invite links, payment objects, upload records, and private account data are not shown.
Solution timeline
- 1
Shape the host journey
Reduced setup to the few decisions a host needs before an event goes live.
- 2
Build the guest upload path
Created a low-friction QR flow so guests can upload from their phone without downloading an app.
- 3
Add payment and access rules
Connected paid activation, event windows, and protected album access so the product can run as a real service.
- 4
Harden the handoff
Tested uploads, moderation, email, and payment paths so the product is safer under real event pressure.
Safe public proof
This page talks about the build in plain English. It avoids sensitive data and uses anonymised framing whenever the real client system is private.
Ready to build something useful?
We can turn the messy version of the problem into a practical first build, then keep the private parts private.