Ven Trip Planner
UI & UX Design for a Trip Planning App
For this project, I led the UX research and design of a trip planning app that balances structure with flexibility. Insights from user interviews shaped key features like dual list/map views, interactive itinerary links, rich notes, and trip-mate collaboration, giving travellers clarity and control throughout their journey.
Initial User Research
Quotes, Observations & Insights
Through user interviews and observation, I found that travellers often relied on flexible tools like Notion or Google Docs but struggled with features that were either too rigid or too unstructured. Pain points included difficulty adding times, lack of note-taking, crashes, and friction when planning complex journeys. Across the board, users wanted a balance of flexibility and structure, with must-haves like map and timeline views, rich notes, offline access, and collaboration with trip-mates. These insights shaped my design focus: giving users clarity, control, and adaptability whether they were meticulous planners or spontaneous travellers.
Tools & Current Planning Habits
Insight:Users already rely on flexible, multi-purpose tools like Wanderlog and Notion that allow them to centralise trip planning, visualise timelines, and collaborate. They gravitate toward apps that balance structure with freedom.
[Observation]
Users rely on tools like Wanderlog, Notion, Plan & Go, and Tripsy to centralise planning, use maps and timelines, import reservations, track expenses, and share trips.
Libby
[Quote]
“Databases with calendar/timeline views … easily shareable with travel partners” (Notion user).
Libby
Frustrations & Pain Points
Insight:Reliability issues, like app crashes, missing basic features (e.g. time zones, export), and poor syncing, break user trust. Friction around multi-leg transport planning adds cognitive load and limits adoption.
[Pain Point]
App crashes and freezes are common - especially when adding links or saving steps.
Libby
[Pain Point]
Missing features like time zone support, export/PDF options, and incomplete reservation syncing.
Libby
[Pain Point]
Complex transport planning across multiple regions is a major source of friction.
Libby
Summary Opportunities
Insight:Users want a system that balances structure and flexibility, one that supports both meticulous planners and spontaneous travellers. To meet expectations, the experience must feel robust, intuitive, and adaptable from day one.
[Insight]
Users expect frictionless control over the itinerary - reordering, annotating, sharing, and viewing routes.
Libby
[Design Implication]
Build for both high-structure planners and freeform travelers - toggle between modes.
Libby
[Design Implication]
Include offline access, export options, and drag-and-drop interaction patterns.
Libby
Customisation & Control
Insight:Users want a clear, structured itinerary that includes lodging, transport, and key activities. Visual formats like maps and timelines help them understand their trip at a glance. Flexibility is valued for small groups; structure is critical for larger or more complex trips.
[Quote]
“You can rearrange stops … map view saves me so much time.”
Libby
[Pain Point]
“Unable to add times … times aren't shown” -users expect this baseline functionality.
Libby
[Feature Request]
Drag-and-drop itinerary reordering in map and list views is essential.
Libby
[Feature Request]
Ability to add rich notes per item - confirmation codes, reminders, context.
Libby
[Feature Request]
Collaboration support - shared trips, editable by others, budget/expense splits.
Libby
[Feature Request]
Time zone clarity and editable time fields (especially when syncing from other apps like TripIt).
Libby
Must-See Itinerary Info
Insight:Users want a clear, structured itinerary that includes lodging, transport, and key activities. Visual formats like maps and timelines help them understand their trip at a glance. Flexibility is valued for small groups; structure is critical for larger or more complex trips.
[Quote]
“I always like to have a rough itinerary with where I'm staying and my first few transport/accommodation details.”
Libby
[Quote]
“Big groups need tighter itineraries, small groups just need a loose guide.”
Libby
[Insight]
Core info users expect: lodging, transport, key activities all shown clearly in map or timeline views.
Libby
[Feature Request]
Visual, map-based itinerary views help users understand their trip spatially.
Libby
[Feature Request]
Colour-coded categories for pins (e.g. food, sightseeing, transport).
Libby
User Flow: Creating & Editing Trips
Translating Research Insights Into Practical Design
This flow highlights key actions such as adding phases, locations, journeys, activities, and accommodations, as well as editing or deleting trip details. Subtle coloured backgrounds are used to signify container levels, helping to visually organise the hierarchy of steps and show how users move through the process. This made it easier to spot where clarity, flexibility, and control were most important.
Wireframing the trip pages
Defining core flows and structure before visual design
I created these low-fidelity wireframes to plan the main user journeys for Ven, including the trip dashboard, trip creation flow, and trip detail page. This stage helped define the overall structure, navigation, and component layout, making sure the experience felt clear and consistent before moving into high-fidelity design.
Style Guides
Initial visual design foundations & component system
This was the first iteration of the visual design for Ven. Since the early stages of the project focused heavily on UX structure and research, the visual system is still evolving. This initial pass established core foundations in colour, typography, and component styles, which will be refined as the product design matures.
