Skip to the workbench
← Back to the workbench

PROJECT FILE 03 / Collaborative product / Source available

Trip Planner

Less coordination. More going places.

Bring an itinerary, a group, and the shared expenses into one place. A collaboration problem turned into a practical planning tool.

Trip Planner project user-flow diagram connecting account, trip, itinerary, and collaboration steps.
Project user-flow diagram

The problem

Trip plans become scattered across messages, lists, and spreadsheets. Groups need a shared plan with clear permissions and room for change.

What I built

  • Built trip creation and day-by-day itineraries with activity reordering.
  • Implemented trip-specific owner, editor, and viewer roles, invitations, and comments.
  • Added checklists, attachments, expenses, and budget reporting.

Inside the engineering

The trip is the collaboration boundary

Invitations, comments, permissions, and planning data are organized around a specific trip.

Planning beyond the itinerary

Checklists and shared expenses keep practical coordination beside the day-by-day plan instead of separating it into disconnected tools.

What this demonstrates

Shows product thinking across collaborative workflows, access roles, and connected full-stack features.

  • React
  • Express
  • MongoDB
  • TanStack Query

The repository marks its former live deployment unavailable. The supplied diagram is project documentation, not a product screenshot.

SOURCE REVIEWED / 2026-11-07