Case study
CineCircle
Swipe through films together until you match. A web app that helps couples and friends decide what to watch tonight.
- Role
- Creator. Designed, built and shipped.
- Owned
- UX, Design system, Animation, Realtime backend, Deployment
- Stack
- Next.js, TypeScript, Framer Motion, Socket.io, Node.js, Express, TMDB API
- Status
- Live
Try itRuns in your browser with sample data
Anna1 of 5
Ben1 of 5
01 The problem
Two people, one evening, no decision.
Choosing a film together means scrolling separate catalogues and negotiating out loud. CineCircle turns it into something both people do at the same time, on their own phones, with the app telling them when they agree.
02 What I built
Rooms, swipes and a match.
One person creates a room and shares a code; the other joins. Both swipe through film cards independently, showing only films available on their own streaming services. The moment both like the same film: a match, with confetti and a direct link to watch it. No account needed, filters across seven streaming providers.
03 How it works
Create, join, swipe, match.
room.create()01 Create a room
One person opens a room and gets a short code. No sign-up, no friction.
room.join(code)02 A friend joins
They type the code and both are in, instantly, over a realtime socket connection.
onSwipe()03 Swipe independently
Each person swipes through film cards filtered to the streaming services, genres and runtime they actually have. Swipe up for the synopsis, rating and where to watch.
onMatch()04 Match
The moment both like the same film: a fullscreen match with confetti and a direct button to watch it.
04 Technical decisions
A split architecture that keeps joining instant.
A Next.js frontend on Vercel and a Node.js, Express and Socket.io backend on Railway, wired together through environment config. Rooms are kept in memory for the MVP, which keeps the account-free, join-by-code flow instant. The TMDB film database provides posters and regional streaming availability.
- Clients
- Phone A
- Phone B
- Frontend
- Next.jsVercel, Framer Motion
- Realtime
- Socket.ioExpress on Railway
- Roomsin memory
- Data
- TMDB APIfilms, regional availability
Swipes travel over the socket. A match fires as soon as both clients have liked the same film.
05 What I owned
The full product and the full stack.
The UX redesign, the design system and every animation, the realtime backend and the deployment. That includes the TMDB integration for posters and streaming availability, the matching protocol over websockets, and putting it live on its own domain.
06 Why it matters
Realtime only feels simple when it is built carefully.
Two clients, shared state, touch gestures and an animation that has to fire at the same moment on both screens. The product explains itself in seconds because the engineering underneath stays out of the way.
Need a product built end to end?
From the interface to the realtime backend and deployment. Tell me what you want to build, and I will tell you how I would approach it.