TravelHub

Plan the
whole trip.

TravelHub started as a planner I built for myself. One simple place to keep track of the trip, from daily plans and bookings to who's coming and how much we're spending.

Role
Product Designer - UX/UI
Timeline
2025
Platform
Mobile App
Tools
Figma
01 / Overview

It started as my own itch to scratch

I plan a lot of trips for myself, with my partner, and for the whole group. Every time, I ended up stitching the plan together across a spreadsheet, my inbox and three chat threads.

TravelHub is the tool I wished existed: one place to plan the whole trip, day by day, with the budget sitting quietly alongside.

01

The plan lives in five places

Flights in email, hotels in chat, ideas in notes. Nothing shows the whole trip in one view.

02

No day-by-day view

It's hard to see what actually happens on each day, or what's still missing before you go.

03

Trips get out of sync fast.

Who’s coming, what’s booked, what’s left to spend - everyone keeps asking instead of having one place to see it all.

02 / Research

Validating the problem

To understand whether others faced similar challenges, I spoke with six people who had recently planned a trip and explored the tools they used along the way. Their insights revealed four recurring patterns that helped shape the direction of the product.

6interviews
5/6used a spreadsheet
+3apps per trip
  1. Planning is where the complexity starts. People want to see the full trip at a glance.
  2. Trips are shared, but planning tools are not. Planning happens together, yet most tools are still built around individual users.
  3. Planning happens in everyday moments. People make trip decisions throughout the day, making mobile the natural place to plan.
  4. Budget belongs in the trip. Knowing what’s been spent and what’s left is most useful when it sits alongside the actual plans.
03 / User Types

Travelers Plan Differently

The interviews revealed similar planning needs across different types of travelers. Whether traveling solo, as a couple, or in a group, the need to keep plans and spending connected remained consistent.

The Organiser

Plans for a group
Context
Takes the lead on planning for the group - coordinating bookings, payments, and keeping everyone up to date.
Needs
A shared view of the trip that keeps everyone informed, with plans, bookings, and spending clearly tracked in one place.

The Duo

Couple or two friends
Context
Plans the trip together, with both people involved in decisions, bookings, and day-to-day plans.
Needs
A shared view that keeps both people aligned on the itinerary, decisions, and spending throughout the trip.

The Solo Planner

Travels independently
Context
Plans trips independently, often managing more than one upcoming trip and handling every detail from start to finish.
Needs
A clear, structured view of each trip, with plans, bookings, and spending easy to manage throughout the journey.
04 / Structure & flow

Five tabs, one connected experience

The trip serves as the app’s central hub, bringing the itinerary, bookings, and budget into one connected planning flow. Instead of treating them as separate tools, the experience keeps every decision within the context of the trip.

Trips

Home & overview

Itinerary

The heart of it

Budget

Alongside the plan

Bookings

Flights & docs

Group

Who & tasks

Core flow: build the day-by-day plan

01

Open the trip

from Trips home

02

Open the itinerary

pick a day

03

Add a flight, stay or
activity

a few taps

✓

It lands on the timeline

and its cost rolls into the budget

05 / Wireframes

Structure before style

Low-fidelity wireframes helped define the app’s hierarchy and navigation early on - placing the day-by-day itinerary at the center, with bookings and budget supporting the planning flow.

What changed after lo-fi
  • Each trip now opens directly into the day-by-day plan, keeping the core task front and center.
  • Reduced budget visibility to one key number - money left, with the full breakdown one tap away.
  • A persistent action keeps adding plans, bookings, and expenses within reach throughout the trip.
06 / Design system

Designed for consistency

A consistent design system keeps the experience clear and familiar, while creating a sense of ease and anticipation throughout the journey.

Palette

Coral · primary Peach Cream Surface Ink Danger Success Warn

Components

Primary Secondary Ghost
Active chip Paid Booked
Hotel Flight Food Transport

Typography: the product

Assistant
Used for body copy and UI labels, with clear readability at small sizes.

Icons & shape

16px
radius
07 / The interface

The trip, screen by screen

The final interface brings the planning experience together - keeping each trip, its daily plans, bookings, and shared details connected and easy to navigate.

9:41Good morningMoranMIMYour tripsParis 202616–19 Sep · 2 travellersChristmas · Bratislava10–16 Dec · 3 travellersTripsItineraryBudgetBookingsGroup
Trips home
9:41TripParis 202616–19 Sep 2026 · Paris, FranceIMItzik, MoranItineraryFlight TLV to Paris16 Sep · TO3450Hotel check-inParis Hotel · 3 nightsBUDGET LEFT₪3,249 / ₪10,000DocumentsNo documents yetAdd tickets & confirmations
Trip detail
9:41DAY BY DAYItineraryPARIS · 16–19 SEPDAY 116WedFlight TLV toParisTransavia TO345014:10 - 18:15Hotel check-inParis HotelDAY 217ThuAdd activityDAY 318FriAdd activityTripsItineraryBudgetBookingsGroup
Itinerary · day by day
9:41DAY BY DAYItineraryPARIS · 16–19 SEPArrive · Flight TO3450Transavia1FriArrive · Flight TO3450TransaviaJardin du LuxembourgNight walk2TripsItineraryBudgetBookingsGroup
Itinerary · maps
9:41Budget+ Add expenseTripsItineraryBudgetBookingsGroup
Budget · alongside
9:41BookingsPARIS · 16–19 SEPTripsItineraryBudgetBookingsGroup
Bookings & docs
9:41GroupMMoranParis · BratislavaIItzikParis · BratislavaJJoeyBratislavaShared checklistRenew passportsTravel insuranceBook airport transferAdd itemTripsItineraryBudgetBookingsGroup
Group & checklist
08 / Interactions

Small interactions, smoother planning

Thoughtful interactions keep planning quick, connected, and predictable with every action reflected across the trip.

One trip, one timeline

Flights, stays, and activities come together in a single day-by-day and map view, making the entire trip easy to scan.

Everything stays in sync

Add a booking and it lands on the right day automatically, while its cost updates the remaining budget in the background.

Smart defaults

Common choices are pre-selected and recent preferences remembered, reducing repetitive input and making adding plans faster.

Helpful empty states

Empty days and sections guide users toward the next action instead of leaving them at a dead end.

09 / Testing & iteration

What testing changed

Five unmoderated usability tests helped uncover friction in navigation, planning, and budget comprehension. Each finding directly informed the final experience.

5participants
4/5Planned a day successfully on their first attempt
3Design iterations
Observed

Users struggled to switch between trips.

Changed

Made the trip switcher persistent and visible at the top of every screen.

Observed

Users struggled to connect new bookings with the right day.

Changed

Let users add bookings directly to a day, keeping the action within the planning flow.

Observed

“Committed” vs. “Paid” caused confusion.

Changed

Led with “Money left to spend” and moved the detailed breakdown below.

10 / Outcomes

Where it landed

What started as a spreadsheet for planning my own trips evolved into a complete, tested mobile experience.

The result

A focused end-to-end travel planning concept that brings itinerary, bookings, and budget into one connected experience.

What I learned

Starting with a problem I knew firsthand gave the project focus. Testing with others challenged my assumptions and made the experience stronger.

The takeaway

Start with a real need. Protect the core experience. Let every feature earn its place.