Skip to content

Case study · Travel · Global · 2023

Group trip planning, without the group chat

Planning a trip with other people happens across a chat thread, three booking sites and somebody's notes app. Nothing agrees, and the person who volunteered to organise ends up as a manual sync process.

  • Flutter
  • Shared state sync
  • Offline-first storage
  • Maps & places
01

The itinerary is the shared object

Rather than treating a trip as one person's document that others comment on, the itinerary is collaborative state. Anyone in the group can add, reorder or veto, and everyone sees the same plan without somebody re-typing it.

02

Built for the aeroplane, not the demo

Travel apps are used precisely where connectivity is worst. Local-first storage means the itinerary is readable and editable offline, and reconciles when signal returns instead of failing at the gate.

03

Deciding together, then booking

Location selection, travel mode and calendar were designed as a sequence of group decisions, not a form, so the app supports the argument people are actually having before it asks anyone to pay.

Next

What does your product ask people to coordinate manually?

Anything a group has to re-type into a chat thread is a feature that has not been built yet.