MyRoadTrip - Google Docs mechanics for travel planning
The challenge
Two people edit the same trip, one loses connectivity for hours, and both versions must merge without losing structured data.
What I built
MyRoadTrip is a live cross-platform travel planner built on two architecture decisions I stand by. One: offline-first collaboration — two people edit the same trip, one offline for hours in the mountains, and everything merges without loss (Yjs CRDT on client and server). Two: instead of paying Google Places per call (€5-50k/year), I built my own geo index — ~2M self-hosted OSM points (OpenStreetMap → SQLite → vector tiles). No dependency on a giant for the core feature.
The architecture is reusable for field, medical, agriculture or logistics applications where offline edits must never be lost — and where owning your data beats renting it from a platform.
Key engineering points
Yjs CRDT synchronization on server and client, with local persistence through IndexedDB.
Web, Android and configured iOS builds from one Vue / Capacitor codebase.
Self-hosted OSM points of interest in SQLite to avoid Google Places dependency and pricing risk.
Fastify backend modules for planning, collaboration, billing, weather, routing and AI assistance.
Similar technical risk?
I can help scope the risk, architecture and first deliverable.
A 30-minute first call is enough to see whether I am the right profile for the problem.
A similar challenge?
A system like this one to build? Let's talk.
I take on critical technical work — from scoping to production, no debt or lock-in once it's handed over. Fastest way to see if it fits: a 30-minute call.
I reply within 24h — often sooner.