ChillRide

Category: Motorcycle
Platform: Mobile, Realtime
Year: 2026; Started
Developer: Jake
Stat: 117; commits so far
Stat: 25; architecture decision records
Stat: 4; apps: API, realtime, worker, mobile

Preview

Architecture

Still being built. Screens come once it's further along; for now, this is how it's put together.

A group-ride app for motorcycle riders. A group starts a ride and everyone shares their location on one live map, keeps chatting on the way, and gets a history of every ride. Checkpoint alerts, group voice and a feed for each group come next.

What's Included

Sign-in with an email code, with refresh tokens that rotate
Groups with a join policy
Live ride: every rider on one shared map
Location sharing that keeps going with the screen locked
In-ride chat
Ride history with a summary of each ride
Next: checkpoint alerts, group voice and a feed for each group

The Problem

On a group ride the riders spread out: someone falls behind, misses a turn or stops, and the rest only find out at the next stop. ChillRide keeps the whole group on one live map while they ride.

By the Numbers

117
commits so far
25
architecture decision records
4
apps: API, realtime, worker, mobile

Under the Hood

Highlight 01
One map update per tick, not per ping
Each rider’s ping is written to Redis instead of being rebroadcast to the group. A tick loop per ride sends one snapshot every second or two, about 95% fewer messages for a 20-rider group, which is what lets a phone last a three-hour ride.
Highlight 02
Redis for the ride, Postgres for the record
Live positions sit in a Redis hash with a TTL. When the ride ends, a worker simplifies the track with PostGIS and stores it as one line, so raw pings never flood the database.
Highlight 03
Realtime as its own deployable
Live positions and chat go through a separate NestJS WebSocket gateway, so a busy ride doesn’t slow the REST API. Both come from one codebase and verify the same tokens.
Highlight 04
Location that survives a locked screen
Position sharing keeps running in the background when the rider locks the phone, which is how a phone spends most of a ride.
Highlight 05
A database role that can’t rewrite history
The app connects as a role that can’t create tables or change the audit log. Migrations run with their own role, and every route is denied unless it opts out.

Information