RouteFeed
Get in touch
Under the hood
RouteFeed is being built to production quality before launch: clean architecture, failure states designed up front, and place data the product owns outright.
Instead of renting search from a geocoding API forever, every named place in a market is imported once, given a permanent RouteFeed identity, and indexed for instant, typo-tolerant search. External geocoders become a shrinking fallback.
A new market means running the importer for that region. Nothing else changes.
The rule: replacing the map engine, the database, or a video CDN may only touch its adapter, never the product code. These boundaries exist in the codebase today.
MapRendererMapLibre today · swappableSearchServiceown catalog → index → geocoder fallbackRoutingServiceon-device engine (Valhalla planned)LocationRepositoryFirestore geohash queriesMediaUploadServicestorage and CDN under evaluationAuthRepositoryFirebase Auth · guest → real account linkingThe entire UI reads from one theme system. The coral accent is reserved, in the app and on this site, for exactly one thing: the moment you decide to go.