project

Design of a Family Travel Web App

ROLE
Product Designer
Process

Sitemaps
User Flows
Wireframes
Mood board
Mockups
Usability Test

tools

Figma
Figjam
Whimsical

time
2024
3 months
Scope
UX/UI Design Course by Designership
"Have you ever struggled to find the perfect accommodation with the right filters and information?“
"Have you ever needed expert advice but struggled to find quick, reliable answers?"

Overview

As part of UX/UI bootcamp project (Designership), I worked on designing FamStay, a booking app helping families find the right place to stay in France.

Problem statement
Families often struggle to book accommodations that match their real needs.

  • Key details like room count, bathrooms, or child-friendly features are unclear.
  • Filters are either overwhelming or not relevant.
  • Pricing lacks transparency, which creates frustration and mistrust.

The challenge was to design an MVP that makes booking simple, transparent, and reassuring for families.

Users and audience
The application targets parents in their 40s with kids, traveling as a family. Their priorities were safety for young children, activities for older ones, and trust in the booking process.

Roles and responsibilities
I was the only designer on this project, working as a UX/UI Designer.

I handled the full process: user research, defining flows and structure, designing wireframes and high-fidelity UI, prototyping, usability testing, and iterating based on feedback.

Scope and constraints

  • Project carried out during a bootcamp, with tight deadlines.
  • Early MVP focused only on core pages: Home, Search, Booking, Profile, Login
  • Small dataset of listings used for testing
  • Solo project, fully managed end-to-end

Understand

I started by revisiting the brief I had created during the UX Research phase. This document included my recommendations as well as the competitive analysis of major booking platforms.

With these insights in hand, I could begin the design phase with a clear understanding of user needs and improvement opportunities, allowing me to focus on ideation and creating the experience.

Brief Analysis

The founder of Accom.ai personally experienced the challenge of struggling to find a specific accommodation. There is a lack of supportive information and user controls to help traveling couples find suitable getaways in France.

Competitors

Airbnb, Booking.com, Expedia

Target Audience

Couples in their 40s with families seeking unique accommodations in France.

Objective & Constraints

The goal was to design a new web application with key sections: Homepage, Search/Booking, My Bookings, Profile Settings, and Authentication. Given this was Version 1, I had to be practical and realistic, considering limited listings (as it was a launch), tight timelines, and available resources.

Ideation

To frame the solution, I began by creating a sitemap, which gave me a clear overview of the app’s structure and the relationships between its main pages. From there, I translated the job stories into a user flow, illustrating how families would navigate through the booking journey. This helped me ensure that the experience was both coherent and aligned with real user needs.

Design

Wireframes

To create the wireframes in Whimsical, I looked at the sitemap, the user flow, and checked how competitors were doing things. It gave me an idea of what to expect from an accommodation booking platform, and some inspiration.

Mockups

I created high-fidelity mock-ups with visual design in mind. You can see several pages here.

Test

Once the high-fidelity prototype was ready, I conducted moderated remote usability testing to evaluate how well users could complete tasks related to the key features of the application. I was able to identify two major problems which I was able to work on and improve.

Test

Usability Testing

Since this was the first version (MVP), the goal was to validate key aspects of the product, especially the homepage messaging and the search listings page filters. The homepage needed to be compelling enough to attract users, while the search experience had to be intuitive and efficient.

To achieve this, I conducted moderated, in-person usability tests, where participants completed three key tasks while I observed and took notes, gathering insights to improve the design.
I can see I could search by occasion, which is great.
I’m not sure about the price… Is it per night or total?
I don’t know what this person icon means on the map…
Login
Search Results
Multiple Users 1 Streamline Icon: https://streamlinehq.com
6 participants
Birthday Cake Streamline Icon: https://streamlinehq.com
ages 30-40
Checklist Streamline Icon: https://streamlinehq.com
4 Tasks

Iterations

User feedback was minor but valuable. Here’s what I changed:

- Pricing clarity: Displayed both total price and per night price to avoid confusion.
- Activity icon update: Changed the generic person icon to a hiking icon (backpack & stick) for better clarity.
- Filter hierarchy: Adjusted the order from “Occasion, Price, Style, Activities available” to “Occasion, Style, Price, Activities available” as users associated Style with Occasion, which influenced price.
Login
Search Results

Prototype

What this project taught me…

This project taught me how to design with real-world constraints, especially when building an MVP with limited listings. I learned to prioritize features carefully and saw how small UI changes—like adding a map showing both accommodation locations and nearby activities (walking trails, nature spots, etc.)—can help customers make better decisions. Following a structured UX/UI process gave me a solid foundation for future projects.

Medium length hero heading goes here

Lorem ipsum dolor sit amet, consectetur adipiscing elit. Suspendisse varius enim in eros elementum tristique. Duis cursus, mi quis viverra ornare, eros dolor interdum nulla, ut commodo diam libero vitae erat.

By clicking Sign Up you're confirming that you agree with our Terms and Conditions.
Thank you! Your submission has been received!
Oops! Something went wrong while submitting the form.