Case study · Reeplayer

We put youth games on families’ phones, live

A live sports platform with real-time chat and paid Pro replays, used by 30,000+ people. Since 2021 we’ve built much of its app, backend and web app.

App Store Google Play Website

The Reeplayer app during a live game, with a comment and emoji reactions floating up

Client: Reeplayer
Industry: Youth sports streaming
Timeline: 2021 – present
Services: Mobile apps, Live video, Real-time features, Subscriptions & in-app purchases, Backend & APIs, Web apps, DevOps
Platforms: iOS, Android, Web

The opportunity

Reeplayer makes AI cameras that film and live-stream youth sports on their own. It wants families, teammates and scouts to follow a game from anywhere and, through its End Pay-to-Play program, sponsors to help bring player fees down.

Reeplayer’s own engineers build the camera and its AI. Everything people touch around the camera needed a team too: the app, the backend that runs live games and stores footage, the web app, and the tools staff use to run the business. Since 2021, we’ve been that team for much of it.

What we built, and why it mattered

Every game, live, for the whole family

Parents can’t make every game, grandparents often live far away, and scouts can’t be everywhere. Clubs needed streaming that just works on game day.

Admins start a Reeplayer camera’s stream from the app, check a private preview, then go live, and followers get a push. In 2026 we added phone streaming: a phone broadcasts the game natively over RTMP, adapts its bitrate, and keeps going in the background and through network drops.

Why it mattered: Anyone can follow a game live, in the app or on the web, and a team without a camera can still go live from a phone.

The My cameras screen in the Reeplayer app, listing cameras that are live, recording or ready — Owners see every camera at a glance: live, recording or ready.

A sideline you can join from anywhere

Watching alone on a phone isn’t the same as being there. Families wanted to react to a goal with everyone else who was watching.

Scores, game status, comments and likes reach everyone watching instantly over Socket.IO. Fans reply, @mention friends and teams and tag plays with hashtags. Each comment keeps its moment in the game, and reactions float up the screen as they land in the feed.

Why it mattered: A live stream feels like a shared sideline: the whole family can cheer the same goal from different places.

Reeplayer App Store screenshot, cropped: a live game with the score, a comment with a heart reaction, and the box to tag, chat and react — A live game with the score, comments and reactions.

Replays people pay for, clips they share

Reeplayer needed the app to earn money without putting the live game behind a paywall.

Reeplayer Pro adds Live Reeplay, a live DVR for rewinding a goal and jumping back to live, and Instant Playback of the whole game the moment it ends, plus pinch zoom, TV casting and picture-in-picture. Match Highlights are bought per game in the app, sponsored games carry the sponsor’s banner, and anyone can clip a play, add it to the game’s highlights and share it.

Why it mattered: Three ways to earn, from Pro subscriptions, per-game purchases and sponsors, while watching live stays free.

Creating a clip in the Reeplayer app, with the option to add it to the game’s highlights — Clip a play and add it to the game’s highlights.

A game day that holds up

A youth game happens once. A failed stream, or a release in the middle of a game, can’t be redone.

The release script won’t ship while a game is streaming live, database migrations run before any restart, and production ships from a version tag after approval. Phone streams ride out dropped connections, owners see each camera’s status live, and every recording’s sync to the cloud is tracked.

Why it mattered: Clubs and families can count on the stream when it matters, and Reeplayer keeps shipping improvements without risking a live game.

The Camera storage screen in the Reeplayer app, listing recorded games and their cloud sync status — Camera storage shows which recordings have synced to the cloud.

How we built it

React Native, native where it counts

One React Native codebase serves iOS and Android. Broadcasting from a phone needs native video pipelines, so phone streaming uses HaishinKit on iOS and RootEncoder on Android.

A Socket.IO room for every game

Each game has its own room on our NestJS backend, so viewers receive only that game’s scores, comments and status, and camera owners get live updates from their camera over the same connection.

Purchases checked on our server

RevenueCat runs purchases on both app stores. Our backend records each subscriber’s entitlements from RevenueCat’s webhooks and reconciles them with its API, so Pro access stays right even if a webhook is missed.

The best video that’s ready

NativeFrame carries live streams and keeps the archive behind Instant Playback, Mux stores camera uploads and cuts clips, and the player moves to the best available source on its own.

Technology

React Native
TypeScript
NestJS
PostgreSQL
Prisma
Socket.IO
SvelteKit
NativeFrame
Mux
RTMP (HaishinKit, RootEncoder)
RevenueCat
Google Cast & AirPlay
Firebase
Branch
AWS
GitHub Actions

How we work together

Since 2021, Invemo developers have worked as part of Reeplayer’s product team, alongside its product, camera and AI engineers. We ship the iOS and Android releases, run the backend’s deploy pipeline, and do the day-to-day engineering across the app, the backend, the web app and the staff dashboard we built to replace Retool.

That leaves Reeplayer’s own engineers free to focus on the camera and its AI, and gives the company one team that knows the whole platform, from a camera’s first boot to the replay on a parent’s phone.

Invemo’s founder, Parug Demircioglu, serves on Reeplayer’s board.

Next case study: Astrology Zone: We rebuilt Astrology Zone with its subscriptions intact

All work

Got an app idea? Let’s build it.

Tell us where your app is today and where you want it to go.

Get a quote Schedule a call 