TrackMe journal

Notes from building a tracker that keeps its mouth shut

Engineering decisions, product arguments, and the occasional thing we got wrong — written by the people building TrackMe. No growth-hacking listicles.

A key derived on a device seals four envelopes; across a dashed trust boundary the same shapes appear as unreadable blocks.

The relay that cannot read its own traffic

Group Ride lets several riders watch each other move on one live map. The server carrying those positions holds no key to any of them — and every other design decision, from the Redis layout to the two-step join, follows from that one constraint.

Read the post

More posts are on the way — offline-first storage, what the battery actually costs, and why the SOS button was removed.