Fernweh
An offline-first itinerary app that keeps a whole group's trip in sync, even at 30,000 feet.
- CLIENT
- Fernweh GmbH, Berlin
- ROLE
- Design, mobile, backend
- TIMELINE
- 14 weeks, 2025-26
- STACK
- React Native | Supabase
Group travel planning lived in six different chats.
The founders had a validated waitlist and a Figma prototype, but no engineering team. They needed a production app on both stores before the summer season, one that worked without signal, merged edits from every traveller, and didn't need a backend team to run.
- 01Offline-first data layer with conflict-free sync between devices
- 02Shared trip timeline with bookings parsed from forwarded emails
- 03Native maps, widgets and Live Activities on iOS
- 04Admin dashboard and analytics for the founding team
What made it difficult, and how it got solved.
Sync without a server of truth
Edits from five phones in airplane mode had to merge cleanly. A CRDT-based store resolved conflicts locally, with Supabase as a relay rather than a referee.
Two platforms, one person
A shared React Native core with native modules only where it counted, maps, widgets, background fetch, kept velocity without the lowest-common-denominator feel.
Parsing messy bookings
Airline and hotel emails arrive in hundreds of formats. A small parser pipeline with fallbacks and manual correction reached 94% auto-import.
“We went from a prototype to both app stores in one season, and the codebase is still something our new hires enjoy working in.”
Need a website or app like Fernweh?
Tell me what you're building. You'll get a 30-minute call, a written scope within two days, and a fixed price before any code is written.
or write directly | [email protected]