All originals
TravelShipped 20265-week sprint
Trip Synced
One itinerary the whole group can actually follow.
Scroll for the technical layer
Layer 01 — The world
A dark horizon line where a flight path and a coastline resolve into one continuous route.
Group travel planning that keeps flights, stays and reservations in a single shared plan, even when everyone books separately.
Interface01
Motion02
System03
Layer 02 — The build
X-ray the interface. See the engineering.
The challenge
Group trips fragment across screenshots, confirmation emails and three chat threads. The plan exists in someone's head, and the rest of the group finds out at the airport.
Architecture decisions
- 01One itinerary object per trip, with reservations as typed attachments.
- 02Email forwarding ingest so a confirmation becomes a plan item without data entry.
- 03Offline day view with timezone-correct rendering for every traveler.
Build process
Week 1Followed three real trips end to end.
Week 2Prototype: today, in order, offline.
Week 3Email ingest and reservation types.
Week 4Timezone model and the missed-flight path.
Week 5Ship ahead of summer booking season.
Stack
- Client
- React Native · Expo
- Ingest
- Forward-to-plan email parsing
- Time
- Timezone-correct itinerary model
- Offline
- Day view cached per traveler
From the codebase
// Timezone is a property of the plan item, not the phone
renderDay(day, { timezone: trip.timezone })Measured results
1
itinerary, zero screenshots
72%
reservations added by forward
5wk
kickoff to store
Principles in play
The technical layer holds the challenge, the architecture decisions, the week-by-week build and the numbers. Open it when you want to judge the engineering, not the screenshots.
Next originalWhenWouldWork
Build the next one