synctrip

Synctrip

A travel platform designed to help solo and group travelers effortlessly plan, organise and stay in sync throughout their journey.

  • Project Type: End-to-end product design + branding

  • Role:Sole UX/UI designer + brand identity designer (with guidance through critique sessions)

  • Industry:Travel, Lifestyle, Digital Experience

  • Tools:Figma, FigJam, Notion, Zoom

  • Duration:Q4 2024

DISCOVER

  • Why travelers?
  • How Do Travelers Use Their Time?
  • What do they really want?
  • The gap between behaviour and desire

DEFINE

  • What is the real problem?
  • Rerouting the Research

DEVELOP

  • Brainstorming Solution Ideas
  • Prioritizing With an MVP Mindset
  • Mid-Fidelity Prototype
  • Yellow Flag: Overwhelming Text

DELIVER

  • How Does SyncTrip Solve Real User Needs?
  • What I Learned

Designing an app for Travellers

DISCOVER

Why a travel connection app?

sectionImg

Based on existing research on modern travel behavior:

Travel planning today is extremely fragmented.

Through early research, I saw the same pattern across every traveller type — from 26-year-old freelancers to 67-year-old retirees:

During early research, I realized something interesting:

Even though the travel tech market is huge, there are still no platforms designed for:

Travel is social by nature — but travel planning is still fragmented, lonely, and scattered across apps.

Synctrip aims to fix that.

The gap:

No current tool lets travellers plan together and find aligned travellers in one place.

Everything is either a travel app or a social app but never both. Synctrip fills this by blending the clarity of planning tools with the social familiarity of swipe mechanics.

How do travelers use their time?

asterick_png

My Hypothesis

At the beginning, I believed Synctrip would mostly serve young solo travelers .

But early interviews challenged this idea almost immediately. It became clear that the real problem wasn’t age or experience; it was the lack of a simple, shared space where people could find compatible co-travelers and plan trips without chaos.

groupIcon
asterick_png

Research

Research Sources:

Sample:

A wide age range — 20s, 30s, 40s, 50s, 60s

Solo travellers, small groups, retirees, creative professionals

Research Questions:

These questions guided every interview and shaped SyncTrip’s structure and tone:

Artifacts:

Getting to know solo travelers through user interviews

I spoke with travellers across different age groups and life stages—solo travellers, small friend groups, retirees, and working professionals. Most of them travelled often but still struggled with connection, planning clarity, or coordinating with others.

What I wanted to understand

These conversations helped me shape clear, grounded personas—Aarav, Ananya, Ravi, Meera, and Lucas—and understand the emotional patterns behind how people plan trips, not just the functional ones.

userInterviewImg

Affinity map of notes from the user interviews. View the affinity map via FigJam.

What do travellers ACTUALLY DO?

What do travellers WANT?

Is there a disconnect between what travellers want and what they actually do?

According to user interviews, motivation to travel is already high. The real problem is coordination fatigue, scattered communication, and not finding the right people to go with.

The gap between behaviour and desire

The motivation to travel is already high.

The real blockers are:

I realized my hypothesis was wrong.

Synctrip isn’t only for young solo travellers.

Older adults, retired travellers, and family-based planners also expressed a strong need for structured planning and aligned companionship.

The challenge isn’t age! it’s the absence of a platform that supports shared decision-making before a trip truly begins.

My hypothesis was wrong!

I initially believed that Synctrip would primarily serve young travelers

Through interviews, I met:

Synctrip is not age-based.

Synctrip is rhythm-based.

It’s for anyone seeking aligned travel energy — not just young travellers.

This reframed the entire product direction.

DEFINE

Defining the actual problem

Travellers are willing and excited to explore, and they do have time or flexibility, but finding compatible co-travellers and keeping coordination alive is the real barrier stopping plans from turning into trips.

"I hate when 5 people say yes to a trip but no one wants to take the lead. The plan just dies in the chat."

– 31 year old user

"I want to go on trips but my friends never match my excitement, budget or pace. I wish I could just find people who are already planning."

– 62 year old retired traveler

Rerouting the research

New research focus: Social coordination layer in travel planning

Now that the problem space was properly framed, the direction of research shifted with these core questions guiding the next phase:

sectionImg
asterick_png

New Research Direction

Key questions now shifted to:

asterick_png

Research for the content

Before designing features, I needed to understand how people actually plan trips, not the polished version, but the messy real version that happens in group chats at 1:30 AM.

So I studied trip planning behaviour through travel forums, group chat screenshots from participants, and user interviews. A repeating pattern surfaced:

This helped me shape Synctrip not as just another itinerary tool, but as a shared decision space where everyone in the group can interact with the plan instead of just reacting to it.

sectionImg

Research for the method – Competitive review

To position Synctrip properly, I reviewed three types of existing solutions:

Across all tools, the missing element is participation. There is no space where people can vote, react, pin ideas, lock dates, or track who's in and who's out.

Deep Dive Research

I analysed:

Core Patterns

sectionImg

Tools Checked

Strengths Observed

Weaknesses Noticed

Opportunity

No app supports shared, interactive, multi-person planning + matching in one system.

My hypothesis was wrong!

HMW (How Might We...)

sectionImg

Brainstorming solution ideas

Using this HMW question as a filter, I started brainstorming different ways Synctrip could intervene in the current planning mess. I wrote down every possible interaction that could reduce friction between group members — from quick polls to synced calendars to playful “Are you actually coming?” confirmation nudges.

But adding everything was not the goal. The goal was to reduce mental load, not add another complex tool that needs a tutorial to understand. So I used the research insights to define clear product goals that helped me eliminate anything that didn’t actively make group alignment smoother.

Product Goals

Brainstorming

Ideas explored:

Prioritizing with an MVP mindset

