AIRLINER – HOTEL & FLIGHT BOOKING APP
Lab project
Flights, hotels and trip plans in one booking flow, designed from two real traveller profiles.
View prototype
BACKGROUND & CONTEXT
- Planning a trip from Ghana usually means flights on one site, hotels on another and the plan itself in a notes app.
- Prices change between tabs, details get typed in again and again, and the plan is lost once the booking is done.
- The lab brief: understand responsive design and Figma's responsive tools by designing one booking product end to end.
TARGET USERS
Leisure travellers like Sarah (29, marketing manager in Accra): budget-conscious, deciding on price, reviews and what to do there
Business travellers like Kofi (42, IT consultant in Takoradi): booking often, sometimes for family, deciding on time, reliability and paperwork
THE GOAL
Let someone search, compare, book and plan a trip in one place, and find it all again under 'Your Trips'.
MY PROCESS
- Problem statement & user stories
- Personas & mind maps
- Sitemap & breakpoint rules
- Style guide & components
- UI
- Prototype
KEY DECISIONS
- One search on the home page with Flights and Hotels tabs, so the first action is the main action
- Browse without an account; sign in only when you commit to a booking
- Loading states for every search, so a slow result never looks like a broken one
- A trip is more than a ticket: each itinerary pairs the booking with attractions, activities and restaurants
- Mobile Money alongside card and PayPal at payment, for travellers paying from Ghana
THE SOLUTION
- Search: flights or hotels from one hero, with filters for price, stops, airlines, star rating and amenities.
- Book: flight and hotel booking flows with seat selection, add-ons, payment and a confirmation.
- Plan: destination guides with attractions, food, customs and etiquette, and a View Itinerary page with receipt and boarding pass.
- Return: 'Your Trips' with a calendar and list of itineraries and saved destinations, plus account settings with a live password checklist.
KEY FEATURES
- Flights & hotels in one search
- Filters & sorted results
- Destination guides
- Trips calendar & itineraries
- Receipt & boarding pass
- Card, PayPal & Mobile Money
DESIGN SYSTEM & ACCESSIBILITY
- A documented style guide: blue #0F3FA9, amber #FFB000, a spacing scale of 2–64 and radii of 8, 12 and 24.
- Navbar, footer, cards and payment methods built as components with desktop, tablet and mobile variants; the sitemap sets the breakpoint rules (1200+, 768–1199, 320–767).
- Password rules use ✓ and ✕ icons, not just red and green. Next: white numbers on the amber calendar dates are 1.9:1 and need dark text.
View gallery (11 images)Hide gallery
(opens full size in a new tab)
(opens full size in a new tab)
(opens full size in a new tab)
(opens full size in a new tab)
(opens full size in a new tab)
(opens full size in a new tab)
(opens full size in a new tab)
(opens full size in a new tab)
(opens full size in a new tab)
(opens full size in a new tab)
(opens full size in a new tab)BY THE NUMBERS
- Search for flights and hotels
- 1
- Sign-ins needed to browse
- 0
- Ways to pay, Mobile Money included
- 3
OUTCOME
- A complete desktop booking product, from search to boarding pass, backed by a documented problem, personas and sitemap.
- A component library with breakpoint variants ready for the tablet and mobile layouts.
- A clear plan for the next breakpoints: what stacks on tablet, and what mobile prioritises (upcoming trips and quick actions).
What I learned
Writing the breakpoint rules before drawing the screens made the components honest: every part had to know how it would shrink.