So I asked a very direct question:

What is the smallest version of Synctrip that still solves the chaos of group planning? This helped eliminate heavy features like shared packing lists or experience journals from early versions.

Took alot of messy conversations

But we were able to finalise a path

Included

Removed / Delayed

Reason: These features add complexity without helping early flow validation.

User flow. View the user flow via FigJam.

DEVELOP

Where and how will users achieve these product goals?

To answer that, I started mapping an early sitemap structure, referencing how users currently navigate through trip planning using WhatsApp chats, Google Docs and mental notes. Instead of copying competitor flows, I used conversation-like hierarchy — the way trips actually start:

Home → Start Plan → Destination Swipe → Date Selection → Itinerary Builder → Invite → Trip Dashboard → Sync + Travel

Before detailing every branch of the app, I focused only on the essential touchpoints that would need to exist to test if Synctrip actually reduces planning fatigue.

The IA respects natural behaviour:

visual → choose → sync → refine.

Everything stays linear, soft, and low-stress.

asterick_png

Respecting existing user behaviour

From research, 4/5 users already start trip planning in WhatsApp to “float the idea first.” Instead of forcing them to abandon their natural behaviour, I introduced a “Convert Chat to Plan” entry point — a way to turn an existing idea or chat link into a Synctrip board instantly.

This became the first user flow I developed — because onboarding should feel like a continuation of their existing habit, not a fresh start.

Example flow: User drops a trip idea in chat → Taps “Sync this plan” → Synctrip generates a shared planning board with built-in voting

sectionImg
asterick_png

Primary flows for usability testing

To test whether Synctrip actually reduces back-and-forth frustration, I prioritized these core flows for usability testing:

These flows directly map back to the product goals and allow me to see if the app is doing what it promised — making planning feel shared, not scattered.

Finding design patterns for every element

userInterviewImg

Inspiration to Prototype

For the first round of Synctrip sketches, I placed quick wireframes alongside interface patterns from well-known travel and lifestyle platforms to study interactions that already feel intuitive to users.

I drew inspiration from Swiggy’s straightforward decision-making flows, Airbnb’s clear and confidence-building layouts, Trip.com’s structured search and booking patterns, and the way Marriott Bonvoy simplifies complex travel information without overwhelming the user. These references helped guide early choices around navigation, hierarchy, and interaction so the experience felt familiar from the very first use.

This inspiration phase made the shift from low-fidelity to mid-fidelity designs far more seamless. Because the foundation was built on proven user behaviors rather than experimental patterns, the overall structure remained strong and consistent as the design evolved.

userInterviewImg

Yellow flag: Overwhelming text

While shaping the trip board, I noticed that the itinerary section quickly became a wall of text. Most travel apps present the plan as one long paragraph, and during testing this made users skim or ignore important details.

I wanted the itinerary to feel lighter and easier to navigate.

So instead of one continuous block, I split the plan into day based segments. This mirrors how travelers naturally think about their trips and reduces cognitive load. Users can tap into one day at a time without feeling rushed or overwhelmed.

I marked this change as a yellow flag for testing because I wanted to see if users would understand the new format instantly or still expect the traditional long itinerary. Early feedback showed that breaking it down by days gave users more control and made the trip feel clearer.

asterick_png

How this improves navigation

Breaking the itinerary into days did more than reduce text. It changed how users moved through the plan. Instead of scrolling repeatedly to find one detail, they could jump directly to the exact day they cared about.

This also made it easier for groups to discuss plans. When someone said check day three, everyone knew exactly where to go without searching through a long list.

During quick tests, users naturally tapped through the day tabs without needing cues. The structure matched their mental model, so the navigation felt simple and familiar.

Iterating based on usability test results

Red flag: Limited calendar visibility

The initial design showed only one month at a time. I assumed this was enough because most users usually plan short trips and would select dates within a single month.

However, this created a major limitation:

During usability testing, it became clear that users expected to view a broader timeline at once. The single-month view made the experience feel restrictive and caused uncertainty.

To fix this, I replaced the one-month layout with a two-month view that shows a full range at a glance. Dates now highlight immediately when selected, reducing confusion about what is included in the trip.

sectionImg

Priority revisions

Testing surfaced multiple opportunities to improve clarity and reduce misclicks. I evaluated each issue based on impact, frequency, and the effort required to resolve it.

Most users were able to select dates, but the experience felt unclear. Expanding the visible calendar and improving selection feedback helped users feel more confident and aware of the trip range they were choosing.

Making group travel easier with SyncTrip

DELIVER

How does SyncTrip solve
real user needs?

The problem:

The problem:Planning a trip, especially with a group, has always been a messy multi-app process. People jump between WhatsApp chats, Google Sheets, Docs, screenshots, links, budgets, and endless back-and-forth messages. Information gets lost, decisions get delayed, and the confusion often leads to dropped plans or cancelled trips altogether.

The solution:

The solution: SyncTrip brings everything together into one destination for organising and planning travel. Users get all the tools and assets they need in a single place — dates, budgets, voting, itinerary planning, reminders, and tracking — without switching apps. It also works as a social platform where strangers with similar travel interests can connect, organise trips, and plan confidently as a group.

sectionImg

What I learned

asterick_png

Looking at existing research before interviews helped me enter the conversations with some direction, and revisiting it afterward made the insights sharper and the competitors clearer.

asterick_png

Spending time upfront on design references saved me later the wireframes came together quicker because I already knew what felt right.

asterick_png

And for branding, starting with what I didn’t want was surprisingly helpful. It cleared the noise and made it easier to see the direction Synctrip should take.

happy

Next Project

EXAM HUB

End-to-end responsive website + branding

Thank you for your interest in my work!

Made with lassi & spicy chips :)